yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] bonzer2u:
lookin forward to it.....
[Nexus 7 Original Development] slebit:
That is really great news. Can't wait to use it!
[Nexus 7 Original Development] elsworth1983:
Great news :p
[Nexus 7 Original Development] slebit:
Can´t wait for Bricked-Kernel for 4.4! It´s the only thing that is missing right now. :)
[Nexus 7 Original Development] nealkoy:
[MENTION=4195844]show-p1984[/MENTION] any chance you will release a kernel update for 4.4.1? Would love to use your kernel in grouper seeing how it is flying hammerhead :sly::D:thumbup:
[Nexus 7 Original Development] show-p1984:
Christmas got in the way of my plans (also 2 birthdays in December for my niece/nephew and present madness...)

I will be back in action next week :)
[Nexus 7 Original Development] slebit:
That is great news!
[Nexus 7 Original Development] thelangosta:
My wife and father have birthdays in December so I feel your pain.

Sent from my Transformer TF101
[Nexus 7 Original Development] nealkoy:
Wunderbar! Cant for it already. Just want to tell you in advance A Merry Christmas and a happy new year :beer::thumbup:
[Nexus 7 Original Development] lagoskon:
Just installed 170913 version on KitKat by Mahdi ROM

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
[Nexus 7 Original Development] Lazy Rich:
Any news?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Original Development] Faschoda:
Would be awesome.
[Nexus 7 Original Development] show-p1984:
"An update is never late, nor is it early. It arrives precisely when it was meant to."

:)
[Nexus 7 Original Development] slebit:
That is so right. :)
[Nexus 7 Original Development] redeyedjedi:
thanks for your work! Your hotplug is killer. I had a couple of ideas I wanted to ask you about. do you think it would be possible to add core scheduling or ability to set "max active cores" in? what about OCing LP core and encouraging the system to stay on LP core until it needs more juice? would this be tooooo far from your "project butter" to make any sense? I was thinking a LP OC of 620 or 666 and then setting the CPU input boost minimum down to 666 from 910...... just curious on your thoughts about this.
[Nexus 7 Original Development] networkdood:
I use this kernel on my Nexus 5, and it is awesome. Trying to download the latest for my N7 2012 and I get an error during the Aroma installer process.
[Nexus 7 Original Development] beppemila:
Has anybody successfully installed 0.58 on nexus 7 2012 with kk4.2? Thank you!
[Nexus 7 Original Development] can0brains:
I'm running the 09172013 version on beanstalk 4.4.2, and seems to be running fine. :)
[Nexus 7 Original Development] networkdood:
No, not for me, it fails to install after I go through the default options with the AROMA installer....
[Nexus 7 Original Development] Lazy Rich:
Yup, fails for me too.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 Original Development] can0brains:
Hmm... What recovery are you using, I'm using twrp for multirom.
[Nexus 7 Original Development] dark2099:
For those trying version 0.58, that is for 4.1.2 I think, tree versions at the top of the lists are the newest and should be using those.
[Nexus 7 Original Development] Lazy Rich:
I tried the latest one, 0917, and it failed.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 Original Development] bjcrj:
What recovery?
[Nexus 7 Original Development] Lazy Rich:
Latest twrp

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 Original Development] lagoskon:
If you mean 2.6.3.1 downgrade to 2.6.3.0

Many issues with latest twrp. You will find zip file at twrp site

Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
[Nexus 7 Original Development] Lazy Rich:
Thanks for your help, but I think I don't need it anymore. I bought a Nexus 7 2013 (running Bricked kernel of course :) )

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 Original Development] Maxr1998:
Hi, I'm new to this kernel, how is the battery when oc to for example 1,5GHz?..

EDIT: it seems this kernel isn't kexec-hardboot patched, am I correct?

Sent using my nexus7 running Stock 4.4.2 with Xposed, GravityBox and XHaloFloatingWindow
[Nexus 7 Original Development] spica123:
Using bricked on hammerhead since it came out, now I bought a grouper!

Is there a version for KitKat 4.4.2 available?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Original Development] slebit:
Nope.
[Nexus 7 Original Development] ironmaskusa:
No, but I'm sure you or someone can include it in if you go to the developer's only section for this device there is kexec-hardboot patches you can add and such. Just an idea.
[Nexus 7 Original Development] Monfro:
Flash 2013.09.17 (the last stable kernel released): it works well with 4.4.2 (it will use 4.4.2 ramdisk from the ROM you flashed)
[Nexus 7 Original Development] stickus:
Anyone know if this will work on 4.4.4 now?

