yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] abhifx:
haven't tried it.. is there a problem? last build failed to.. well build. i am eyeing today's build which should contain android 7.1
[Nexus 7 Original Development] abhifx:
drat! jenkins got killed while compiling grouper :/

Edit: and the latest grouper build is not working, signature verification fails with provided recovery and through twrp, it remains stuck at patching system unconditionally. [MENTION=4619263]sheffzor[/MENTION] I know this is not for regular users but any help in going over bleeding edge?

Double Edit: Seems to be fixed with 25th build. kill me. Also if anyone wanted to know, this is still 7.0 build
[Nexus 7 Original Development] abhifx:
just to note that twrp based on 3.4.x kernel keeps getting overridden by stock recovery. maybe we need new recovery or some update with ROM. also.. No Omni or CM?
[Nexus 7 Original Development] erk1725:
Thanks for new build....will try it when i get home tonight hopefully
[Nexus 7 Original Development] akashkyh:
i flashed 27th October build .... was very excited but got stuck with the black screen... :(

Can any1 help me out??
[Nexus 7 Original Development] Nintonito:
Tried October 27 build. Doesn't get past the google logo. TWRP is not overridden but the device won't boot with the rom.
[Nexus 7 Original Development] amaces:
Just curious, does it seem like it's warming up while being stuck? Also, have you tried force powering off, then starting cold?
[Nexus 7 Original Development] Nintonito:
It's a completely cold start, device remains cold.
[Nexus 7 Original Development] scotte9999:
I installed the 2016-10-28 build on my Grouper, and it gets at least to the "android" screen. adb lolcat shows that it's busy JIT'ing the applications, so I think it's working.

Note that I used the TWRP with the 3.4 kernel in the OP, and (because TWRP kept telling me there was no OS installed) I flashed the boot.img via fastboot. I used the Pico OpenGAPPS from 2016-10-28 as well.

Seems like it's working fine. Logged in, installed a few apps (Chrome, keyboard, Maps, Photos, Google Now Launcher) and it's all good.

Lots of debug output, but clearly usable.
[Nexus 7 Original Development] dareino:
So I made a stab at this...was already rooted, running latest twrp...I too was stuck at google screen for a 5min but then I just rebooted and it was fine. No twrp, had to adb it over.

It wont install the gapps tho, tried twice.....everything else seems fine

d

**edit*..ok so play store appeared and I had to log in so its somewhat working but not d/l any of my previous apps.....
[Nexus 7 Original Development] pincher65:
1 wipe в TWRP

2 reboot recovery

3 instal ROM

4 reboot in OC (everything was loaded quickly, it is possible to include WiFi at once )

5 reboot recovery and install Gaps (open gapps pico 28102016)

6 reboot OC

7 reboot recovery and instal superSU

everything works perfectly. thanks for your hard work
[Nexus 7 Original Development] giannibat:
Installing kernel+TWRP was ok; then installed for the first time the ROM but was stuck on 'android' logo, so I formatted data to ext4 and now booting without gapps. Tried installing gapps and stuck again on 'android' logo. All partitions now are ext4 but no boot trying to install gapps.

EDIT: problem solved, wiping partitiong and downloading gapps again.
[Nexus 7 Original Development] eNVy:
Can you build a cm14 rom for grouper ?
[Nexus 7 Original Development] abhifx:
hey devs! i know this is a pure aosp project, but in case you are building anything other than aosp, can you please make a rom with navigation bar control in system ui tuner? that way we can add volume etc button which is useful for car install
[Nexus 7 Original Development] akashkyh:
Can you elaborate "OC" ?

Plz help me to install correctly
[Nexus 7 Original Development] pincher65:
reboot system in twrp ;)
[Nexus 7 Original Development] Aceracer27:
How long is boot time after flashing Super SU? Seems to hang at boatloader unless I interrupt it. (power off) And has anyone tried Parrotmod? I can't get it to install. Using TWRP latest.
[Nexus 7 Original Development] pincher65:
3-5 minutes

the last (14.10.16) works well
[Nexus 7 Original Development] Flowah123:
Does Phh's SuperUser works? Or is it only for Chainfire's SuperSU?
[Nexus 7 Original Development] chosin137:
I can confirm the 28th 7.1 AOSP build still is getting stuck at the Android logo screen. Sideloading through ADB and flashing boot.img via fastboot does not work. Are you using F2FS on data and cache? What version of SuperSU are you using? I also rebooted to recovery when installing OpenGapps 7.1 and SuperSU 2.78. I noticed during installation getting two error messages of cannot find E:/

---------- Post added at 04:35 AM ---------- Previous post was at 04:07 AM ----------

