yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Streetwalker:
I see, thanks for the explanation.

As for the memory leak issue I don't know if CM fixed it on their side but it hasn't been much of a problem to me since I upgraded (I think I started building aosp 5.0 before the factory images were even out).
[Nexus 4 Original Android Development] show-p1984:
Just checked for you:

git merge --no-ff origin/android-msm-mako-3.4-lollipop-release
Already up-to-date.

and merged beta to stable.
[Nexus 4 Original Android Development] russde:
does this have the multirom patch?
[Nexus 4 Original Android Development] gorilla p:
This really is an awesome kernel. I have been so busy working on my repository and creating profiles for HD and AK, I never got to try a lot of other kernels.

Once AK left and Barome took a break, I've been looking for others to use.

I started using HellsCore and just found Bricked and I have to say I see a lot of similarities. I'm a fan of both.

I went ahead and created a BatMax Synapse profile for the latest Bricked kernel.

I'm running it on Euphoria (AOSP) 5.1.1 and it's working great.

Sent from my Nexus 4
[Nexus 4 Original Android Development] LolHacker17:
Pliszz share the batmax config??
[Nexus 4 Original Android Development] atulclassic:
any plan to support CM?
[Nexus 4 Original Android Development] gorilla p:
http://xdaforums.com/showthread.php?t=2987907

Sent from my Nexus 4
[Nexus 4 Original Android Development] shawnbrennan55:
I've been experimenting with different Mako kernels as well. I use Bricked on my Grouper and I didn't realize that Bricked Mako was still being actively updated. Performance seems good so far, battery life TBD. Thanks for the post!
[Nexus 4 Original Android Development] hardwareadictos:
Hi! [MENTION=4195844]show-p1984[/MENTION] please can you update your awesome kernel to 5.1? Missing it a lot, thanks in advance ?
[Nexus 4 Original Android Development] show-p1984:
beta updated to latest google source

20150502_155248_exp-6b6539b @ http://bricked.de/index.html#down
[Nexus 4 Original Android Development] show-p1984:
20150502_155248_exp-6b6539b beta promoted to stable
[Nexus 4 Original Android Development] LolHacker17:
I find 20150511 for stable makoo??thats it?
[Nexus 4 Original Android Development] jimyiak:
I think yes that's it!!

sent by nexy 4
[Nexus 4 Original Android Development] show-p1984:
Indeed ;)
[Nexus 4 Original Android Development] russde:
Hi, I noticed that the nexus 5 has the multirom patch, are planning to implement the multirom patch in the kernel for nexus 4. thanks.
[Nexus 4 Original Android Development] Alessioromatm:
Is safe change cpu frequency to 1.7 ghz with this soc?
[Nexus 4 Original Android Development] show-p1984:
As of now, there are no plans.

It's doable.

There is no "safe" when overclocking.
[Nexus 4 Original Android Development] gorilla p:
Yes, other devices have clocked this same chip up to 1.7GHz.

Chip was made to clock to 1.7GHz.

https://www.qualcomm.com/products/snapdragon/processors/s4-s1
[Nexus 4 Original Android Development] show-p1984:
"up to" doesn't mean that its ok to clock every chip with that clock. There are chips that will become unstable at those clocks, especially with our stepping. When you take into consideration that LG has requested a 1.5Ghz SOC from Qcom, they surely would be very very dumb to hand out very fast binned CPUs with 1.7Ghz capabilities. Most likely they will have handed out re-binned SOCs that run stable at 1.5Ghz, even if only barely.

This theory is backed up by kernel code, the very very low number of devices actually housing a soc that is normal or faster binned and common sense.

Even if you have a 1.7Ghz soc, lg could not have designed the device to pull the additional heat or distribute the needed power for this higher clock speeds over a longer period (which luckily isn't the case here if your device is properly built and not faulty).

However, those are just a few reasons. Also, increased voltage and higher current draw will increase wear on your device to a point where electrical pathways inside the soc are degraded so much that random errors occur. How fast this will occur can nobody tell you, since no chip is made 100% like the other.

It is never safe to over clock beyond manufacturer specifications and suggesting that is just ignorant.
[Nexus 4 Original Android Development] gorilla p:
outOTE=show-p1984;61043064]"up to" doesn't mean that its ok to clock every chip with that clock. There are chips that will become unstable at those clocks, especially with our stepping. When you take into consideration that LG has requested a 1.5Ghz SOC from Qcom, they surely would be very very dumb to hand out very fast binned CPUs with 1.7Ghz capabilities. Most likely they will have handed out re-binned SOCs that run stable at 1.5Ghz, even if only barely.