Sent from my Nexus 7
[Nexus 7 Original Development] slebit:
It should work.
[Nexus 7 Original Development] D_Viper:
hi... doues this kernel support ntfs on otg? thx
[Nexus 7 Original Development] bart.found:
hi [MENTION=4195844]show-p1984[/MENTION] Is the project discontinued? Does it works on 4.4.4 aosp roms? Last stable release in the OP is from 2013... It's a sin because it seems to be a great kernel...
[Nexus 7 Original Development] dark2099:
Try the latest beta in the link in the OP.
[Nexus 7 Original Development] show-p1984:
Right. I could merge beta to master :p

Otherwise: exp is up2date with google sources
[Nexus 7 Original Development] bart.found:
Could we expect a lollipop version soon? :fingers-crossed:
[Nexus 7 Original Development] show-p1984:
As soon as there are sources, yes. :)
[Nexus 7 Original Development] grandamle91:
Im having problems getting it to install on my Nexus 7 3g , keeps saying the board is wrong
[Nexus 7 Original Development] show-p1984:
It's probably your recovery identifying it as a wrong board. The zip looks for:

assert(getprop("ro.product.device") == "grouper" ||
getprop("ro.build.product") == "grouper" ||
getprop("ro.product.board") == "grouper" ||
getprop("ro.product.device") == "tilapia" ||
getprop("ro.build.product") == "tilapia" ||
getprop("ro.product.board") == "tilapia");

##########################################

Stable updated.

http://bricked.de/index.php?action=kdownload&device=grouper&release=stable&type=aosp
[Nexus 7 Original Development] grandamle91:
What can I do to fix it
[Nexus 7 Original Development] show-p1984:
Boot into recover and give me each output of:

adb shell

getprop ro.product.device

getprop ro.build.product

getprop ro.product.board
[Nexus 7 Original Development] grandamle91:
~ # getprop ro.product.devic

getprop ro.product.device

tilapia

~ # getprop ro.build.product

getprop ro.build.product

tilapia

~ # getprop ro.product.board

getprop ro.product.board

grouper
[Nexus 7 Original Development] chaostrodamis:
F2FS

can you please add all f2fs support. most kk grouper are running on f2fs
[Nexus 7 Original Development] show-p1984:
That should not generate any issues, as I am checking exactly for each one of those in my assert.

Which version did you try to flash?

I can have a look .

Android 5.0 is a higher priority though :)
[Nexus 7 Original Development] show-p1984:
BETAS UPDATED:

Kitkat with F2FS support

20141113_094602_exp-e5ca0b4

Lollipop Release with F2FS support

everything after e5ca0b4
[Nexus 7 Original Development] Natakranta:
Hi, thanks for such a quick support.

I flashed yesterday 5.0 factory images on my wife's Grouper and as expected superSU root was not working (I'm guessing selinux enforced as default in lollipop). So I went on karnel hunt today's morning to find a solution and I see Bricked in top of the list :)

Am I right thinking it will solve my lack of root problem?

Thanks, you are a legend!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 Original Development] show-p1984:
Nope, you will need to do this:

http://xdaforums.com/showpost.php?p=56526706&postcount=87

EDIT:

or-->

SuperSU-working modified stock boot images for lollipop:

https://drive.google.com/folderview?id=0B1Tn7X59NcPxek1ZTENxbnBzRTA&usp=sharing
[Nexus 7 Original Development] Natakranta:
Thanks for your quick reply. Appreciated

First part is beyond my skills/knowledge.

Second - are these boot images to be fastboot flashed?

In this case why isn't Bricked lollipop test karnel SuperSU-working modified as well?

Or are they the CFautoroot images to be booted only, the ones from here:

http://autoroot.chainfire.eu/

I feel like I'm missing something here because of my lack of knowledge.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 Original Development] show-p1984:
Yes they are to be fastboot flashed.

Bricked has never and, if possible, will never bring a ramdisk with it. That limits user choices and possibly overwrites user modifications. (as well as dealing a fatal blow to compatibility)

Furthermore: Auto-rooting your ramdisk while flashing bricked would be possible, but would also weaken device security on devices not going to use root. Which is why I do not do that. (Yes, there are people flashing kernels but are not rooting their handsets.)
[Nexus 7 Original Development] Natakranta:
Since you are in good mood to give lecture and I always like to understand things and learn, what's the difference between the boot images you linked which needs to be fastboot flashed to replace stock boot and the one from CFautoroot which are supposed to be only fastboot booted to perform some action, change something in system if I understood correctly apart of obviously flashing superSU 2.20 and su binaries.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 Original Development] grandamle91:
I got it to flash, i had to change my recoverey back to TWRP. I guess PhilZ Touch doesn't play well
[Nexus 7 Original Development] show-p1984:
The boot image I posted is the stock boot image minus the one line preventing us from getting supersu to work. :)

