yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] manulemaboul:
After a deep sleep period, I'm stuck with the 4 cores always on and the min freq raised at the input boost freq or sometime 720mhz.

I'm trying with another kernel tuner and trickster uninstalled, maybe it's a trickster issue since it tends to mix min freq and boost freq, I'll keep you informed on either it fixed it or not.

Edit: So far so good, I uninstalled trickstermod 4h ago and it didn't reproduced since. I think it do was just a trickster issue,

UKM + synapse works fine.

2nd edit: confirmed, it was definitely that :).
[Nexus 7 Original Development] surikan12:
Does this kernel support Stock lollipop? Nexus 7 grouper with google official lollipop.
[Nexus 7 Original Development] slebit:
Of course.
[Nexus 7 Original Development] ashjas:
Does this support f2fs?
[Nexus 7 Original Development] petenatas:
Yes
[Nexus 7 Original Development] AirOne70:
Hi,

Is this kernel going to have DoubleTap2Wake ? It would be cool to have a test build with this feature since I'm only using it on the official dock. It's working great on KitKat !
[Nexus 7 Original Development] svs57:
android 5.0.2

bricked_grouper_20141223_171306_exp-f583ba8.zip

255|root@tilapia:/ # uname -a

Linux localhost 3.1.10-bricked-grouper-exp-gf583ba8 #1 SMP PREEMPT Tue Dec 23 17:14:52 CET 2014 armv7l GNU/Linux

root@tilapia:/ # insmod /system/lib/modules/kcontrol_gpu_tegra.ko

insmod: init_module '/system/lib/modules/kcontrol_gpu_tegra.ko' failed (Try again)
[Nexus 7 Original Development] show-p1984:
You can't insert the module without parameters :)

see dmesg for more details after the insertion attempt.
[Nexus 7 Original Development] svs57:
10x

Will test your kernel
[Nexus 7 Original Development] joaopaulo_:
Why camera doen't work with this kernel?
[Nexus 7 Original Development] show-p1984:
Are you sure that it is a kernel issue? It clearly works for me, and the kernel is up2date with google sources:

showp1984@jarvis:~/WORK/kernel/bricked-grouper-3.x$ git merge origin/android-tegra3-grouper-3.1-lollipop-release --no-ff
Already up-to-date.
[Nexus 7 Original Development] PrizmaticSmoke:
From what i've noticed while flashing several different lollipop ROMS recently, it seems like camera is broken on most AOSP based ROMS (tested freak-slimLP, DU, and purity), but works on most CM based ROMs. Switching kernels doesn't make a difference.

I'm guessing some change in AOSP for 5.0+ borked the camera for our device, but some ROM devs out there definitely have it working again already.
[Nexus 7 Original Development] tyler999:
somebody can tell me the CMD for choose gpu overclock , i can't use it on trickster or other kernel control on the last beta.
[Nexus 7 Original Development] pride007.2012:
unable to download shows 404 error. please any mirrors?
[Nexus 7 Original Development] show-p1984:
working perfectly here.

http://bricked.de/index.html#down
[Nexus 7 Original Development] Bob in Northern NJ:
Will this kernel still work with Google's 5.1 L release? My poor wife's tablet is so slow, and hangs up with the stock kernel. I'm trying to help her out.
[Nexus 7 Original Development] pride007.2012:
Yes it is working.
[Nexus 7 Original Development] Bob in Northern NJ:
I just downloaded and installed the kernel, and it works quite smoothly on the stock 5.1 release. Very impressive! I am using Trickster Mod, but I can't find the sweep2wake settings for the kernel. Any help or suggestions?
[Nexus 7 Original Development] pankaj_GB:
can i use it on tilapia because the download file says only grouper????
[Nexus 7 Original Development] show-p1984:
grouper is a superset of tilapia (there is only one kernel for both), so yes.
[Nexus 7 Original Development] Dodgexander:
I just don't get what I'm doing wrong. Trying to get my sister's n7 a performance boost running this kernel and the latest pa 5.02 alpha whilst utilizing f2fs on data and cache.

Using latest twrp I follow this procedure:

1. Flash rom and gapps

2. Format data and cache too f2fs

3. Install this kernel

The result? The system just boots up with both partitions still ext4.

What could be the problem here? Is twrp to blame? This kernel includes the ram disk needed for f2fs already right?
[Nexus 7 Original Development] show-p1984:
This kernel does not include any ramdisk. It uses the one installed on your device.

