yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Doominq:
Thanks for reply show-p1984.

I have one more question. Would You temporarily upload latest stable version on some other mirror ? It would be very helpful for me, becouse I don't have any copy :(
[Nexus 7 Original Development] show-p1984:
Mirrors until bricked.de comes back again: (only stables)

Mako:

Kernel: bricked_mako_20130510_005118_master-028db65.zip

MD5: bricked_mako_20130510_005118_master-028db65.zip.md5

SHA1: bricked_mako_20130510_005118_master-028db65.zip.sha1

Grouper:

Kernel: bricked_grouper_20130510_211856_master-ef19bf2.zip

MD5: bricked_grouper_20130510_211856_master-ef19bf2.zip.md5

SHA1: bricked_grouper_20130510_211856_master-ef19bf2.zip.sha1

Ville:

Kernel: bricked_ville_20130510_033625_master-e34c2f0.zip

MD5: bricked_ville_20130510_033625_master-e34c2f0.zip.md5

SHA1: bricked_ville_20130510_033625_master-e34c2f0.zip.sha1
[Nexus 7 Original Development] Doominq:
A lot of Thanks show-p1984 !!
[Nexus 7 Original Development] ABu33:
Thx :) You're the best
[Nexus 7 Original Development] ricardowec:
Hope you get the server problem solved soon.

I am stuck in the Google logo.

Cheers

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] tibere86:
I can verify that the latest experimental(5-11) does not boot.
[Nexus 7 Original Development] fishhelmet:
Also just in case anyone is wondering even the stable version makes the new vanir nightly crap itself on boot. Seriously I've never seen a static and jumpy boot image before
[Nexus 7 Original Development] show-p1984:
Stable works perfectly, the beta doesn't boot because I was tired and didn't test it. (it was 8am).

If the stable doesn't boot for you reduce the GPUOC.

I am on stock and it works perfectly.
[Nexus 7 Original Development] drynyks:
Only time I have seen that was when I was overclocking the gpu at aroma install. You sure you didn't do that?

- "Is it dark in there?"
[Nexus 7 Original Development] ricardowec:
Here is what I got :

All builds finish the flash process with a dark screen. Have to be manually rebooted.

The stable build with time stamp 21.18.56 boots and works fine at 416 MHz. If over clocked, the gpu produces the distorted screen and doesn't go further. Working with this build atm. Will report any issues.

I am on multirom and have tried it with Rasbeanjelly and Carbon.

Cheers

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] show-p1984:
After the flash in recovery it shows you a black screen?

If that is the case it's your recoveries fault. My twrp (2.4.4.0) works fine.
[Nexus 7 Original Development] k29er:
484 gpu gives black screen. Setting lp to 620 fixed the black screen at 484 MHz GPU but still just lines at boot. Lp at 620 and gpu at 520 works fine.
[Nexus 7 Original Development] show-p1984:
You can't be talking about bricked since it doesn't allow you to overclock the lp core (which would defeat the purpose of it being a lp core in my opinion).
[Nexus 7 Original Development] ricardowec:
It might be Dennis, I am also using TWRP 2.4.4.0 but with the multirom extensions. Also never used Aroma in this environment before, so...

Cheers

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] tibere86:
Stable "bricked_grouper_20130510_211856_master-ef19bf2.zip" does not charge while docked. Verified by reverting to Glados kernel and reflashing Bricked twice.
[Nexus 7 Original Development] show-p1984:
Docked with what?

That kernel hasn't modified any charging stuff, it's still stock google.

Log?

Sure?
[Nexus 7 Original Development] k29er:
Sorry, the max screen frequency? Not lp.
[Nexus 7 Original Development] ricardowec:
Sorry, I am on the latest TWRP recovery (with the multirom extensions though) which is 2.5.0.0

Cheers

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] show-p1984:
New beta up:

http://bricked.de/index.php?action=kdownload&device=grouper&release=beta&type=aosp

bricked_grouper_20130512_063002_exp-8929b70.zip

It still has that usbhost & audio stuff + some tegra_mpdecision ports from the msm_mpdecision brother. And it boots now. (small fix, kernel was just too big)
[Nexus 7 Original Development] bamonkey:
edit for not reading back. Okay yup set the GPU to default of 416 and boot works, 484 is the cause of static bootup.

edit2: ok wow i have my own "tests" for performance and this one is bloody great so far. running dice video player in window overlay mode with LMT launcher and rounded window mod..usually i expect some microstutter using lmt at this point...but its smooth like butter. most excellent!
[Nexus 7 Original Development] El Nino1977:
Hate to be the one to say it, read back my friend the last 2 pages have discussed this issue.
[Nexus 7 Original Development] spthacker:
Dennis this beta loads just fine, but the transfer of audio to an external dac via the usb port doesn't work for your info
[Nexus 7 Original Development] ricardowec:
Boots fine at 416mhz. Hangs in black screen after flashing. Running now.

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] sjknight413:
Dennis,

I seem to have been a bit silly and not read that setting a gpu OC causes that weird static screen.

How would i go about getting into recovery again if that is the case?
[Nexus 7 Original Development] poondog:
Hold both power and vol down for like 15 secs until it goes to bootloader, then from there you can :thumbup:
[Nexus 7 Original Development] sjknight413:
Cheers, is fastboot the only way? currently at my girlfriends house so i have no adb/fastboot access!

EDIT: ah okay, did not realise there was options to scroll through on the bootloader! thanks mate :)
[Nexus 7 Original Development] poondog:
Don't need fastboot

Hold the buttons down, it will boot to bootloader

In bootloader on the device use the volume keys and power button to select the recovery option, boot to recovery, reflash the kernel witout GPU OC

On another note, I have come to a conclusion that the problems in recovery going black and due to Aroma? In HTC One forums there are massive problems with the same outcome. Aroma is made for HTC Desire originally, WVGA. Touch is off on grouper as well

I do find that leaving the device flat on a table and using the power/vol buttons instead of the touchscreen in Aroma helps with the stablilty and gets to the end of the process :) Just my 2cents
[Nexus 7 Original Development] farhanito:
Working fine here with fiio e07k DAC.

I'm using USB Audio patch by [MENTION=3158907]jacknorris[/MENTION]. Without this patch you probably need to reboot with DAC attached to make it work..

http://xdaforums.com/showthread.php?p=35023598
[Nexus 7 Original Development] spthacker:
Thats cos you are using the patch! :eek: I am aware of the attaching of it on boot as thats how I was using it via faux's kernel, but on bicked its still not right
[Nexus 7 Original Development] k29er:
If I set the screen off max frequency to 620 no black screen. Why do you call 475 lpmode if its not lp? GPU over clock to 520 works fine. 484 has not worked since before 58.
[Nexus 7 Original Development] FitAmp:
Latest beta is working very well, it seems to hot plug better than the latest stable. Battery life seems to be quite good :)

Changed up_threshold to 95, as 70 seemed to keep higher frequencies running a lot. Haven't noticed any lag/stuttering yet.
[Nexus 7 Original Development] Jomari29:
woah... the dead just raised from the ground...

Love it....

is this JB 4.2.2?
[Nexus 7 Original Development] FitAmp:
Yes
[Nexus 7 Original Development] nereis:
First time on Bricked and really enjoying its smoothness!

Best UI experience so far on the N7, will see about battery life.
[Nexus 7 Original Development] show-p1984:
Somebody has to fix your twrp multirom edition then.

Aroma works perfectly fine on my non multirom twrp version.

Log? @ https://github.com/showp1984/bricked-grouper-3.x/issues

475Mhz is lpmode. In fact it is the last frequency the lp mode supports. If cpu0 is anywhere above this frequency lpmode will not be possible. If it is at 475Mhz or below the lp mode will be possible. G-Mode range is from 340-max freq iirc, so they somewhat overlap (lp mode 51-475).

484 works on my device though, if someone would give me a log (as I asked for so often) at the Issue tracker on github I could do something about that.

to get the log, let it sit at the static screen, let it reboot, enter recovery and pull the last_kmsg.

Would be worth checking if it has adb in that static screen some ppl described when using 484Mhz gpuoc. (Might just be the gpu crapping out but the kernel still runs)
[Nexus 7 Original Development] Triscuit:
So I went and flashed the latest stable build but right after the boot screen I just got a screen full of static, did I read that this is for aosp only? I'm running project frankin nexus

Edit: just read your post above this, I'll give stock GPU clock a try

Edit 2: selected stock GPU, it shows the boot animation now but that's as far as it gets
[Nexus 7 Original Development] ximmox:
Trying something new (or rather old, bricked was my first N7 Kernel and was superceded by the also great M-Kernel), latest beta working really smooth here.

Did increase the threshold to 85 instead of 70, 51Mhz lowest freq, everything else stock. No boot problems either, running great! Danke Dennis, once again.
[Nexus 7 Original Development] nereis:
I've also happened to arrive at 85 after some testing, scrolling thru xda in Tapatalk HD feels much better than other kernels, as if there is a different touch screen driver behind this (anyone else notice better flicking momentum on Bricked?) Perhaps the mpdecision based hotplug is onlining cores more aggressively than other kernels?

--

After playing a bit more I brought it down to 80, this kills lags in Photo heavy apps like Pinterest compared to 85.
[Nexus 7 Original Development] uns0undl0gic:
Glad to see that Bricked is alive and kicking again. Definitely the smoothest kernel I have used on the N7 so far. Thanks for all the hard work!
[Nexus 7 Original Development] jclendineng:
Dude. Awesome kernel. Black screen is not a problem. Just hard reboot and Bam.
[Nexus 7 Original Development] show-p1984:
If you are talking about the ondemand up_threshold then it should be < 90.

#define DEF_FREQUENCY_UP_THRESHOLD	(76)
#define MICRO_FREQUENCY_UP_THRESHOLD	(70)

If it is not then something overwrites this. Probably the ramdisk.
[Nexus 7 Original Development] nereis:
The up_threshold I was playing with is

/sys/devices/system/cpu/cpufreq/ondemand/up_threshold

Shows up as just up_threshold in Trickster Mod, and I believe the default value was 70 at boot.
[Nexus 7 Original Development] nereis:
Not a full cycle yet but battery life looks very promising so far.

This is with -100mV UV across the board, max 1300 / min 51, ondemand up_threshold 80, auto brightness, no gaming but gps/wifi on all the time.

Looks like I found a new favorite kernel!
[Nexus 7 Original Development] FitAmp:
On demand values need a bit of a tuneup currently testing some different values
[Nexus 7 Original Development] show-p1984:
Well throw a pull request over to github if you have found some magic :)

But the current values actually work quite good, don't they?
[Nexus 7 Original Development] FitAmp:
Yes they do work well, but isn't 70 a little low for up_threshold?
[Nexus 7 Original Development] show-p1984:
Justify that claim. I won't change it just because it 'feels' too low.

If you can show me an example or explain why this is too low in your opinion then I am more than happy to listen to your argument and change it if necessary :)
[Nexus 7 Original Development] FitAmp:
Makes sense, its just that my device sits at 1300mhz most of the time, even when just sitting with screen on
[Nexus 7 Original Development] show-p1984:
With what refresh frequency? Ever thought about that the frequency is increasing because you are watching it? Somewhat like the Heisenberg uncertainty principle: if you are watching it, the value changes :)
[Nexus 7 Original Development] FitAmp:
I just checked once in 15 mins and had a 56% @ 1300mhz, Btw I'm using trickstermod.
[Nexus 7 Original Development] nereis:
This is mine after a day of use at up_threshold 80, frequency scaling looks fairly reasonable and feels just fast enough, but I can see 70 may be a better choice for smoothness under all circumstances though.
[Nexus 7 Original Development] ricardowec:
Just flashed tonight's beta (5-13 / 21hs).

Flashes fine under TWRP 2.5.0.0 with multirom extensions (no black screen) . Running all defaults (still cannot apply Gpu OC).

Cheers

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] poondog:
Hey show, any chance you can add smartmax governor? I've heard niothijg but good things for one x and assuming it will be there same because we use the same processor?

Works wonders on my incredible s too, its a great idea :)

https://github.com/maxwen/enrc2b-kernel-BLADE/commits

He's the developer of smartmax and that's his main github for hox+

Thanks :)
[Nexus 7 Original Development] Neroga:
+1 on this. Smartmax is amazing with CPU scaling. Getting 5+ hours of screen on time on my LGOG. Would definitely be higher on here. :3

Sent from my RootBox LG-E970
[Nexus 7 Original Development] show-p1984:
I guess you checked right after bootup? During bootup it's for 3-4minutes (depending on your installed apps) @ max freq. If you now add some ui interaction and since all apps need to be reopened after the first bootup this sounds valid though.

By the way: It's not the point of the governor to restraint the cpu, the point is to give it a longer leash if you need the power and prevent unnecessary high frequencies. If you use your device though it will ofc be @ max longer.

That seems rather not so good for our N7. On the first look it does not seem suited for our special ninja core architecture.

My modified ondemand tries to stay below or at lpcpu frequency as long as possible which gives us the biggest battery savings. Without such behavior screen on time would most certainly drop since g mode eats battery like crazy. I would also have to investigate scaling behavior, since mpdecision won't unplug any cores that are above idle_freq. If smartmax would keep the cpu above that for longer periods then we would also have our CPUs longer online than needed.

So you see, it's not that easy. :) I won't add any stuff that compromises the current balanced setup, even if it's not default.

If you request it at the Github issue tracker I will have a look once I have my current TODO list clear though.
[Nexus 7 Original Development] Remoteconcern:
Governors with made up names are almost always inferior to good old on demand or interactive in the long run. I'd rather Dennis spent his time on making on demand work well like he does do.
[Nexus 7 Original Development] ricardowec:
Had a strange crash with 5-13 21hs build.

Was browsing Tapatalk when suddenly got a black screen and the tab went dead. Had to hard reboot into recovery in order to switch kernels. Got last_kmsg. Will post it shortly.

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] ricardowec:
Here is the last_kmsg from previous post
[Nexus 7 Original Development] Cyda:
Any chance we can get a build with an option for GPU @ 446Mhz? Pretty please. :)
[Nexus 7 Original Development] show-p1984:
That kmsg is not from my kernel.

Linux version 3.1.10-g51d308e (tassadar@nymeria) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #32 SMP PREEMPT Sun Dec 2 14:09:23 CET 2012

Are you sure that you would even recognize any performance increase at that clock? (Compared to 416 stock)
[Nexus 7 Original Development] Cyda:
Possibly not but I've used that setting with most other kernels just to give a little boost and it does seem work well. I'd give the GPU @ 484 option a try but each time I do my N7 fails to boot, and with that in mind I am a little reluctant to even try the 520mhz option.
[Nexus 7 Original Development] ricardowec:
No, as i said, when I rebooted into recovery I flashed another kernel. My bad. Sorry.

But the crash was on your said beta.

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] show-p1984:
Well even if it's 'only' the beta I would still like to have a log.

Make it happen again and save the actual last_kmsg please :)
[Nexus 7 Original Development] drynyks:
Hey Show there are a couple things I have noticed that I wanted to let you know about.

On your latest stable " bricked_grouper_20130510_211856_master-ef19bf2.zip" turning on Zram in Aroma isn't saving for me.

On your latest experimental " bricked_grouper_20130513_214234_exp-df0dd20.zip" setting min frequency isn't working for me and no matter what I set it at it ends up at 910000.

- "Is it dark in there?"
[Nexus 7 Original Development] show-p1984:
True, I had an error in my updater script (init.d scripts are not getting extracted from the zip archive), which has since been fixed. I just didn't want to rebuilt master with no changes other than that.

That's the app you are using. I explained this in length somewhere on the ville and mako threads.

Mainly the following thing happens: If you set a freq your cpu is boosted. Which means it will be @ 910Mhz since you touch the screen. This will get some apps confused (even my own app had an issue with that in the beginning) and when their update threads try to update the frequency currently shown in said app as current frequency an android 'missing feature'/bug attacks. A programmer has no 100% reliable way to determine if (in the example of spinners) a user changed the spinner value, or if the thread which updates the currently shown value did that. Because of that the old value gets re-set when the update thread updates the current value. On most apps it is enough to open the CPU screen to cause this behavior since the background update thread will already be running and checking if the frequency changed. (and you touched the screen to open the cpu screen which caused a frequency boost to 910Mhz).

If you however did not encounter this and just got confused that your min freq is sometimes at 910Mhz, then this should answer this for you too, otherwise look in the second post.
[Nexus 7 Original Development] drynyks:
No other version I have tried, which is a bunch now, has done the min frequency thing to me except the one I listed.

- "Is it dark in there?"
[Nexus 7 Original Development] ricardowec:
Other kernels act in the same manner, modifying the min frequency when the screen is active.

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] drynyks:
I get it now. As Trickster was loading I moved my finger on the screen and was able to see what you guys are talking about. Sets min to 910000.

- "Is it dark in there?"
[Nexus 7 Original Development] razvanwin95:
how can i activate sweep2wake future ?
[Nexus 7 Original Development] ricardowec:
You cannot. Not implemented here AFAIK.

Sent from The Beast using Tapatalk HD
[Nexus 7 Original Development] poondog:
Not present as of yet in this kernel

DAMN ninjad :(
[Nexus 7 Original Development] razvanwin95:
hmm...what kernel includes this then ?
[Nexus 7 Original Development] Mahdi786:
Hi showp, do you think it's a good idea to disable 2-phase now that we this boost feature in mpdecision? I've disabled it in my personal build and it's working great, alot snappier.
[Nexus 7 Original Development] poondog:
none at the moment for grouper/tilapia
[Nexus 7 Original Development] show-p1984:
you can't. I have it on a local branch, but it is very spotty and has not been released because of that. I could push it out but most times it just won't work if the screen is offline and I just hadn't any motivation to fix it since I have my 'smart case' :). It also includes a rework of the touchscreen driver with some improvements to it.

it is already disabled. (https://github.com/showp1984/bricked-grouper-3.x/blob/master/arch/arm/configs/bricked_defconfig#L517)

zcat /proc/config.gz | grep ONDEMAND
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y

So you couldn't have disabled it :)

That good old placebo effect hit you critically it seems.
[Nexus 7 Original Development] nereis:
To those who where tweaking ondemand up_threshold, my conclusion is don't bother and leave it at the default 70. Enjoy the smoothness!

I see no discernable difference in SOT from 80, albeit I am testing more aggressive UV in the lower frequencies now.

I suppose one thing we need to keep in mind is that ramping up to max frequency earlier might not necessarily be bad for battery life, as this might prevent more g cores from going online, and from my understanding, apps like Trickster Mod only monitor the first core.

Next round of trials I'd try making 370 the min freq, seems to use 370 mostly anyway and not go to 51, and the rest should be for the companion core. Unfortunately there doesn't seem to be a way to monitor the lp core.
[Nexus 7 Original Development] show-p1984:
That's because the linux kernel has no knowledge of the lp core. The switch to lp mode is done by the tegra 3 soc on it's own. A few things need to be given in order for this to happen:

only cpu 0 may be online

the max clock of cpu0 has to be set to the maximum lp mode supported frequency (475Mhz)

+ a bunch of internal stuff we don't really know about. That's why switching into lpmode will fail sometimes.

The switch from lp to g mode is (on bricked with mpdecision) possible in two cases:

While on lpcore the runqueue is crossing the threshold

the frequency requested by the governor is above the lp cpus max frequency.

You will usually see the latter one, which is ok. We want this to be happening. Otherwise we would experience stutters. (Mpdecision identifies this in the kernel log with the '(freq)' annotation)

As far as the kernel is concerned there is only one cpu0 which has a range of 51-max and 3 cpus which have a range of 370-max.

If cpu 0 is in g mode only frequencies above and including 370mhz are available for it.

Using a true 5 core setup in an arm smp environment would be a true nightmare. that's why nvidia does the switch internally, so to speak a cheat to avoid all that hairy stuff that a 5 core arm smp setup would bring with it.

You can force your device into using only the lpcore if you disable mpdecisions boost mode, set max_cpus to 1 and set the max freq of your cpu0 to 475Mhz.

Then your soc will only use the lpmode, except in a few special internal cases we don't really know nor have any control about.
[Nexus 7 Original Development] lulonen:
So sick that I just bricked my Nexus with bricked kernel.

After flashing latest "stable" one I cant run SmoothRom and even enter recovery. How to unbrick whent the only option is bootloader?

edit: Back to live but unfortunately this SmoothRom don't start with this kernel, had to change to another.
[Nexus 7 Original Development] Shmi117:
Flash stock firmware, root, then flash any ROM you want again.
[Nexus 7 Original Development] show-p1984:
Most likely not the kernels fault since nothing touches your recovery. Try to wipe your cache from the bootloader, that's the most common thing that keeps recoveries from booting. If that fails just reflash the recovery.

I would hardly call that bricked by the way.

A bit drastic?
[Nexus 7 Original Development] Shmi117:
Not really, just straight to the point.
[Nexus 7 Original Development] show-p1984:
Worst case scenario he will just need to reflash recovery, he has a 90% chance that he can get it working again with erasing his cache though.

Going back to stock is like shooting with a bazooka on a mouse. Sure it gets the job done, but it's completely overkill.
[Nexus 7 Original Development] Shmi117:
As long as he gets it fixed the process does not matter.
[Nexus 7 Original Development] show-p1984:
True.

Minimalist versus thorough procedure I guess. :)
[Nexus 7 Original Development] lulonen:
Thx for help.

No problem with bringin back my nexus with toolkit and booting recovery without flashing but still don't know is any version of Bricked will work with SmoothROM. I remember bricked kernel as the best one on my old HTC Sensation so i really want to try it.