Would you like to know more?
[Nexus 7 Original Development] ricardowec:
Tried with this and a couple of other kernels and I am not getting this from CPU Spy

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] airmaxx23:
PA 2.1799
[Nexus 7 Original Development] poondog:
This was reported a few pages back. Reboot the device and it should show properly

Sent from my Nexus 7
[Nexus 7 Original Development] ricardowec:
Dennis:

I don't know if this helps but as other people have, I also set the minimum to 102Mhz and have been 65% of the time in Deep Sleep without going into SOD sod so far. Battery does not seem to have been affected,

BTW.. the SODs are a clear loop as one chewed almost 15% of juice.

Cheers

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] bigeyes0x0:
My advice to you, don't tinker with your gf's gadgets if she's the type that's easy to flip out. A lot of things might come out scathed...
[Nexus 7 Original Development] show-p1984:
The last_kmsg is from francos kernel.

Linux version 3.0.38-franco.Kernel-nightly-384GPU (francisco@francisco) (gcc version 4.6.x-google) #230 SMP PREEMPT Sun Jul 29 22:47:40 WEST 2012

Would be cool if you could join me @IRC so we can get it stable on your device. Just pm me when you have time, or highlight me on irc. (freenode, #bricked)

But we can still support it, can't we? :)

Yeah, most likely not enough voltage @51Mhz which causes random errors. The T30L is a bit strange across it's variants, like all Tegras are I guess.

(or the regulator is just unstable at such low voltages, which has happened before on some devices)
[Nexus 7 Original Development] albundy2010:
Of course you can support it. I just think its dumb to include / support something that is not needed at all and has no benefit to the device.
[Nexus 7 Original Development] show-p1984:
It has a benefit to users which are running memory heavy apps. Mostly Games ofc, like GTA3.

Since it has no adverse effect to support it, but may be useful to some users, why not include it?
[Nexus 7 Original Development] albundy2010:
I remember when I first saw it mentioned on the forums. The seven forum itself actually. Anyways I said wtf is this and what does it do etc. Everything I seen basically said it is just a rebranded compcache ( or something close to that. To lazy to look it up again) that was used on older devices with very little ram like a swap partition so apps that use more ram can actually run. How new devices don't need it and should not use it because there is enough ram so those apps fit and don't need virtual swap and so on.

I do not have extensive knowledge on the subject to break it down but it looks like some crap people drop in their feature list just to um well make their feature list longer. I also figured if this was used way back on devices like the g one, wouldn't people have kept on including it on newer devices first over the years if it was actually useful in anyway. I also run Linux and know how swap works on my desktop.

I fail to see how it can benefit our devices in any way at all. I still don't see how it can make a game run better or anything run better. So I ask why. I admit I am no expert on the subject and am going off of my vague memory of looking it up, but I can't make sense of why it would be used since all I ever seen was it is useless.
[Nexus 7 Original Development] Dabaum:
It's used for the same reason Windows uses a pagefile, and Linux uses a swap partition. 1GB isn't all that much memory, even for a mobile OS. And with the OOM killer in Android, it helps even more so in regards to keeping programs from being involuntarily shut down.

Z-ram is faster than compcache, since it's now in the Linux kernel. I don't think it would be in one of the most widely used kernels on Earth, if it weren't potentially useful.

No matter how efficient an OS is, if the programs you run aren't, you can never have too much RAM.
[Nexus 7 Original Development] farhanito:
just got SOD... while charging (probably when it's completely charged)

here's last_kmsg

http://db.tt/jo2rJYLa
[Nexus 7 Original Development] MetalPainis:
I experienced a few sod's in the last couple of days using this kernel with cm 10. Running @102 mhz as minimum frequency seems to have fixed this issue so far . Battery is great, overall perfomance is fine too. Keep it up ;)
[Nexus 7 Original Development] poondog:
That's another device lol the n7 kernels are based off Linux 3.1.10 and have higher GPU speeds on stock l :) lemme guess gnex?

+1 to everything you said. No sods after changing the min CPU speeds here :) *touch wood*

Only issue now is the no CPU states file thingo where I can't see CPU speed history in both trickster mod and cpuspy

It worked then didn't work. Its working again after a reboot, is it something that can be fixed or just live with it? Not a big deal though

thanks!!!

Sent from my Nexus 7
[Nexus 7 Original Development] show-p1984:
Next kernel will have default 102Mhz until someone with an sod n7 can lend me a few evening hours to figure out why it sod's on 51Mhz (mine is running fine).

You can ofc set it back to 51Mhz (which I would encourage you to do if it can handle it :p)

The states file issue remains a mystery. It should not disappear, yet it does. Couldn't get a log from the incident since mine somehow doesn't want to disappear anymore :/
[Nexus 7 Original Development] poondog:
What log can I get for you, and when? Do I pull a log when CPU states aren't found? And which log? Thanks

Sent from my Nexus 7
[Nexus 7 Original Development] airmaxx23:
Since changing my minimum clock speed to 102MHz I have not had another SOD. :good:
[Nexus 7 Original Development] sert00:
oh well,now i know why i not see a sod in 2 days....i'm always at minimum of 200,not 51 neither 102..so far so good,and i don't see negative impacts on battery

for the log above,it's a dmesg fom a gnex 's kernel...a nightly franco's one.384 is the fisrt OC step of the gpuOC.or you had attacked both on pc and you grabbed the wrong files,or you did an error when you copy-paste it from the destination where you stored that (and ofc you taken the wrong one)
[Nexus 7 Original Development] ricardowec:
I would be glad to help depict the difference in hours. we can arrange something in between , but I am on the road for the w/e and just took my Beast and phone with me. ( hot spot )

For the time being, an as you say in another post', settle for 102 at the bottom which I did and really enjoying the best engine for the N7

I will pm you . BTW.. as I have two ( they def are not the same ) one a July per order and a newcomer from last Tuesday. can play with both as the other has PA

Cheers

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] spthacker:
Be interesting to know if those experencing SOD's have tinkered with voltages or anything else themselves?