To get f2fs working either modify your ramdisk, or flash a boot.img that is already modified and then flash this kernel.

Tbh: f2fs is very hyped, but I only saw little real world improvement over ext4.
[Nexus 7 Original Development] manulemaboul:
In fact, f2fs is faster in write operations, a bit slower in read. It would help a tiny bit on /cache only. It helped a lot before 5.02 on grouper because of broken fstrim, but with the ext4 and fstrim updates brought by 5.02 it's pretty much useless now.

Want a real perf boost ? Use 5.1, the improvement is gigantic.
[Nexus 7 Original Development] Bob in Northern NJ:
How do I activate the sleep2wake functions of this kernel on my wife's nexus 7 grouper? Do I need a different app other than TricksterMod? All help would be greatly appreciated!

Thanks!
[Nexus 7 Original Development] mkiker2089:
Is this one no longer supported? The download page is just black when I click on it.
[Nexus 7 Original Development] show-p1984:
hmm?

bricked downloads
[Nexus 7 Original Development] mkiker2089:
Soory, it was on my end. I have firefox locked down too tight. Chrome brings it up. Dropbox probably uses java or flash and I have to turn those on when a site asks for them.
[Nexus 7 Original Development] show-p1984:
Bricked.de is pure HTML. Apart from The Google ad that is.
[Nexus 7 Original Development] SkOrPn:
Can I run this on 5.1 AOSP such as Chroma ROM?
[Nexus 7 Original Development] 1haumann1:
Yep.....running great with chroma [emoji106] [emoji6]

keep calm and have a Nexus :D
[Nexus 7 Original Development] SkOrPn:
Thanks, I was wondering if it needed anything from the 5.1 sources though. I noticed other kernels getting 5.1 bits, so I was wondering if we needed these bits as well, lol.

Currently got bricked at 1.5ghz and its running great. Although I noticed that sometimes the screen just out of the blue goes blank and I have to turn it back on, this will happen spontaneously even when scrolling through something. Does not happen on the stock 5.1 kernel, which is why I asked if this was ready for a 5.1 AOSP based ROM. I love it still though. Thank you.
[Nexus 7 Original Development] show-p1984:
I have merged the sources with aosp upstream, couldn't release anything though yet because kraken (compile server in my basement) suffered an apparent mainboard failure. It would freeze every time cpu & i/o over pci-e were loaded.

Supermicro replaced it without an issue and I have just finished swapping the boards. Tonight I will run continous Android aosp builds and kernel builds with -j100 at the same time on 4 VMs to assure stability and that this issue is fixed. If it is, I will release a beta tomorrow.
[Nexus 7 Original Development] SkOrPn:
Wow, you are amazing, thank you. In your KControl app I noticed that when I launch it, it then seems to hang a little bit, then the screen suddenly goes blank, then I turn the screen back on, and then a popup window tells me that KControl is not responding and asks me if I want to wait or close it. So, I close it then re-open it where it then works normally the 2rd try. Almost seems like SU not giving it permission the first run maybe? I am thinking about doing a dalvik and cache wipe, since this is a restored backup from TWRP.

I will report back if wiping dalvik and cache works or not. Thanks.
[Nexus 7 Original Development] show-p1984:
Try wiping KControl's app data.

Otherwise give me a logcat and I will fix it for KControl v2 (if that issue still exists in v2 since I rewrote major portions completely).
[Nexus 7 Original Development] SkOrPn:
Haha, I would thank you again, but XDA says I am limited to 8 thanks a day. So, I will thank you in person here... Thanks :good:

OK, well clearing/wiping cache and dalvik did not fix it. Its a fresh clean install of Chroma ROM, so I will try and remember the logcat procedure and post it in say Pastebin maybe? I just opened KControl and was met with an immediate closure of the screen, then it asked if I wanted to close the app, then on 2nd try KControl worked perfectly. Probably a new ROM issue maybe.

Thanks again
[Nexus 7 Original Development] SkOrPn:
Here is a logcat, its about two and a half minutes long because it took three times for the KControl app to actually work this time, which the log captured.

http://pastebin.com/h3Gv4vvu

I noticed that once it launches though, it seems to continue to launch just fine afterwards, so it only seems to have trouble launching the first time after a reboot. Other then that it appears to do its job just fine. Thank you again :good: Oh, and please let me know if its my ROM or device that is causing it.
[Nexus 7 Original Development] show-p1984:
Two new betas uploaded with merged sources for lollipop-mr1.

http://bricked.de/index.html#down

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

