Email Thread
OP Senior Member
Heidelberg
Thanks Meter: 1,645
 
More
Features
  • unexpected app closes fixed (many thanks to @Ziyan)
  • additional performance tweaks (thanks to @parrotgeek for some special hints)
  • new PerformanceControl application added (based on the version from @daniel_hk)

Installation Instructions
  1. Update Recovery to TWRP 3.1.0
  2. Boot into Recovery
  3. Factory Reset (only needed if you are not already on Android 7 AOSP)
  4. Install SuperUser v2.79SR3 (systemless) (Optional)
  5. Wipe dalvik/cache
  6. Reboot

Important: For more detailed installation instructions please refer to the next post
Important: First boot after upgrading will take a bit longer (stays on ANDROID) because of art optimizations

flash and use on your own risk!

CREDITS,
AOSP/Google, LinageOS, Ziyann for setting up the Grouper-AOSP repository and his Unlegacy Android project, daniel_hk for some hints how to get the 3.1 kernel running with N, timduru for his work on the Asus Transformer, Timur Mehrvarz for his work on the tegra kernel, Francisco Franco for his kernel work in general

Bugs:
  • due to the lack of a Tilapia device, I was not able to test the build, please report issues if you find some
  • mirroring to a Chromecast device is working, but disconnecting by using the notification is blocking the device. Workaround: use the Home.app from google to disconnect the casting.
  • probably some more

Changelog
  • 20170410 (AOSP 7.1.2)
    • NFC fixed (was an issue for Grouper only)
    • SetupWizard crashes hopefully fixed, too
  • 20170409 (AOSP 7.1.2)
    • video crashes fixed
  • 20170407 (AOSP 7.1.2)
    • new release based on 7.1.2_r5, April 2017 security fixes applied
    • huge changes / updates in the kernel to improve performance and battery life time
    • PerformanceControl application added (no further need to use Kernel Adiutor)
    • sudden appplication closes fixed
  • 20170308 (AOSP 7.1.1)
    • new release based on 7.1.1_r25, March 2017 security fixes applied
    • several changes in the kernel
      • zRAM 200MB default enabled
      • lz4 compression algorithm for ramdisk
      • optimizations for interactive governor
      • several optimizations
      • usb hostmode changing patch fixed
  • 20170207 (AOSP 7.1.1)
    • new release based on 7.1.1_r20, February 2017 security fixes applied
    • DRM issues (hopefully) fixed
    • several changes in the kernel
      • compiler changed from gcc-4.9 back to gcc-4.8
      • several security patches
      • several optimizations
      • usb hostmode changing patch added
    • ota update script modified so that /system is formatted before applying a FULL-OTA image
  • 20170105 (AOSP 7.1.1)
    • new release based on 7.1.1_r9, January 2017 security fixes applied
  • 20161213 (AOSP 7.1.1)
    • new release still based on 7.1.1_r4
    • tilapia ril issues fixed (thanks to @millosr)
    • Add CUSTOM_BRIGHTNESS support (used the patch from DC-kernel, thanks to @daniel_hk)
    • camera2 fixed (thanks to @aaopt)
    • missing WallpaperPicker project added
    • using widevine libs from Unlegacy (thanks to @Ziyan)
  • 20161207 (AOSP 7.1.1)
    • new release based on 7.1.1_r4
    • Music app no longer crashing
    • stabilzation, almost no FCs
    • Kernel security patch (CVE-2016-8655) applied
  • 20161127 (AOSP 7.1)
    • new release, first release for Tilapia based on 7.1.0_r5 (thanks to @millosr for providing the tilapia device tree)
    • camera working now
    • Music app no longer crashing
    • overall more stable and much less FCs
  • 20161109 (AOSP 7.1)
    • new release, based on 7.1.0_r5
    • security patch for November applied
    • several security fixes in kernel
  • 20161028 (AOSP 7.1)
    • new release, based on 7.1.0_r4
    • security patch for October applied
    • SELinux in enforcing mode now
    • Dirty COW security patch applied
    • integration of performace tweaks based on ParrodMod, thanks to @parrotgeek1
  • 20161019
    • new release, based on 7.0.0_r14
    • security patch for October applied
    • minor bugfixes (NFC, bluetooth, ...)
  • 20160923
    • initial release, based on 7.0.0_r6

Downloads

Version from 04/10/2017 (7.1.2)
[URL="https://www.androidfilehost.com/?fid=745425885120723367"]Grouper OTA package 20170410/URL]
Tilapia OTA package 20170410
Version from 03/08/2017 (7.1.x)
Grouper OTA package 20170308
Tilapia OTA package 20170308
Version from 02/07/2017 (7.1.x)
Grouper OTA package 20170207
Tilapia OTA package 20170207
Version from 01/05/2017 (7.1.x)
Grouper OTA package 20170105
Tilapia OTA package 20170105
Version from 12/13/2016 (7.1.x)
Grouper OTA package 20161213
Tilapia OTA package 20161213
Version from 12/07/2016 (7.1.x)
Grouper OTA package 20161207
Tilapia OTA package 20161207
Version from 11/27/2016 (7.1.x)
Grouper OTA package 20161127
Tilapia OTA package 20161127
Version from 11/09/2016 (7.1.x)
OTA package 20161109
Version from 10/19/2016
OTA package 20161019
Version from 09/23/2016
OTA package 20160923