Running the latest Rasbean rom with this kernel as is, no other changes and buttery smooth with no SOD's and brill battery life.......
[Nexus 7 Original Development] wywerny:
nvm
[Nexus 7 Original Development] 9Lukas5:
[MENTION=4195844]show-p1984[/MENTION] could you also edit the stock lollipop kernel being able to boot with ALL-F2FS? That'd be great! :good:

L

Gesendet von meinem One mit Tapatalk
[Nexus 7 Original Development] javacody:
Installed the lollipop beta using CWM on my grouper and its boot looping no matter what options I select.

Looks like I get to reflash the factory image.

If anyone gets it working, I'll try again.
[Nexus 7 Original Development] frikakwa:
Had the same "issue" on stock root but no need to reflash the entire rom: just fastboot the kernel you can find in the zip.

fastboot flash boot boot.img
[Nexus 7 Original Development] javacody:
This kernel makes changes to other files besides boot.img. The proper way to revert will require flashing of system.img as well. Too bad I already wiped my data, eh?
[Nexus 7 Original Development] slebit:
I have also some problems with booting this kernel on stock 5.0. I can't get past google logo...
[Nexus 7 Original Development] show-p1984:
Lollipop Beta pulled.

There is an overlapping ramdisk issue, which wasn't appearing on my device since I am running a custom bootloader with a modified partition table.

If you have flashed it, just flash /boot and /system from the factory image and you will keep all your data, or restore /boot and /system from a nandroid which you should have created before flashing something called "beta" anyway ;)
[Nexus 7 Original Development] show-p1984:
Lollipop beta fixed & updated @ http://bricked.de/index.php?action=kdownload&device=grouper&release=beta&type=aosp

20141129_155149_exp-8050f27.zip is what you are looking for.
[Nexus 7 Original Development] slebit:
I can't enable Wifi on rastapop after flashing this kernel. Someone else with same problem?
[Nexus 7 Original Development] gorneman:
Rastapop dos not have init.d support. I have tried to add it but no luck. I'll make another try.
[Nexus 7 Original Development] sir*mez:
I get no wifi on stock lollipop.

edit: I ran the init.d files manually on terminal and still no wifi.
[Nexus 7 Original Development] gorneman:
[MENTION=3265523]slebit[/MENTION] [MENTION=680750]sir*mez[/MENTION] [MENTION=4195844]show-p1984[/MENTION]

I have added support to init.d to Phantom Kernel so you can use it to solve the problem.

Here are the steps:

1) Download the Phantom kernel

2) Download sysnit file

3) Flash Kernel and reboot