This theory is backed up by kernel code, the very very low number of devices actually housing a soc that is normal or faster binned and common sense.

Even if you have a 1.7Ghz soc, lg could not have designed the device to pull the additional heat or distribute the needed power for this higher clock speeds over a longer period (which luckily isn't the case here if your device is properly built and not faulty).

However, those are just a few reasons. Also, increased voltage and higher current draw will increase wear on your device to a point where electrical pathways inside the soc are degraded so much that random errors occur. How fast this will occur can nobody tell you, since no chip is made 100% like the other.

It is never safe to over clock beyond manufacturer specifications and suggesting that is just ignorant.[/QUOTE]

I have yet to run into anyone who has bricked this device due to a 10-15% over clock.

There are also features that unplug cores if heated beyond a certain temperature.

A large number of unleashed kernel users set 1700MHz as max freq., in fact in that thread it was recommended to not set the max freq below that for performance purposes, as the chip has no trouble with it.

In always up for an academic discussion or debate and open to new views. I also understand if you disagree, and I personally wouldn't "recommend" it to anyone, but to say that it's safe, is far from ignorant. If its so dangerous as to say (in bright red text) that saying its safe is "ignorant" , why even have the option?

Idk if you're just trying to CYA, but I feel the comment highlighted in red was a bit out of line.
[Nexus 4 Original Android Development] show-p1984:
The comment in big red was for anyone who, after reading your "it's safe to oc" post, thinks that pressing the "Go faster" button will have no chance whatsoever of bricking your device. All over clocking is dangerous, since you are driving hardware beyond manufactured specifications. I bricked a device last week (s6) by over clocking the cpu for that said 10% and running a benchmark. In Germany it's relatively easy to get a replacement for that if you are within 2 weeks of original buy date, but that is not the case for every country. We are talking hundreds of dollars here, most people save their money for more than 6 months to buy a new device.

You see, issuing a blank "it's safe" amnesty for over clocking is indeed ignorant. There are risks, depending on the build quality of your soc/your device they are either low or high and thanks to quality control most devices have an overall good build quality, which doesn't mean that there can't be serious negative incidents though. Since there is no way to look inside a chip and figure that out, you are basically in a game of Russian roulette. 5 times you may hear a click, but that one time you flushed a lot of money down the toilet.

I also would like to have you back up your claim that a chip running at lower clock speed can have trouble with that speed. I highly doubt that, using my definition of trouble (random faults, slower than usual performance at this speed, etc) this is not possible, unless the chip as a whole is defective.
[Nexus 4 Original Android Development] gorilla p:
Can you please clarify what you mean in your last paragraph here?

I don't believe I said anything about trouble at low clock speeds?
[Nexus 4 Original Android Development] show-p1984:
This in essence says that the chip has trouble with frequencies lower than 1.7 GHz max clock and you wrote it. ;)
[Nexus 4 Original Android Development] gorilla p:
Not at all, I'm not sure how you got that.

It was recommended not to set the max freq below 1.7GHz for performance purposes, as the chip has no trouble with it (Meaning It will perform better when set at 1.7GHz, and since the chip has no trouble handling it, there's no reason not to)

Nobody would indicate that using the standard clocking will cause problems, that doesn't even make sense.
[Nexus 4 Original Android Development] show-p1984:
Scratch that. Mea culpa, mea maxima culpa. Somehow the "no" in front of 'trouble' was cut off at the edge of my screen on mobile, or I was just eager to read something that wasn't there...

Sorry.
[Nexus 4 Original Android Development] gorilla p:
Lol, it takes a big man to admit that. :)
[Nexus 4 Original Android Development] ashjas:
I am having hard time finding a version of this kernel that works with cm12.1 for mako.

Can someone let me know if its stopped development for mako?

the download page on the bricked site, nowhere says if anyone of them works with 5.1.1 and cm12.1 , how to figure it out?

Thanks.
[Nexus 4 Original Android Development] dcop7:
You have hellscore, quanta.
[Nexus 4 Original Android Development] kevinnol:
Someone correct me if Im wrong but I dont think development stopped.

+ here's the latest AOSP(5.1+) kernel http://bricked.de/downloads/kernel/mako/master/bricked_mako_20150511_191446_master-96b53c8.zip
[Nexus 4 Original Android Development] Suhu007:
Will it work on oreo?
[Nexus 4 Original Android Development] D-m-x:
Yeah, he made that Jellybean(!) Kernel 4 years in the past so that it's compatible with Oreo lol.