I have discovered the issue! This newer Rom is incompatible with F2FS /data /cache
[Nexus 7 Original Development] abhifx:
jenkins is producing more recent builds if you want to try that.. i am on ext4 however
[Nexus 7 Original Development] n3kf:
I know that this is a development thread, so excuse the question. Is anyone using this as a daily driver for their grouper? If so, what build are you using? I see some seen to be OK, others not so much. Thank you and great job here....
[Nexus 7 Original Development] Aceracer27:
Latest update is awesome great work.
[Nexus 7 Original Development] chosin137:
It's not a daily driver yet. If you follow the directions exactly you can get it running on EXT4 with the Android 7.1 AOSP build but its not working with F2FS formatted /cache and /data. I'm stilling seeing some menus and apps crashing back to home screen though so I wouldn't say it's ready for primetime. What I can say is it runs a lot better than the older roms especially with parrotmod.
[Nexus 7 Original Development] sheffzor:
Guys, just a note, cache will not support f2fs since it is not used @ runtime, it will only be used for FOTA upgrades(that we will include soon), if it is formated in f2fs with twrp, it will lead to a bootloop, only data partition is able to be mounted in f2fs.
[Nexus 7 Original Development] Nintonito:
Wait OTA's are on the way and TWRP flashing is still broken in this rom? :(
[Nexus 7 Original Development] abhifx:
TWRP works from OP. Except that it gets overwritten by stock recovery. flashed latest nightly and everything is fine
[Nexus 7 Original Development] n3kf:
Was playing some, so took my 32gb grouper and wiped the whole device and put this ROM on it. Nothing unusual except what has been mentioned above. Very responsive ROM. Nice job! Reloaded my apps. Still pretty responsive. However, a lot of times when I started an app the device would reboot. Still, looking good and will be looking forward for it to settle down and get more stable. Thanks
[Nexus 7 Original Development] chosin137:
Make sure you have SuperSU 2.78 running, that seemed to stop the reboots for me. I'm also not sure F2FS on /DATA is really worth the hassle since it usually causes more issues with TWRP and bootloops. So far even Chrome has been really responsive which has been the main sticking point with Android 6 + ParrotMod for me. I think as long as one doesn't bloat it up with multiple chat clients and or Facebook this should work quite well now.
[Nexus 7 Original Development] n3kf:
Yep, been using 2.78 since it was out. I moved back to a marshmallow build cause that is more stable. I get reboots on every Nougat build, but this one was not really usable. Also FCs. I did not expect it to be stable, but figured I'd play with it. I don't use any chat clients. Facebook actually ran quite well. Anyway, back on a marshmallow ROM and my grouper is rock stable. No FCs or reboots.

And yes it was a complete wipe before the install.
[Nexus 7 Original Development] abhifx:
on 07.11.2016 build, everything is great. i still wish i could get navigation bar settings in system tuner. apart from occasional app crashes, tablet is flying, has performance tune being done or is it already done?
[Nexus 7 Original Development] armada786:
I don't know if this is an anomaly, but although the battery icon changed when plugging into AC, my Nexus 7 would not actually charge and battery stats would say "not charging." Using Ampre I was able to see it wasn't drawing current either, despite being plugged in. It would charge while off and also while in recovery. Flashing another 7.1 fixed the problem. I wasn't able to get any useful information like logs, but I thought I would share this issue anyway.

EDIT: It was the 10/27 build. I haven't installed any newer versions because I want to be able to charge my tablet.
[Nexus 7 Original Development] eNVy:
Can you build a cm14 version for grouper ?
[Nexus 7 Original Development] abhifx:
i have charging issue too but that seems more like hardware issue as it is with every rom i tried. however, the tablet do charge. so i doubt rom is causing not to charge your tablet. you also might consider hardware issue (usb port defect which is frankly common in our stupid tablet).

---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------

cm14.1 is not even out now yet (it *might* be out for few devices from today). So no use in compiling a rom which is still in heavy development. devs might want to perfect AOSP first before going CM or Omni route.
[Nexus 7 Original Development] supertiger1234:
YouTube's ui is so laggy and the app crashes all the time. Any fix? :D
[Nexus 7 Original Development] abhifx:
Probably something to do with OMX as i am also getting crash with android auto.

Logact shows something like this:

11-11 12:07:09.022 19269 19302 W CAR.GH : 12:07:08.467 : V GH.PerformanceMonitor : Metric(STARTUP_GEARHEAD_APPLICATION_CREATED) took 225 ms.
11-11 12:07:09.023 19269 19302 W CAR.GH : 12:07:08.469 : I GH.CONFIG : groups:
11-11 12:07:09.024 19269 19302 W CAR.GH : 12:07:08.530 : V CAR.GH : onCreate completed
11-11 12:07:09.025 19269 19302 W CAR.GH : 12:07:08.544 : V GH.SetupActivity : onCreate
11-11 12:07:09.026 19269 19302 W CAR.GH : 12:07:08.572 : V GH.FRX : onActivityCreated
11-11 12:07:09.026 19269 19302 W CAR.GH : 12:07:08.584 : V GH.SetupActivity : onResume
11-11 12:07:09.027 19269 19302 W CAR.GH : 12:07:08.585 : V GH.FRX : onResume
11-11 12:07:09.027 19269 19302 W CAR.GH : 12:07:08.613 : V GH.SharedServiceConnect : Service connected
11-11 12:07:09.028 19269 19302 W CAR.GH : 12:07:08.615 : V GH.Telemetry : Logged 1 events.
11-11 12:07:09.031 19269 19302 E CAR.GH : Terminating process
11-11 12:07:09.032 19269 19302 I Process : Sending signal. PID: 19269 SIG: 9
11-11 12:07:09.046 429 4222 D GraphicsStats: Buffer count: 6
11-11 12:07:09.046 429 4424 I WindowManager: WIN DEATH: Window{c41a5c8 u0 com.google.android.projection.gearhead/com.google.android.projection.gearhead.frx.SetupActivity}
11-11 12:07:09.047 145 626 E OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything...
11-11 12:07:09.047 18199 18212 I CAR.SERVICE: A car connection listener died.
11-11 12:07:09.048 429 441 I ActivityManager: Process com.google.android.projection.gearhead:projection (pid 19269) has died
11-11 12:07:09.048 429 441 D ActivityManager: cleanUpApplicationRecord -- 19269
11-11 12:07:09.048 429 4424 I WindowManager: Destroying surface Surface(name=com.google.android.projection.gearhead/com.google.android.projection.gearhead.frx.SetupActivity) called by com.android.server.wm.WindowStateAnimator.destroySurface:2033 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:884 com.android.server.wm.WindowState.removeLocked:1471 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2487 com.android.server.wm.WindowManagerService.removeWindowLocked:2445 com.android.server.wm.WindowState$DeathRecipient.binderDied:1802 android.os.BinderProxy.sendDeathNotice:688 <bottom of call stack>
11-11 12:07:09.049 429 441 W ActivityManager: Force removing ActivityRecord{8733e14 u0 com.google.android.projection.gearhead/.frx.SetupActivity t22}: app died, no saved state
11-11 12:07:09.075 18165 18165 E GH.VnLaunchPadActivity: FRX failed to complete, cant launch vanagon
11-11 12:07:09.116 18010 18010 V Launcher: [onWindowFocusChanged]: true, takes: 0ms
[Nexus 7 Original Development] supertiger1234:
What is OMX? Any way to fix it? :D
[Nexus 7 Original Development] um.z:
Has someone been building CM13 roms with this kernel lately, or are the August ones the latest CM13 builds available?
[Nexus 7 Original Development] Sage:
anyone advise how this compares to SlimKAT 4.4.4? (or any other 4.4.4 rom for that matter). Everytime i got to 5.x or 6.x i regret it - just too slow.

Can i also ask if the kernel supports overclocking too? Always nice to have on the ol nexus..
[Nexus 7 Original Development] chosin137:
The Kernel change to 3.4 is what makes the difference. 7.1 is just a side benefit. No there is no overclocking built into this Kernel and frankly it doesn't need it. I ran Pure Nexus 6.x builds with Parrot Mod and DC kernel before this and it was moderately fast but still a little slow with things like Chrome. AOSP 7.1 with the 3.4 Kernel makes the tablet completely usable again.
[Nexus 7 Original Development] adstraylight:
Is there still a problem with certain hardware variants not being able to boot? Last time I tried I couldn't even get the recovery to start, and flashing the ROM in standard TWRP gave me black screen on reboot, but that was some time ago.
[Nexus 7 Original Development] fadern:
Hi,

my grouper won't see any 5Ghz channels. I dont know if there is a lack of hw support for 5Ghz channels or if it's the rom. Any ideas?
[Nexus 7 Original Development] adeelraj:
grouper doest have 5ghz wifi

---------- Post added at 03:55 PM ---------- Previous post was at 03:55 PM ----------