There is some strange stuff going on there. Are you sure that you have cleared app data?

Firstly, there seems to be wrong information stored to apply on boot:

04-07 18:03:57.111 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 0 for clk vde may not be < 100000000
04-07 18:03:57.111 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 1 for clk vde may not be < 100000000
04-07 18:03:57.111 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 2 for clk vde may not be < 100000000
04-07 18:03:57.111 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 3 for clk vde may not be < 100000000
04-07 18:03:57.111 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 4 for clk vde may not be < 100000000
04-07 18:03:57.112 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 5 for clk vde may not be < 100000000
04-07 18:03:57.112 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 6 for clk vde may not be < 100000000
04-07 18:03:57.112 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 7 for clk vde may not be < 100000000
04-07 18:03:57.112 E/de.bricked.kcontrol.BootupHandler(27140): ERROR: Value of frequency 8 for clk vde may not be < 100000000

Furthermore is the BootupHandler starting on your device, even though the device isn't rebooted?!? It gets started directly by the system, Android, through a callback chain. Android is apparently starting it when the app starts which is nonsense and hasn't happened with any version yet.

04-07 18:03:55.775 D/de.bricked.kcontrol.BootupHandler(27140): Boot handler service started
04-07 18:03:55.794 I/de.bricked.kcontrol.BootupHandler(27140): Yeah! I am running on a tegra device.

This can lead to an ANR since KControl will not attempt to read or write any information while there is already an operation in progress. This is neccessary to prevent race-conditions in a threaded environment.

Which KControl version are you on? (I really need to add a Logcat echo for that...)
[Nexus 7 Original Development] Leonhan:
Hi, can I use this with the Candy5 rom?
[Nexus 7 Original Development] SkOrPn:
Its the latest version at the play store. My ROm is a restored clean install of the latest Chroma ROM (or 04/05/2015). I had size issues with the last fresh install (data partition showed 720 MB free when I had nothing on the device yet), so I backed up the cleanly installed ROM, then used NRT to flash stock Android 4.4.3, then I used the stock recovery to factory reset, then I freshly flashed TWRP 2860, then I used TWRP to restore the backed up copy of my last freshly installed Chroma, then I installed KControl and your kernel and wiped cache and dalvik and rebooted. Yes I agree it looks strange, as if TWRP did not restore properly. I just redid my backups with the new TB. I'm about to do a fresh flash of Chroma all over again. I thought TWRP could restore without incident, but apparently not. lol

EDIT: And I forgot to mention, yes I have cleared app data, and even wiped cache and dalvik and rebooted, and I get the same behavior. Everything is still working, so what I think I want to do is first flash your new betas, then wait until the next version of Chroma and Banks Gapps is released and start fresh again. Thanks for your hard work.
[Nexus 7 Original Development] manulemaboul:
I usually don't care about benchmarks, but holy crap :o

You've put a tiger in my grouper XD

(Chroma + latest beta @1.5ghz, and f2fs on /cache only)
[Nexus 7 Original Development] show-p1984:
New stable build up, merging exp to master.
[Nexus 7 Original Development] SkOrPn:
Did you flash Franco first in order to get F2FS working? Or does chroma support F2FS in its stock version?

I'd love to get Chroma + bricked stable + F2FS on cache. That sounds like the ultimate performance setup.
[Nexus 7 Original Development] manulemaboul:
I was on franco before.
[Nexus 7 Original Development] SkOrPn:
If I want to clean install everything again. How would you do it?

This is how I normally would do it.

1. Copy all my data to usb. Done!

2. Factory Wipe

3. Flash Rom

4. Flash Franco

5. Format /cache as F2FS

6. Flash bricked Kernel

7. Flash latest banks gapps

8. Flash latest SuperSU

Reboot? Should that work?
[Nexus 7 Original Development] manulemaboul:
It should work, yep
[Nexus 7 Original Development] SkOrPn:
[MENTION=4195844]show-p1984[/MENTION]