No, most certainly it's not going to work.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Nexus 4 Original Android Development] show-p1984:
Test and report back if this fixes the temperature sensor 1 hardware failures :p

0.65: Click me

For those who are interested:

https://github.com/showp1984/bricked-mako/commit/76910198a8eb50e47c0292f52478182d173c50ef
[Nexus 4 Original Android Development] bumbumquietsch:
I loved your Kernel on HTC Sensation!

Going to use this without any doubt
[Nexus 4 Original Android Development] estallings15:
0.65

Working great. No shut down issues so far.

Scrolling is very smooth. I just came from 2 other kernels. Both had jerky scrolling. This one is MUCH smoother.
[Nexus 4 Original Android Development] show-p1984:
I will move the download to the stable page then :)
[Nexus 4 Original Android Development] yyz71:
Yep same here this one is alot smoother the scrolling no lag :good: Just like the other guy said below flashed a couple kernels and they seem to lag... Nice job. I've never flash your stuff before. I like the name BRICKED:laugh: BTW do you have an app controller? I've got a few I bought i like to support GOOD work:good:
[Nexus 4 Original Android Development] undercover:
What kernels did you guys come from? And my scrolling is not laggy on any kernel, apart from the Tapatalk, but that's a known issue with the app.
[Nexus 4 Original Android Development] show-p1984:
KControl will be on the market soon(tm) with some pretty neat configuration of mpdecision and thermald.

I decided that the kernel is more important than the app, so i put it on ice until the kernel has the most important features. (s2w, cmdline interface, fsync, cpuoc, cpu on/offline stats)

OP updated, 0.65 is the new stable.
[Nexus 4 Original Android Development] estallings15:
Franco R18 and Faux123's latest beta.
[Nexus 4 Original Android Development] xploder270:
How can you flash back to Stock Rom?