Sources
https://github.com/AndDiSa

If you would like to build from the sources, you can do so by cloning and build from repositories:but please take in mind that you need to have some free space (>= 100 GB) and some time ...


XDA:DevDB Information
Android 7.x AOSP, ROM for the Nexus 7

Contributors
AndDiSa
Source Code: https://github.com/AndDiSa?tab=repositories

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: AOSP

Version Information
Status: Beta

Created 2016-09-23
Last Updated 2017-04-11
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20170408-102657.png
Views:	3314
Size:	57.0 KB
ID:	4105248   Click image for larger version

Name:	Screenshot_20170403-205552.png
Views:	3338
Size:	106.9 KB
ID:	4105249  
Quick Reply Reply
2016-09-23, 6:11PM
OP Senior Member
Heidelberg
Thanks Meter: 1,645
 
More
Please note:
  • the system partition is already quite full which leads to the problem that gapps probably will not install correctly and that may lead to weired problems (apps closing / not showing up correctly / ...). I suggest to use the dynamic gapps package linked above. In addition I suggest you to erase the system partition completely before applying the OTA package
  • if you would like to flash SuperSU, I suggest you to use SuperSU 2.79 SR3 in systemless mode. Systemless mode is important because otherwise you may run into bootloops.
    To force systemless installation
    • boot into recovery
    • mount the /data partition
    • open a shell and type the following command
      Code:
      # echo "SYSTEMLESS=true" >/data/.supersu
    • close the shell and install SuperSU
    be aware that wipe will remove the .supersu file, too, so you need to create it again!

Some additional hints
  • If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
  • If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
    Code:
    adb reboot bootloader
    After a few seconds the device should show up the bootloader screen
Quick Reply Reply
2016-09-23, 6:12PM
Member
Thanks Meter: 16
 
More
Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?
Quick Reply Reply
2016-09-23, 7:52PM
Senior Member
Brussels
Thanks Meter: 113
 
More
Quote:
Originally Posted by Nintonito

Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?

Why not figure it out by yourself?
If you flash this ROM you can create a list of what's working and what's not
Anyway, when I'm home, I gonna flash this ROM on my brother's Nexus 7 and give feedback.

Sent from my Nexus 5 using XDA-Developers mobile app
Quick Reply Reply
2016-09-23, 7:58PM
Junior Member
Thanks Meter: 8
 
More
Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
Click image for larger version

Name:	Screenshot_20160923-185842[1].jpg
Views:	2420
Size:	134.1 KB
ID:	3884176

Click image for larger version

Name:	Screenshot_20160923-185855[1].png
Views:	2386
Size:	22.0 KB
ID:	3884177

Click image for larger version

Name:	Screenshot_20160923-185911[2].png
Views:	2378
Size:	58.7 KB
ID:	3884178
Quick Reply Reply
2016-09-23, 8:03PM
OP Senior Member
Heidelberg
Thanks Meter: 1,645
 
More
Thanks, I'll correct the link
Nevertheless your problems I cannot reproduce ... probably because I've done an update installation. I'll have a look at it.
What was the ROM you have had installed before? Did you wipe?
Quick Reply Reply
2016-09-23, 8:09PM
Senior Member
NYC
Thanks Meter: 622
 
More
When i get a chance this weekend I'm going to try this with Phh Superuser and Magisk. That combo is/was working great on your MM rom.
Quick Reply Reply
2016-09-23, 8:25PM
I flashed your ROM with TWRP 3.0.2-0 and after 'Patching system image uncondinionally' i get
Code:
Patching system image uncondinionally...
E:unknown command [log]
E:unknown command [log]
script succeeded: result was [1.000000]
Updating partition detail...
...done
I doublechecked the md5 of the file and reflashed but still no luck.

[Edit]
I rebooted and it seems to run....
[Edit2]
Flashing the plain ROM without the gapps seems to work - but after these gapps it doesnt start.
Quick Reply Reply
2016-09-23, 9:21PM
Senior Member
Thanks Meter: 157
 
More
I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx
Quick Reply Reply
2016-09-23, 10:18PM
Senior Member
Thanks Meter: 157
 
More
Quote:
Originally Posted by tpuserhp

I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx

I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx

---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------

Quote:
Originally Posted by DSTear

Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!

Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx

I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.
Quick Reply Reply
2016-09-23, 11:34PM
OP Senior Member
Heidelberg
Thanks Meter: 1,645
 
More
As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.

Sent from my Nexus 7 using XDA-Developers mobile app
Quick Reply Reply
2016-09-24, 7:23AM
Reply Subscribe

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread