yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] abhifx:
Only thing added in gerrit seems to be sdcardfs, so that should be it. So how is it? Haven't checked kernel 3.4 for a while.

Edit: this why proof read is necessary. my poor english
[Nexus 7 Original Development] adstraylight:
I was hoping it was sdcardfs, but my ssd boost app makes no reference to it, so I don't think so..

Generally the system runs pretty well, I'm still using my tweak collection to enhance stability, I think rhe camera's still borked, and the system ui occasionaly crashes under heavy cpu load.

But as I say it's generally good, and particularly so given the device's age:)
[Nexus 7 Original Development] jlau3172:
Are you having a hard time keeping it charged?

It took me all day to get it charged with the tablet on.
[Nexus 7 Original Development] adstraylight:
That's probably just background compiling, causing wakelocks, ie the tablet isn't sleeping when the screen is off. I have found this be more of a thing with this latest update, but it's back to normal now.

A few restarts, maybe charging to full when powered off, and it will settle, at least that's my experience.
[Nexus 7 Original Development] adstraylight:
All good so far with the experimental build, no system ui crashes so far? I've just switched back to the default balanced setting for CPUquiet to test further, and will post if anything goes wrong.
[Nexus 7 Original Development] adstraylight:
Further to my last, I did have a system ui crash with the CPUidle governor set to balanced, and overall the ux was much more jerky an prone to small lockups that would clear after a seccond or two. I've now gone back to the runnable setting that I was using before, and everything is smoother. I hope this info helps in tracking down the problem.
[Nexus 7 Original Development] JT1510365:
Try changing the LCD DPI density to 320 instead of 213 in build prop you get a bigger screen and everything works for me that way last time I tested:)
[Nexus 7 Original Development] AndDiSa:
[MENTION=5840086]zyian[/MENTION] [MENTION=4619263]sheffzor[/MENTION] I would like to thank you very much for your hard work. Unfortunately I did not see much progess in the last weeks regarding the Nexus 7. Did you abandon the Nexus 7 or do you still have the intention to bring Oreo to it? Today I've managed to create a pre-alpha version based on the latest Oreo 8.1 sources, the Unlegacy Project tree and my 3.1.10-kernel updated to match the Oreo requirements. There are still many things to be done as almost nothing works but at least it boots up ...
[Nexus 7 Original Development] ThePiGuy:
Great ROM and really great to see the nexus 7 still getting updates even now.

I was just wondering, is the f2fs for the system as well (on the front page, it mentions keep cache as ext4, and data as f2fs but no mention of the system partition)

Edit: typo

Edit 2: Turns out the zip automatically re-formats system as ext4, so that appears to solve the question
[Nexus 7 Original Development] AndDiSa:
[MENTION=8699949]ThePiGuy[/MENTION] there is no advantage to have /system as f2fs as there are no write actions at all ...
[Nexus 7 Original Development] ThePiGuy:
Am I right in saying this is using the 3.4 kernel? How does that compare to 3.1 kernel (both on nougat)?

Edit: typo
[Nexus 7 Original Development] Cocalarix:
It's awesome to see that you got it to boot. Are you willing to upload that build so we can help you out with logs and bugs?

And how's the performance so far? Every device I've updated to Oreo felt so much better so far.
[Nexus 7 Original Development] AndDiSa:
[MENTION=5348241]Cocalarix[/MENTION] as base functionality, e.g. WiFi, is not working yet, I suppose it's useless to upload such a version.
[Nexus 7 Original Development] Alexander_orlov:
Nice. Support nexus 7 2012 3G/Wi-Fi?

Cant wait :P

7.1.2 big lagging and crashed lockscreen other...
[Nexus 7 Original Development] dirtyreturn:
This may be a stupid question, but, who cares.

What happened to the unlegacy-android downloads page???

It was polished and easy to navigate. Now its just a basic list. (???) Anyone have any information? Just curious, why the change?
[Nexus 7 Original Development] Bert98:
Is it gonna be built on android go? It would be perfect on our tablet
[Nexus 7 Original Development] Clamor:
[MENTION=2188693]AndDiSa[/MENTION] Nexus 7 support isn't dropped so far. I'm not UA grouper maintainer, I'm maintainer of Asus Transformers. I'd like to help (our hardware is really close) but I can't till I make a stable N build for my device.

P.S. My experimental builds have many staff working, including wifi.
[Nexus 7 Original Development] dirtyreturn:
Would dirty flashing the ROM help?
[Nexus 7 Original Development] Clamor:
We will try to fix it.

This is known. N builds, unfortunately, aren't currently stable enough.

Since AOSP doesn't support we won't add it either. Main goal of Unlegacy Project is to be as close to AOSP as possible.

This is AOSP keyboard issue, try to use other keyboard.
[Nexus 7 Original Development] Binbin Qian:
I flashed https://builds.unlegacy-android.org/aosp-7.1/grouper/ua_grouper-7.1.2-20180611-1635.zip

But the screen doesn't react from time to time, and now it turned into black, still can see the backlight.
[Nexus 7 Original Development] Clamor:
Yeah, I told Nexus 7 maintainers to look into it. As I said before, I'm maintainer for Asus Transformers and have a lot of issues with them to solve.
[Nexus 7 Original Development] JT1510365:
same here for me will there be a new build with the fix?
[Nexus 7 Original Development] Clamor:
[MENTION=6733022]Binbin Qian[/MENTION] [MENTION=5653319]JT1510365[/MENTION] This state is most likely caused by syncpt crash. We are investigating their causes and evolution N -> O
[Nexus 7 Original Development] Binbin Qian:
Thank you so much, you guys are awesome! I'm very excited to hear that.
[Nexus 7 Original Development] :
Edit: I think I just was setting up OpenGApps strangely. After reinstalling the ROM and the proper OpenGApps, Trusted Face works fine.

Every time I try to use the camera - whether it be the camera app, face unlock, etc - the app I'm using stops. So if I try to set up face unlock, it will crash when it tries to access the camera with the error "unfortunately, Trusted Face has stopped." If I use Camera, I get "unfortunately, Camera has stopped."
[Nexus 7 Original Development] NeoPreacher:
Just recognized a new build on 6 and 7. I'm going to check the 6 build later today and give a little feedback.

EDIT:

it has unofficial securitypatch backport of october patchlevel
[Nexus 7 Original Development] vastus:
Anyone tried 7.1.2 build yet?
[Nexus 7 Original Development] NeoPreacher:
Just thought this project is dead, cuz page is not reachable. BUT, I saw in another subforum that it's a technical problem with the server. Page should be working in the next days again. If someone's curious, now you know ;)
[Nexus 7 Original Development] curioct:
Can anyone tell me if shared memory functions are compiled into these kernels?

Using the grouper nougat build with a chroot filesystem I get

sysctl -w kernel.shmmax=268435456

returns cannot stat /proc/sys/kernel/shmmax: No such file or directory

not sure if that means the function is missing from the kernel or there's another issue? anyone know?
[Nexus 7 Original Development] johndaog:
I tried unlegacy Android 6 latest 201907 release. Was great and fast but drained my battery very rapidly. Only lasts about 12 hours at idle overnight.
[Nexus 7 Original Development] fsw_informatrix:
Unlegacy is a nice project, but if you have a Nexus 7, you really have to try AnDiSa Nougat AOSP here on XDA. In my case, the battery holds 2 days on idle and the last ROM has Google's April security patch :)
[Nexus 7 Original Development] johndaog:
Unlegacy is Great! Thanks Ziyan

I decided to try your Android 6.0 again with my new knowledge of my device.

Now I got it to run very well.

It appears perfect for the Nexus 7 2012.

battery life is good now.

basic steps to increase performance:

setting

turn off optimize brightness

turn off account auto sync

turn off location or battery saver

developer options

animations all set to 0.5 quality

also I only formatted data with F2Fs when flashing

openGapps Pico

after installing cleared cache.

Running really well now. thank you so much.:cool:
[Nexus 7 Original Development] Dreamer...:
Not boot on batteryless device
[Nexus 7 Original Development] steso90:
Hello!

Do anyone have a working link ? :)

@Ziyan
[Nexus 7 Original Development] rahimali:
grouper

tilapia
[Nexus 7 Original Development] steso90:
Thank you!
[Nexus 7 Original Development] Mike7143:
I can't get opengapps pico 7.1 to load, not enough free space on /system

Tried uninstalling some system apps, still can't free up enough space. Any ideas?
[Nexus 7 Original Development] fsw_informatrix:
You should try adding a gapps-config file, like the one linked in this post:

https://xdaforums.com/t/rom-nzh54d-...-ext4-android-7-x-aosp.3467514/#post-68827522

You can tune it even further if you wish:

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Good luck!
[Nexus 7 Original Development] Mike7143:
Already tried that and had everything removed besides "core", still wasn't enough.
[Nexus 7 Original Development] fsw_informatrix:
I didn't test it for now, but BiTGApps seems to be an alternative:

https://xdaforums.com/t/rom-nzh54d-...droid-7-x-aosp.3467514/page-267#post-89373048
[Nexus 7 Original Development] Drexxter22:
Hi!

Somebody keep this rom/kernel (3.4), and can share it?

Download link is dead...
[Nexus 7 Original Development] namerke:
This one did the trick for me too, glitches are now gone.

Is touch boost a simple thing that we can easily cherry-pick from some other 3.4 branch because it is only related to the governor (something like this commit) or is it related to other device specific files/libs ?
[Nexus 7 Original Development] Ophidian_DarkCore:
That commit looks like it references an already implemented touchboost.

See how it just adds an include. The file that it's including I figure doesnt exist in our kernel. So you would look at something like this http://i.imgur.com/PAF13B1.png then open each one and hit history then either cherry pick the commits or hand implement them by copy/paste and look it over(audit) for issues. But usually when you compile it will give you what seems like a vague error(if you are a novice) that will describe what is missing. https://github.com/franciscofranco/flo/commits/lollipop-mr1/include/linux/touchboost.h https://github.com/franciscofranco/flo/commits/lollipop-mr1/drivers/input/touchscreen/touchboost.c
[Nexus 7 Original Development] Ziyan:
Thanks to [MENTION=4619263]sheffzor[/MENTION]'s help, we made some nice progress last week :) he has a 3G variant with the problematic PMIC.

While [MENTION=4693882]HTCDreamOn[/MENTION] is investigating the audio issues, [MENTION=4619263]sheffzor[/MENTION] fixed up baseband (ril) and updated the interactive governor (including touch boost), and in the meanwhile, I merged in kernel/common android-3.4 (including the bcmdhd updates, which was a pain in the ass). Huge steps forward, but there's still a lot of work left. We're looking forward to M + 3.4 ;)
[Nexus 7 Original Development] Indha Lezzio:
I love u guys :)
[Nexus 7 Original Development] Streetwalker:
I've noticed that the magnetic cover sensor doesn't work with this kernel. I might give it a look.
[Nexus 7 Original Development] Traediras:
Wait, Nexus 7 has a magnetic sensor? o_O
[Nexus 7 Original Development] sheffzor:
You might try this branch:

https://github.com/apinela/android_kernel_asus_grouper/tree/grouper-3.4-dev

Magnetic sensor should be working fine,

Test and give us some feedback! :)
[Nexus 7 Original Development] motorazrv3:
My grouper has case that when I open the cover it turns on automatically and turns off when the cover gets closed.
[Nexus 7 Original Development] Streetwalker:
Yes it does, along the left edge of the screen, around the first quarter from the bottom.

I've cherry-picked the relevant commits (c973beb to ea2d69e), but it doesn't seem to work for me.
[Nexus 7 Original Development] Promez:
You guys are really awesome.

Epic work on this kernel and on MM, thank you very much!
[Nexus 7 Original Development] Ophidian_DarkCore:
I am about to ****e mahself. Holy hell that's a lot of work. :thumbsup:
[Nexus 7 Original Development] Traediras:
Well shoot, I'm going to have to find myself a smart cover for the N7 now. :D
[Nexus 7 Original Development] hichris123:
I just built the kernel today (pcbid=0x009e), and got almost the exact same last_kmsg with the stack traces. It seems that the SELinux fix is already in the main branch, so are there any other ideas on why it's still not working?
[Nexus 7 Original Development] Ziyan:
Try powering off your device completely before booting 3.4 (so after flashing), after coming from 3.1.
[Nexus 7 Original Development] hichris123:
No dice. :( Still the same issue.

I've attached /proc/last_kmsg. I think this might be from a second boot I tried, but I'm not positive.
[Nexus 7 Original Development] Ophidian_DarkCore:
Which one of these sources did you compile? https://github.com/Ziyann/android_kernel_asus_grouper/commits/linux-tegra-nv-3.4-grouper https://github.com/apinela/android_kernel_asus_grouper/commits/grouper-3.4-dev

---------- Post added at 08:41 AM ---------- Previous post was at 08:40 AM ----------

@Ziyan What does the working kmsg look like?
[Nexus 7 Original Development] sheffzor:
It should be able to boot doing a clean boot from power off, after flash the kernel.

The kernel is stuck exactly the same place it should be in my tab if I don't do a clean boot.

Definitely, I will check that problem now.
[Nexus 7 Original Development] sheffzor:
And how is the battery with that?

We have updated the interactive gov to the kernel\common 3.4, so the behavior with that specs may vary.

Tanks anyway..
[Nexus 7 Original Development] hichris123:
I just used Ziyann's. Same branch & all.
[Nexus 7 Original Development] TheXorg:
same here. powered device off after flash. i used ramdisk from Minimal OS (marshmallow). any clue? I'm getting that message on all cpus:

[ 28.052958] BUG: soft lockup - CPU#0 stuck for 23s! [migration/0:8]
[ 28.112614] BUG: soft lockup - CPU#1 stuck for 23s! [irq/118-max7766:37]
[ 28.113393] BUG: soft lockup - CPU#2 stuck for 23s! [migration/2:15]
[ 28.114140] BUG: soft lockup - CPU#3 stuck for 23s! [migration/3:20]
[Nexus 7 Original Development] Ophidian_DarkCore:
Isn't there a way to trace this stuff? Like turning on a ridiculous amount of debugging info and use that to decipher?
[Nexus 7 Original Development] sheffzor:
Tomorrow I will look at that.
[Nexus 7 Original Development] Ophidian_DarkCore:
I wonder if it's possible to grep the whole commit history of the original nv 3.1 git to see if the nvidia devs ever had an issue like this when building the kernel for this board? maybe "soft lockup" is a good string?

I think it's probably voltages though.

Maybe disable the watchdog?
[Nexus 7 Original Development] AndDiSa:
As stated here it's not a kernel bug, it's only an indication of heavy I/O load ...
[Nexus 7 Original Development] Ophidian_DarkCore:
It's an indication of a stuck piece of code.(Spinlock?)

"Any code which has acquired a spin-lock and ends up in infinite loop without releasing the lock will result in soft-lock"

I'm gonna check out dwarf to see if that will help in debugging.
[Nexus 7 Original Development] sheffzor:
I'm working on it right now. The problem might be related to the max77663 driver or power initializing @ board files, maybe something missing, I will have to compare cardhu and kai power files that have max77663 with our grouper max pmic file, I will check the driver too and any eventual changes made by asus on that bytes.

It's the place where it is locked is easy to identify, it's on the stack trace:

[ 28.198969] [<c000ea40>] (__irq_svc+0x40/0x70) from [<c07b44a8>] (__raw_spin_lock+0xa0/0xc0)

[ 28.199116] [<c07b44a8>] (__raw_spin_lock+0xa0/0xc0) from [<c07b234c>] (__mutex_lock_slowpath+0xb4/0x1ec)

[ 28.199200] [<c07b234c>] (__mutex_lock_slowpath+0xb4/0x1ec) from [<c07b24d4>] (mutex_lock+0x50/0x54)

https://github.com/apinela/android_.../grouper-3.4/drivers/mfd/max77663-core.c#L334 <---------------------- THIS IS WHERE WE ARE LOCKED

[ 28.199352] [<c07b24d4>] (mutex_lock+0x50/0x54) from [<c03ac278>] (max77663_read+0x34/0xc4)

https://github.com/apinela/android_...per-3.4/drivers/mfd/max77663-core.c#L328-L339

[ 28.199500] [<c03ac278>] (max77663_read+0x34/0xc4) from [<c02e208c>] (max77663_gpio_isr+0x30/0x94)

https://github.com/apinela/android_...er-3.4/drivers/gpio/gpio-max77663.c#L440-L460

[ 28.199644] [<c02e208c>] (max77663_gpio_isr+0x30/0x94) from [<c00c19d8>] (handle_nested_irq+0xa4/0xec)

https://github.com/apinela/android_...per-3.4/drivers/mfd/max77663-core.c#L530-L575

[ 28.199786] [<c00c19d8>] (handle_nested_irq+0xa4/0xec) from [<c03ac4a4>] (max77663_irq+0x19c/0x264)

[ 28.199874] [<c03ac4a4>] (max77663_irq+0x19c/0x264) from [<c00bf708>] (irq_thread+0xec/0x174)

[ 28.200018] [<c00bf708>] (irq_thread+0xec/0x174) from [<c0078994>] (kthread+0xbc/0xc0)

[ 28.200161] [<c0078994>] (kthread+0xbc/0xc0) from [<c000fa1c>] (kernel_thread_exit+0x0/0x8)
[Nexus 7 Original Development] Ophidian_DarkCore:
You are the 2ci-NBome!!!

https://android.googlesource.com/kernel/tegra/+/c31633af769406c48824f97a3fff7afe1ab57a83^!/#F0

---------- Post added at 11:26 AM ---------- Previous post was at 10:57 AM ----------

@TheXorg

Do you have the 32gig also?
[Nexus 7 Original Development] weedy2887:
2-3 days idle.
[Nexus 7 Original Development] sheffzor:
[MENTION=6741818]Ophidian_DarkCore[/MENTION] and [MENTION=5405633]TheXorg[/MENTION], could you please try this:

https://github.com/apinela/android_...mmit/99788a2473702d0b91a25009908ae58fd88f5154

I was able to successfully boot my tilapia with max77663 pmic from kernel 3.1 to kernel 3.4 with that, so try cherry-picking it and rebuild your kernel and give me some feedback!!!
[Nexus 7 Original Development] Ophidian_DarkCore:
It's past the bug, now just selinux issues. updating twrp. Do you get cpu clock setting stack traces? What about regulator complaints. Like Setting clock before regulator is ready may result in overclock?

---------- Post added at 01:04 AM ---------- Previous post was at 12:46 AM ----------

@sheffzor

alright, wtf did i do wrong. i've been out of this game for a couple months now actually. i repacked dimitry's boot img with our zimage, keeping his ramdisk. This is what I get (EDIT: apparently twrp doesnt know how to ****ing sync before exiting)(EDIT EDIT: Alright, got the kmsg redirected. If stupid fackin mount would just create directories dynamically instead of erroring out if a directory doesn't exist, then twrp wouldnt have been designed to have an empty unmounted .... nvm) http://hastebin.com/iparubucuz.xml

---------- Post added at 01:29 AM ---------- Previous post was at 01:04 AM ----------

Thats actually terrible
[Nexus 7 Original Development] sheffzor:
For the regulator not ready, did you cherry-picked my change or are you using my grouper-3.4-dev branch?

This were happening because I've set interactive gov by default on kernel config, so, from the very early boot of kernel, interactive was trying to bump up freq's before pll regulator is initialized.

It is now fixed on my stable branch, no errors:

https://github.com/apinela/android_kernel_asus_grouper/tree/grouper-3.4

The boot problem you're having on M it's because you miss this kernel command line, that is essential for M:

androidboot.hardware=grouper
[Nexus 7 Original Development] Streetwalker:
That's what I've always had. Only problem is, wifi doesn't seem to turn off when the tablet goes into deep sleep even though I turned the option on. When that works, battery lasts weeks if unused.
[Nexus 7 Original Development] Ophidian_DarkCore:
yea, when deep sleep works properly the battery lasts practically forever. thats what i meant :D
[Nexus 7 Original Development] Ophidian_DarkCore:
Boots now, with your commit and the cmdline addition. whats keeping me from bringing the kernel up to 3.4.110? I'm about to start tweaking the hell out of **** if you don't mind a very on the edge derivative.

---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------

the visual artifacts (lines through shadows) are hilarious though.
[Nexus 7 Original Development] sheffzor:
Did you read the OP? ;P

You should go to the downloads section of this thread and download the libnvrm.so and swap it with the on on your ROM...
[Nexus 7 Original Development] weedy2887:
My tablet is the pit that all my junk apps get installed to.

Anything I need randomly for membership points or whatever.

It has like 230 apps installed. I'm not even a little surprised I can only get 3 days out of it. It probably never sleeps.
[Nexus 7 Original Development] Streetwalker:
Mine is freshly factory reset with a few apps installed and it doesn't last longer. It goes into deep sleep but wifi doesn't turn off automatically. I think there might be a missing feature in this kernel that prevents it from turning wifi off during deep sleep. There's an app on F-Droid called wifi automatic which seems to work, I'll see how that goes.
[Nexus 7 Original Development] sheffzor:
There is an option under advanced wifi settings that manage that, it calls "Keep Wi-Fi on during sleep", selections {"Always", "Only when plugged in", "Never"}, by default: "Always".

Since this kernel follows the last Google updates on common kernel 3.4, I will assume that this is the real and normal behavior. :)
[Nexus 7 Original Development] Streetwalker:
That's exactly the option I'm talking about. Not sure if it's CM or this kernel but it's broken for me.
[Nexus 7 Original Development] sheffzor:
I've done a test and no problems at all with wi-fi suspension.

you must be shore that power hals and init scripts aren't messing the kernel 3.4, some sysfs changes happened here and are different from 3.1, so be aware that this wont be a just flashable zip/img, this kernel will need some changes to power hal and init scripts to perform good.

I'm using CM-12.1 with:

- grouper power hal lib removed (so I can play with the sysfs without having it messing my run-time changes);

- init scripts changed (removed all the definitions to sysfs related with interactive gov/cpufreq, cpuidle and cpuquiet);

- sound workaround to avoid sound bug;

- libnvrm.so (fix the graphical glitches);

This is not a daily usable config, since I'm testing to achieve the best tunes for a balanced system so I can persist them over power hal.
[Nexus 7 Original Development] Ophidian_DarkCore:
Now my question is, how would one fix the graphical glitches in recovery? I slipped the kernel into twrp to test out some new filesystems really quick.

Does twrp use the blobs during the build process or something?
[Nexus 7 Original Development] sheffzor:
That is a good point, I'm still on 3.1 in twrp, didn't notice that glitches, [MENTION=2633638]Ziyan[/MENTION]n, do you have 3.4 in your recovery?

That can be related to framebuffer problems that [MENTION=2633638]Ziyan[/MENTION]n got in the early beginning when he brought kernel to boot.
[Nexus 7 Original Development] Streetwalker:
I'm building CM 12.1 with the last two workarounds, I guess your tweaks are what I'm missing.
[Nexus 7 Original Development] Ophidian_DarkCore:
What does that mean?
[Nexus 7 Original Development] Streetwalker:
Was directed at Sheffzor. I build this kernel with CM 12.1, replaced libnvrm.so and applied the audio workaround to my source tree. I haven't made the other two changes he made though in init scripts.
[MENTION=4619263]sheffzor[/MENTION], care to link me your commits or some patches to apply to my source ?
[Nexus 7 Original Development] :
Does this mean there'll be a recovery-flashable zip of this kernel, suitable for use with CM12.1? :D
[Nexus 7 Original Development] Streetwalker:
I have some flashable CM zips that have this kernel built straight in. Not posting them though because I'm too lazy to upload. :P