My TWRP Backup seems to not have worked (it doesn't show up in TWRP) and I saw that the .zip of yours renames some files and adds some modules.

Thanks.
[Nexus 4 Original Android Development] r0cafella:
You decided right my friend.

Better to have a rock solid kernel. than a unstable one which we can control.
[Nexus 4 Original Android Development] Higgsy:
Having issues with downloading from the host site in both stock/chrome browser direct to the phone. Download never starts and just redirects to another page. Boat Browser works fine. Anyone else having issues with those browsers.

Edit: actually boat browser doesn't download correctly either. The file is corrupt.

Sent by Galaxy Note
[Nexus 4 Original Android Development] meangreenie:
Yeh there needs to be reset .zip and warning, or otherwise people going from this to another kernel will end up with no mpdecision/thermal?
[Nexus 4 Original Android Development] show-p1984:
The file is not corrupt, androids WebKit just fails in forwarding the referer. That's why my server thinks you want direct access and redirects you, which android then wraps up into a file and tells you that it downloaded everything.

Firefox or opera work fine iirc. Otherwise download from a PC.

Everybody that can read knows that, its displayed during flashing.

Renaming two files should be easy too if you can flash kernels/roms, I don't think that there is need for a reset zip.
[Nexus 4 Original Android Development] saadi703:
No GPU overclocking?
[Nexus 4 Original Android Development] undercover:
I really don't see the need for GPU overclocking. Everything runs fine as it is. But hey, I say the same about cpu overclocking, so you might want not to listen to me :p
[Nexus 4 Original Android Development] ptr_hamilton:
It's fixed showp no more shutdown at my phone. Thank you!
[Nexus 4 Original Android Development] spr33:
Installed over Franco, however, I get stuck on the Google logo upon reboot. Any idea why? Using stock rooted 4.2.
[Nexus 4 Original Android Development] estallings15:
Franco has his own ramdisk. Reflash your ROM to get back to it's ramdisk, and the flash this kernel again. Remember to wipe caches before flashing the ROM.
[Nexus 4 Original Android Development] AppReviewBros:
You have to flash the stock nexus 4 boot .img posted in the OP before flashing the actual kernel.
[Nexus 4 Original Android Development] spr33:
Ahhhh, I should have read the OP rather than just blindly flash.

My bad.
[Nexus 4 Original Android Development] yyz71:
Here flash this then flash bricked-kernel :good:
[Nexus 4 Original Android Development] Audioboxer:
Awesome work fixing the shutdown bug :good:

Without trying to sound like a broken record or the feature request guy, I'm happily waiting till gamma controls are in to jump onboard. Fell in love with them too much on Faux kernel lol.

Utterly impressive work rewriting the thermal side of things though show. Can't believe the bad decisions made with the stock kernel :confused:
[Nexus 4 Original Android Development] estallings15:
What was Google thinking with their stock kernel? They always brag that they hire the very best coders. These guys had months to build the kernel. Yes, it's the first 3.4 kernel in any Android device, but the sucktitude seems to be off the charts. Let's hope for a kernel overhaul on the next ota.
[Nexus 4 Original Android Development] AppReviewBros:
You can still change the gamma settings using Faux's app when using the Bricked kernel.
[Nexus 4 Original Android Development] undercover:
Do you mean full gamma control or just RGB sliders?
[Nexus 4 Original Android Development] Shaky156:
Edit: ignore
[Nexus 4 Original Android Development] AppReviewBros:
Yes, the gamma settings in the application.
[Nexus 4 Original Android Development] dima901:
Got a problem.

If I turn the screen off and after a while I turn it on and it lags horribly (only cpu0 is online at 384MHz) some seconds later everything is okay.

I'm using kernel tuner. What can I do to prevent this?
[Nexus 4 Original Android Development] undercover:
Ramp up minimum frequency a bit. Should work as a temp fix.
[Nexus 4 Original Android Development] jhericurls:
Errmmm... no you can't.

Faux hasn't shared his gamma code with anyone. So its not going to work with any other kernel.

You can only adjust the RGB settings.
[Nexus 4 Original Android Development] saadi703:
Everything works well. All games are good except GTA Vice City which is still not as smooth as I would have liked. Also the games work smoother on interactive governor and the frame rates were a bit low using on demand kernel. Anyone else experience the same thing?
[Nexus 4 Original Android Development] meangreenie:
play gta vice city with performance governor
[Nexus 4 Original Android Development] danielsf:
Yeah, I've noticed the same thing on matrix and flauxs kernel. Interactive with touch boost enabled is my default set up because of this. Even though GPU over clocking isn't needed just yet, I hope Show will consider it later down the road. :)
[Nexus 4 Original Android Development] saadi703:
Yes I have also tried that and it works best with performance governor but I think with performance governor there are two side effect 1- heat 2- battery drain :( but you are right performance governor seems to me the solution.

---------- Post added at 02:38 AM ---------- Previous post was at 02:37 AM ----------

What is touch boost and what is the advantage of it?
[Nexus 4 Original Android Development] saadi703:
Battery life seems better :) I hope that it get better. My biggest problem (thermal throttling ) is solved and 2nd biggest is battery life so if it also get solved then I would be very very happy. I would check it for couple of days to make sure if my first impressions are correct or not.
[Nexus 4 Original Android Development] saadi703:
I am using v0.6 and so far happy with it. Scrolling looks fine however could have been better. I am happy with this kernel so do not want to mess up anything however I have a question regarding v0.65. Is there any tweak regarding scrolling as well? Couple of pages back some guy was feeling excited because v0.65 has good scrolling. Does v0.65 has better scrolling than v0.6 or both are same as far as scrolling is concerned?
[Nexus 4 Original Android Development] show-p1984:
There is no such thing as "make scrolling smoother" in the kernel. The kernel has no idea that you are scrolling.

0.65 compensates for a hardware bug with temperature sensor 1 and fixes unnecessary calculations in msm_thermal.
[Nexus 4 Original Android Development] saadi703:
I see. Thanks for the explanation. I am not facing any problem on 0.6 so I am going to stick with it as so far I am happy with it and I am not facing any thermal sensor bug at this moment. Games, apps everything is working great. I have checked FPS in need for speed most wanted using fps meter and most of the time frame rates are locked at 60 and do not go down much (max 4-5 frames at times). So happy that finally I am able to use this phone as it was supposed to be. All this because of you. Thank you so much.
[Nexus 4 Original Android Development] zimphishmonger:
wow, so there was an issue w temp sensor 1, im quite surprised
[Nexus 4 Original Android Development] show-p1984:
Since I just fixed the last sweep2wake issue (resume from deep sleep) after 3 hours of reading pm stuff you will all get a very early Christmas present. :)

Well maybe I will add sysfs support to allow you to shut it down first, shouldn't take long though :)

Oh wait! I forgot the traditional sweep2wake video! :)

/me gets his 1X.

Edit:

[youtube]RtmxlnikTiQ[/youtube]
[Nexus 4 Original Android Development] AppReviewBros:
I am about to flash this kernel but before i do so here's a question. Should I worry about the red LED problem if I don't overclock?

Or as long as I watch my temps I am fine?

I really want to get rid of the thermal throttling because it gets very annoying when playing games.
[Nexus 4 Original Android Development] joshndroid:
Show-p back in sensation days you recommended system tuner so i grabbed that but do you have an app out at this point in time for dev support?
[Nexus 4 Original Android Development] mgear356:
http://xdaforums.com/showthread.php?t=2027956

@show, any chance with your expertise, you can fix this? It's to disable the noise cancelation mic.. It's really bothering me when driving...
[Nexus 4 Original Android Development] jan.ringas:
He earlier wrote this:

source: http://xdaforums.com/showpost.php?p=35764136&postcount=207
[Nexus 4 Original Android Development] show-p1984:
There is virtually no way I can see how you could get the red LED on bricked 0.6+.

There will always be thermal throttling in a mobile device, there is no way you could get rid of that, except maybe a 2 kilogram copper cooler with a 140mm fan soldered right on top of the soc.

4 pages back :)
[Nexus 4 Original Android Development] hei1125:
Hi showp ,

I am the developer of Xpeia devices and I also expeience the blue color issue in the AROMA,

Here is the fixed binary http://db.tt/vrGTWDTS

Add the below code and it works for me with the fixed binary

ini_set("force_colorspace","RGBA");
[Nexus 4 Original Android Development] saadi703:
Wow!!! Never heard before that something as good as this is possible.

---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------

Is there any donate button. I can not see even in op. May be I am using XDA app that's why.
[Nexus 4 Original Android Development] saadi703:
Very happy with the results. Thanks to show my phone is working great and has become use able. Because of UV the phone is also running a bit cooler than before. All this and games still run silky smooth.
[Nexus 4 Original Android Development] joshndroid:
Cheers guys eagerly waiting the donate app lol
[Nexus 4 Original Android Development] Crenshaw-PCGH:
Soo i´m on paranoid android. After reading the thread i assume that this is the right way?

Wipe caches

flash kernel through recovery

wipe caches

can´t go wrong can it?
[Nexus 4 Original Android Development] ptr_hamilton:
No need to wipe cache, installer does it for you :D
[Nexus 4 Original Android Development] Crenshaw-PCGH:
So really just flash it? :D
[Nexus 4 Original Android Development] estallings15:
Yes.
[Nexus 4 Original Android Development] undercover:
You could do a little voodoo dance around it, won't do any harm :p
[Nexus 4 Original Android Development] Crenshaw-PCGH:
I will do this thanks for the tipp! :DD
[Nexus 4 Original Android Development] DforDesign:
Im stuck on google logo when fkashed 0.65 on paranoid. Any solution?
[Nexus 4 Original Android Development] AppReviewBros:
What kernel are you coming from? You are supposed to flash the stock kernel before flashing the actual one.
[Nexus 4 Original Android Development] meangreenie:
loving .65, though i do feel .5 ran games better with the on-demand governor. has there been any changes in that department?
[Nexus 4 Original Android Development] Crenshaw-PCGH:
is bricked.de down? :(
[Nexus 4 Original Android Development] elwaxman:
I second that, it is down for me too! maybe it is being updated!
[Nexus 4 Original Android Development] illwafer:
it's not the apple store.
[Nexus 4 Original Android Development] elwaxman:
ok what was that for? trying to be smart?
[Nexus 4 Original Android Development] ceejay83:
Anyone notice games are choppy? Dead trigger shows how choppy it can get
[Nexus 4 Original Android Development] Dan37tz:
The whole system is not as smooth as the stock kernel. NFS most wanted is choppier than stock, and while browsing through the homescreen is better than the other kernels, stock is still the smoothest.

Actually I think I have tried all the kernels for our Nexus 4, and Stock is still the smoothest.

I don't don't get it either, aren't these kernels suppose to increase performance? It seems that every modified kernel is choppier and slower than the factory kernel. :confused:
[Nexus 4 Original Android Development] estallings15:
Stock uses mpdecision, which is closed source. It also drinks battery like a wino does 2 buck chuck and throttles easily. The devs are having to do quite a bit of work to try and overcome these things. If you want to use stock, go ahead. I'll pass.