same here brother
[Nexus 7 Original Development] fadern:
ok, thnx
[Nexus 7 Original Development] gusto5:
I do notice that when I install an update, I do have to cold start (power off and the power back on), otherwise it will get stuck on the google logo.
[Nexus 7 Original Development] abhifx:
its and interface for audio, video and image processing. devs have fixed omx before and i suppose they will do it again even though we don't have new binaries.
[Nexus 7 Original Development] Sage:
all i can say is wow. never seen my tablet work so quick! been watching the thread for over a year.. amazing devotion from an amazing developer. well done and thank you. does the tablet still need TRIM?
[Nexus 7 Original Development] abhifx:
as the developer [MENTION=4619263]sheffzor[/MENTION] has said, all variants should be fixed. However, you should try and revert back in case things go other way.
[Nexus 7 Original Development] adstraylight:
Ok, so just one more question, is it necessary to use the version of TWRP listed in the OP, as I don't think this has been updated since I last tried, and couldn't make it boot, or can I use the (3.1) standard TWRP to flash the ROM?
[Nexus 7 Original Development] abhifx:
Nope.. it does work though. but if you want the XDA way.. flash the recovery from here

http://jenkins.unlegacy-android.cf/job/android/

flash through fastboot

go to recovery and sideload the zip file. this will boot nougat 7.1 but with no gapps.

but if you want gapps then you will have to use TWRP

---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------

on the sad note... there does not seems to be much activity at gerrit regarding ulegacy android, let alone grouper. Technically nothing much has changed for us from 10.11.2016. if people are flashing blindly then its a bummer news for them.

good thing is there are tons of commits for grouper still open for merging, maybe lot more fun stuff will be there in the near future.
[Nexus 7 Original Development] kalafior12:
Two questions to be sure:

1. Which version should I install (dated on what day)?

2. is the recommended version now compatible with f2fs data and cache?

Thx

Wysłane z mojego LG-D855 przy użyciu Tapatalka
[Nexus 7 Original Development] Sage:
i just went the most recent. works well. though i still think it would be better with some overclocking freqs available :)
[Nexus 7 Original Development] n3kf:
So are people using parrotmod on this, or is the ROM fairly responsive without it? Any other tweaks being used like setting background processes to 3 or 4 in developer options? Many FCs or reboots or running fairly well? Thanks
[Nexus 7 Original Development] abhifx:
any latest build will do

http://builds.unlegacy-android.cf/aosp-7.1/grouper/

It does seems latest one are bit more unstable but still this can be used as daily driver.

However nothing has changed for us from 10.11.2016 so your choice. flash away.

Also F2FS on data should work. Not on cache or system
[Nexus 7 Original Development] kalafior12:
Wow, im realy impressed ! So smooooth ! Great job ! I hope my old nexus be the same after few weeks. Regards

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Nexus 7 Original Development] Sage:
I am not using parrotmod. I have upped the min CPU from 51 to 204mhz and added limit of background process to 4. it was good before now its very good. I do get quite a few FCs on all different apps though..

I would like to know if TRIM is needed and init.d works
[Nexus 7 Original Development] n3kf:
Thanks. I tried this about a month ago. I did a clean install, but then bought my apps back in with titanium. I was getting a lot of FCs also. Enough that I really did not want to put up with it, so went back to marshmallow. I have heard some people saying not to restore data with titanium, as that will cause the FCs. Done it that way hundreds of times before and never had issues. I seem to find I was getting FCs on any Nougat ROM I tried. Would really like to know if there are people running the ROM that are not getting FCs. And which version they are running. 16gb or 32gb. I have a 32gb.