I factory reset my device again, and 100% did everything from scratch, then I restored the apps using TB, and I still get the exact same weird behavior. Just thought you may want to know. I guess its the 5.1 ROM. No matter, it still works :good:
[Nexus 7 Original Development] shawnbrennan55:
I second that. Great combination for ye old Grouper. Thanks [MENTION=4195844]show-p1984[/MENTION], [MENTION=1978554]zephiK[/MENTION], and [MENTION=1050103]sykopompos[/MENTION] !
[Nexus 7 Original Development] SkOrPn:
I third it, lol. I'm thoroughly surprised at how well it runs. I set my cpu to 1550 mhz though. Hehe
[Nexus 7 Original Development] Leonhan:
Just a newb question though: why do you need to flash franco kernel first THEN the bricked kernel?
[Nexus 7 Original Development] PatrickMac:
For me it feels way snappier with f2fs on /data + /cache. I think that is as good as it gets for our beloved grouper
[Nexus 7 Original Development] shawnbrennan55:
Be careful with F2FS for /data on Grouper. I was unable to backup /data with several of the most recent TWRP versions.
[Nexus 7 Original Development] PatrickMac:
Any chance you used francos latest kernel?
[Nexus 7 Original Development] shawnbrennan55:
You should not need to do that with only /cache formated as F2FS. I flashed Bricked right over the stock Chroma kernel without issue. Just pure greatness for Grouper ?

---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------

Now that you mention it...I was on Stock 5.1.0 with Franco's latest. I seem to remember seeing folks having TWRP issues possibly related to that kernel.
[Nexus 7 Original Development] PatrickMac:
Unfortunately francos kernel seems to corrupt the data partition in time. But it is the only reliable kernel choice if you want to use f2fs on data partition with android 5.1 at the moment.
[Nexus 7 Original Development] show-p1984:
I haven't experienced that on both groupers and the one tilapia that run my kernel and are within "hey! you ****ed up my device!" - shouting distance.

Only one of those devices is running f2fs on /data though, but that still runs fine.

Exact kernel version?

How did you get to your conclusion?

Since you were using f2fs: what did you change/do to get f2fs on /data? (manually edited the boot.img, relied on a 3rd party solution, etc...)

To everyone else:

F2FS is experimental. EXT is rock stable. It has been for decades.

Do _NOT_ use F2FS on devices you rely upon.
[Nexus 7 Original Development] PatrickMac:
Sry, maybe this post was not specific. I was not talking about your kernel, the post concerned francos kernel
[Nexus 7 Original Development] bill3508:
This is running nice on Chroma. Good to have 1500 MHz. Thanks
[Nexus 7 Original Development] cilverjolt:
Has anyone figured out how to get bricked kernel working on the latest chroma with data/cache f2fs? i tried these steps so far and i would bootloop and find that my data partition went from f2fs to a 6.6gb ext4. This works fine with franco's kernel.

Step 1 flash latest chroma

Step 2 flash gaps

Step 3 flash super user

step 4 flash bricked_grouper_20150409_192819_exp-27a527c.zip

step 5 flash repack-grouper-bootimg-flash-after-kernel-f2fs.zip

step 6 flash dalvik/cache

step 7 reboot
[Nexus 7 Original Development] shawnbrennan55:
Works fine for me with /cache only as F2FS and skipping step 5.
[Nexus 7 Original Development] cilverjolt:
have you tried with data f2fs?
[Nexus 7 Original Development] show-p1984:
You need a ramdisk with f2fs support prior to flashing bricked.

Bricked does not bring it's own ramdisk along, it instead reuses your installed ramdisk and cmdline, which prevents overwriting a lot of stuff that rom developers usually edit. Franco on the other hand comes in a boot.img (iirc), which contains kernel + cmdline + ramdisk. That way franco can offer a f2fs boot.img (with the ramdisk edit) and a normal one, whereas I can't.

Delivering a boot.img is bad for a multitude of reasons, mostly because it overwrites everything, and there will be no-booters if your rom dev has made some critical adjustments which get overwritten.

It's also confusing because I would need to provide a boot.img for every rom and version/update (optimally, to ensure compatibility), which is obviously a full time job if you look at the number of roms available for only _ONE_ device.
[Nexus 7 Original Development] googleygoggles:
I may have bricked my tablet with your bricked kernel ;) lol. is this lollipop only or Kitkat only?

Bootloop
[Nexus 7 Original Development] tcat007:
Well, I just flashed on L, r5, and running fine with Chroma ROM.
[Nexus 7 Original Development] Leonhan:
What kernel tuner are you recommending for this kernel sir? I tried trickstermod but the cpu settings don't seem to stick. Min always caps at 910000.
[Nexus 7 Original Development] SkOrPn:
Lol, probably his own kernel control app. KControl in the play store.
[Nexus 7 Original Development] show-p1984:
Bricked is synced with aosp sources within 14 days of any updates on the aosp trees. Hence Bricked is Lollipop, 5.1 to be specific, at the moment.

My app, KControl, since I know it behaves correctly (duh :p).

910Mhz min is the touchboost frequency, which is only set if an input (touchscreen, button) is detected. It will be removed after one second again.

Some apps though are not built to handle touch boosts (either in-kernel, like in bricked, or through a binary). While trying to set the min frequency they sometimes set the touchboost freq to the min freq, which would make it permanent and this is obviously unwanted.
[Nexus 7 Original Development] bombadier:
Its not clear to me on the downloads which is the last version to work on kitkat ?

Thanks in advance
[Nexus 7 Original Development] show-p1984:
Last kitkat beta: 20141113_094602_exp-e5ca0b4

Last kitkat stable: 20141110_121623_master-5443222
[Nexus 7 Original Development] bombadier:
Thanks for that ,how do you tell ?
[Nexus 7 Original Development] show-p1984:
Let's take the betas as example. Under "Changes" there will be a link with all changes done to the kernel. Since this is a nexus device (and I merge with --no-ff), merging something from google always contains the repo url and branch I merged from.

So let's look at, I don't know... let's look at 20141113_095032_exp-c730c31. The "Changes" link for that is pointing here.

Now use CTRL+F (or your eyes, if you are oldsql and

boring

) to search for "Merge remote-tracking branch". You will find this at the bottom:

This means that this kernel is for lollipop, since I merged from Google's lollipop branch. Let's look at the previous kernel...

Kernel: 20141113_094602_exp-e5ca0b4

Changes: https://github.com/showp1984/bricked-grouper-3.x/compare/b0387d0...e5ca0b4

You will find no merges from Google, so we don't yet know for what version this kernel is. So let's look at the previous kernel...

Kernel: 20141110_113021_exp-b0387d0

Changes: https://github.com/showp1984/bricked-grouper-3.x/compare/b0387d0...e5ca0b4

At the bottom you will see this:

Bam. From here on until the lollipop merge it's kitkat!

Ergo: 20141113_094602_exp-e5ca0b4 is the last kitkat kernel, since 20141113_095032_exp-c730c31 is the first lollipop.
[Nexus 7 Original Development] googleygoggles:
Wow, that actual made sense!

Edit: thanks man, (or I could just press that button ;) )
[Nexus 7 Original Development] Sage:
Thanx very much
[Nexus 7 Original Development] TheDude:
Hello, you happen to have a uninstaller made up for grouper? Like this one? Awesome kernel but need y-cable support and modules for external wifi adapters... Thanks!
[Nexus 7 Original Development] poondog:
Flash your ROM back over the top :)
[Nexus 7 Original Development] TheDude:
Thanks man. I was just worried about all the init.d scripts etc. This kernel is awesome and complicated ;) I ran the awesome kernel cleaning script and flashed a different kernel and it seems to be working perfectly. Thanks for the heads up!
[Nexus 7 Original Development] sweetsuicide:
Hi, sorry for the idiotic questions:

* when you say "the most customizable kernel" do you intend stuff like frequencies and the like (like using the tool you suggest in the main page) or do you also refer to other paramenters ?

** Are these parameters stuff in the standard init.d scripts?

*** Is this stuff distro related?

*** Is this stuff kernel related?

More simply:

* Can I use this kernel on MinimalOS with any improvement on the performance?

* Can I use this kernel on ResurrectionRemix with any improvement on the performance?

* Can I use this kernel on Cyanogenmod 12.1 with any improvement on the performance?

In any case I would like to thank everybody involved in the development of this kernel: it makes my stock 5.1.1 snappier and at least usable!!!
[Nexus 7 Original Development] adeelraj:
Plz add fastcharge
[Nexus 7 Original Development] skooter32:
Any thoughts on a a kernel for mm?
[Nexus 7 Original Development] trowakage:
Has anyone tried using the 20150501 release with the latest CM12.1 snapshot?

I had the snapshot installed with F2FS and from this I think the CM12.1 stock ramdisk and cmdline should already support F2FS but after I flashed the kernel it's stuck at the CM logo.
[Nexus 7 Original Development] Byrana:
Yes, I did. It works quite well, except of data and WiFi drop. It won't receive a signal. A reboot will fix it. Unfortunately, it is a now go for me and I found out after buying kcontrol. Show-p can you fix that?
[Nexus 7 Original Development] show-p1984:
I could have a look later. On which rom is this? (the CM12.1 snapshot?)

Stock on the grouper/tilapia only goes to lp iirc (which works fine, tested on 5.1.1 LMY47V).