4) Copy sysinit in system/bin and chmod 777

5) Create init.d folder in system/etc and chmod 777

6) Reboot to recovery and flash Bricked-kernel

7) Installer script have a big cockroach: it not copy modules and init.d script to the right places, so you have to do it manually and set the right permission (modules folder rwxr-xr-x / init.d scripts rwxr-xr-x).

I'll try to fix the installer.

Thanks to [MENTION=4984300]Shivam Kuchhal[/MENTION] for his github repository
[Nexus 7 Original Development] show-p1984:
Bricked already adds init.d support to the ramdisk on flash, but that requires that busybox is installed as well. (I don't install busybox as well because that's the Windows way: Doing something the user may not want to do as default)

So I don't follow why you would post this here.

also: Having sysinit + busybox on your /system and ramdisk hooks for it will lead to some serious side effects. Mainly: All scripts would be executed twice, which could be devastating depending on what your startup scripts do.

To all those with wifi issues:

I will have an opportunity to grab my grouper tomorrow and I will look into that. Sadly nobody provided enough information (as seen in my thirdpost) which left me guessing blindly.
[Nexus 7 Original Development] gorneman:
I hope description of my situation would help you to solve problem.

I have rastapop F2FS with busybox installed and fully functional (Rastapop F2FS comes with M-Kernel a72 installed and busybox is required to use Tricksetr Mod).

Then I have installed Bricked latest beta. It boots, but no wifi and rom reboots many times .

I have reset to factory, installed rastapop f2fs, created init.d folder, set permission and re-flashed bricked-kernel: no wifi.

With the steps I wrote wifi seems to works fine and reboots are gone.

I don't know this was the best way, but it works. It was only a little hint to fix a problem.

P.S: if I understand correctly, the installer use ramdisk from previous kernel to build boot.img, so these ramdisk should support init.d.
[Nexus 7 Original Development] show-p1984:
My installer modifies any ramdisk and adds init.d support.
[Nexus 7 Original Development] show-p1984:
Wifi fixed @ 20141201_142306_exp-be5199b.zip
[Nexus 7 Original Development] slebit:
Thanks! It does work!
[Nexus 7 Original Development] gorneman:
WiFi solved with latest zip, bit i noticed that CPU min frequency is 910 MHz and i can't change it with trickster,kernel Turner 2014 beta,no frills CPU control
[Nexus 7 Original Development] show-p1984:
The CPU min freq isn't 910Mhz.

Please read the third post.
[Nexus 7 Original Development] gorneman:
Thanks show-p and excuse me for the stupid post.

910 MHz is the touchboost frequency, wich is erroneously regarded as the min frequency
[Nexus 7 Original Development] Pavelol:
Hi show-p, it's good to have you back old friend!

After upgrading to official lollipop images, i got it rooted and flashed twrp.

well.... there was some moments i was thinking "why did i do that", i wasn't able to perform a single task without lagging,framing and all the bad stuff....

And suddenly i saw Bricked and i knew "miracles do exists".

After i flashed the kernel my nexus got revived and has now new life, thank you for that and keep your awesome work going :)
[Nexus 7 Original Development] grunch21:
I found a bug when playing music. There's hissing sound when screen is locked. I didn't have this problem with other lollipop kernels.

Other than that, everything is good. Thanks.
[Nexus 7 Original Development] Pavelol:
Is anyone facing random inactive shutdown?

For example after 12 hours or more with no use sometimes i find my nexus, off.
[Nexus 7 Original Development] slebit:
Nope. It's rock solid for me.
[Nexus 7 Original Development] Hasuris:
I'd like to overclock the GPU but there is no Aroma-installer popping up during flashing. I am using the latest beta on rastapop (f2fs). Any ideas what went wrong?
[Nexus 7 Original Development] slebit:
You will have to change it with an cpu app. I guess trickster mod might work. I haven't changed it myself.
[Nexus 7 Original Development] manulemaboul:
I doesn't have GPU OC in trickster, didn't have aroma installer either, I guessed it was because it's a beta release. I'm happy with the default GPU freq so it don't bother me.
[Nexus 7 Original Development] Hasuris:
The way GPU overclocking is implemented, isn't supported by any app. Tried trickstermod, Kcontrol and some others.
[Nexus 7 Original Development] manulemaboul:
I got a weird bug, after a while the hotplug stop working and I got to re-set max freq or min freq to get it to work again:

Am I the only one ?
[Nexus 7 Original Development] show-p1984:
Please explain your issue in more detail.