As for the trim, since that has to do with the flash memory, I would think it would be a good thing to do since groupers seem to have flash issues.
[Nexus 7 Original Development] kalafior12:
I wonder which version has the shortest charging time. I have a version 15.11 and charging takes 12 hours :(

Wysłane z mojego LG-D855 przy użyciu Tapatalka
[Nexus 7 Original Development] gorneman:
Hi, for apps that crashes a lot I have found on the forum (parrotmod section) this command (in a root shell):

service call SurfaceFlinger 1009 i32 1

it seems to help.
[Nexus 7 Original Development] adstraylight:
Really, that's interesting, I've been looking into this myself but the ROM I'm running throws an error when I try to use this command. Apparently what it does is disable the ”transformation hint", which as I understand it is some kind of pre-buffering of visual effects involving transparency such as the rotation animation.

Do keep us informed, as I'd be very interested to know how much it helps with the random app crashes that seem to affect all the 7.1 ROMs for the grouper.
[Nexus 7 Original Development] vocoderism:
Please for random FC post full logcat to investigate

Sent from Tapatalk on Nexus5x
[Nexus 7 Original Development] tpuserhp:
What is the command result you got back? I got Parcel(NULL) back. I'm running CarbonROM. Most of my crashes are pointing to webview from the microdump. But after using ksm, zram, and scrolling cache, I have not got a crash for several hours. It could be a flute.
[Nexus 7 Original Development] gorneman:
Result of command is Parcel(NULL). Touch is a bit slow to respond. I had to uninstall nova launcher because it crashed, but other apps (Spotify for example) don't. [MENTION=4831205]vocoderism[/MENTION]: asap I'll post a logcat.
[Nexus 7 Original Development] adstraylight:
Check out Nova Beta, it's running very well for me on a 3.1 based 7.1 ROM.

Yes In pretty sure Parcel(NULL) is the correct response, I've just got it to run on my ROM via an init.d emulator, so I can test it too ?
[Nexus 7 Original Development] gorneman:
Some Google Play crash. Log files attached.
[Nexus 7 Original Development] Sage:
yeah i got a lot of FCs in lots of apps. (20161114) Clean install and i didnt restore anything with titanium etc.. is the MM version more stable than the N?
[Nexus 7 Original Development] n3kf:
I'm running this mm ROM. It's fast and extremely stable. Use parrotmod. However, no longer being updated. It's hard to move to an N ROM and put up with all the FCs they have. Some day it will quiet down I hope and I'll move again.

http://xdaforums.com/nexus-7/development/unofficial-pure-nexus-project-layers-t3243943/page107
[Nexus 7 Original Development] abhifx:
while it is true that N build is unstable than Mm build, but has anyone tried posting bug report as given in OP i.e. http://bugs.unlegacy-android.cf/

this should help the devs fix the issue and make N even more stable than MM build (its already faster than MM build)
[Nexus 7 Original Development] Aceracer27:
.

Irrelevant comment when you are referring to an old version of this Rom. Try the latest before giving feedback.

I'm enjoying my tablet for the first time since 2013. Bloody great work developers! Many thanks.
[Nexus 7 Original Development] n3kf:
So, out of interest, which version of tablet do you have? 8gb, 16gb, or 32gb. It seems like there was variations in the types of flash used. I have a 32gb version and it does not matter which version of the ROM I use. I get a ton of FCs. But it is not just this ROM. I get this on any Nougat ROM. OK, if I want to start an app 3 or 4 times, it will eventually run. I just don't have to time to collect a bunch of logs, wish I did. On my tablet, MM runs very well. So don't tell me what's irrelevant. I have tested most of the versions and get the same result. Might work for you, but does not work for me. I'd like to know a technical reason why instead of someone just saying irrelevant......

On top of this, this is a developers thread and I am aware of that.
[Nexus 7 Original Development] Aceracer27:
16GB. Too bad you can't enjoy this awesome rom.
[Nexus 7 Original Development] n3kf:
And that confirms what I have read in the past. That the 16gb and 8gb models don't suffer with some of the issues that the 32gb does. I just wish that everyone who successfully runs the ROM would post what version it is. That would give developers a technical issue they could go after. Or maybe people with 32gb versions are just out of luck.

Once that would be known I would certainly be willing to work with a developer to try and figure out why this is happening.
[Nexus 7 Original Development] tpuserhp:
My grouper is a 32GB device. I only encounter an app with FC when scrolling the screen. If I wait a few seconds after opening that app, I don't have a FC. This could be a problem with the app. Since I can manage the FC for one app, it is not an issue for me.

Not sure which apps gave you FC problems.

With parrotmod changes applied, the grouper performs well under 7.1.
[Nexus 7 Original Development] Sage:
your comment is just as irrelevant.. the ROM version was current at the time of posting..

mine is the 32gb version too.. seems like that maybe the culprit.. ill drop back to MM for awhile.
[Nexus 7 Original Development] n3kf:
Many. Maildroid, chrome, playstore, maps, esfileexplorer, Facebook, and I could go on. These all work perfectly fine on my n7 flo running a Nougat ROM. And I could note that if I keep restarting the apps, they sooner or later will run fine....

I'm a Linux developer, so some day, when I have time I'll root through the logs and see if there is a common reason for the FCs.
[Nexus 7 Original Development] tpuserhp:
All the apps that you mentioned with the exception of facebook and maildroid (i use gmail) are running fine on my grouper. Facebook is resource intensive so I did not install it.

Something does not look right.

I would uninstall facebook first and see if this helps.

I seem to have read that you did a clean install. I guess it is wiping system, caches and data before flashing rom and gapps.

You might want to use Titanium to restore the apps only. One app like Waze crashes if I restore both app and data.

I hope this helps.
[Nexus 7 Original Development] gorneman:
Here is a zip based on parrotmod. It seems to improve performance. Flash in recovery. Please, be careful, make a backup first and don't blame me, this is released as is