yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] AICProcks!:
Are you using the newest TWRP from https://dl.twrp.me/grouper/twrp-3.2.1-0-grouper.img.html?

You should try formatting System, Data, Cache, Dalvic Cache, and Internal Storage. Make sure System is EXT4. Data and Cache can be F2FS or EXT4.

I only had luck installing the smallest Open Gapps Pico with the open gapps fix zip. Maybe you should try an older Open Gapps Pico, like the one from January 19, 2018: https://github.com/opengapps/arm/releases/download/20180119/open_gapps-arm-7.1-pico-20180119.zip

Ultimately, I think you are safe in trying an older crDroid Grouper version since all of them have the October WiFi safety patch on them, although there was a vulnerability in January.
[Nexus 7 Android Development] Crafty77:
Thanks for your help, so I might have told a white lie earlier - I said I was using TWRP, but I was actually using CWM, mindlessly wrote the wrong one.

Changed to TWRP and everything worked on the first try, I guess CWM doesn't play nicely for some reason. Hope that helps someone else.
[Nexus 7 Android Development] AICProcks!:
Thanks for letting everyone know. I guess I should remove CWM from the first post's instructions, then. :D
[Nexus 7 Android Development] grzesoliwka:
Hello,

Could somebady can help, I just try install this ROM and I made big mistake.....

I've instaled TWRP made a backup,

-copy rom amd gaaps to storage

-wipe system, data and cache

-I also chnhe format Data and Cache partitions to F2FS

Now when I want to flash rom no zip, no bacup, everything is cleen :(

I have only TWRP may I do something ?

My PC don't see Nexus.

Please help, my son will kill me........
[Nexus 7 Android Development] AICProcks!:
I am assuming you wiped the Storage as well.

You should boot into TWRP and then connect the tablet to your computer. It should show up. If it doesn't, assuming you're on Windows, go into Device Manager and check if the tablet is being detected. You might need to "update" the driver in Device Manager. But, eventually, you will be able to copy and paste the rom and gaaps to storage from your computer. You could also try to ADB push the files.

Also, the tablet driver might take a while to install if it does so automatically.
[Nexus 7 Android Development] grzesoliwka:
Many Thanks crDroid zip flashed, only with nano gapps problem, I cannot flashed, I get Error code 70 unmounting / system

Data and Cache partitions to F2FS as recomended
[Nexus 7 Android Development] AICProcks!:
So it looks like you solved the problem with your computer not detecting the tablet. Regarding the Nano Gapps problem, Error code 70 is "Insufficient storage space available in system partition." The System partition is too small for Nano Gapps. I myself even had trouble installing Pico Gapps with the Open Gapps System Size Fix I posted in the first post.

However, you can remove some System apps before installing Nano Gapps to try to install it. It might give enough space. You can remove the System apps you don't need either by rooting and through ES File Explorer or some other System app remover. Or, you can simply flash the following zip in TWRP that I created to remove the System apps that I don't use.

You can flash the following System App debloater zip in TWRP that I made based on [MENTION=6303197]lieferant[/MENTION]'s original zip: https://www.androidfilehost.com/?fid=746010030569951230. Since I don't use the following System apps, I uninstalled them with the zip: Calendar, crDroidFileManager, crDroidMusic, Email, crDroidWallpapers, Browser, BasicDreams, LiveWallpapersPicker, AudioFX, and Jelly. In addition to these apps, I also manually removed Trebuchet since I use Nova Launcher. I also removed the default LatinIME keyboard since I use Gboard keyboard.

After removing these 12 System apps the System partition has 188 MB free. :highfive: But, I am not sure if that's even enough for Nano Gapps. I think you would still need to use the Open Gapps System Size Fix to remove some of those extra Gapps.
[Nexus 7 Android Development] grzesoliwka:
Many, many, many Thanks !

Your script working fine, allow me instal gapps pico without any issue :)
[Nexus 7 Android Development] grzesoliwka:
Hi, I just tested the rom, I like it very much ;) thank you for good job.

I have only a question refarding the issue related with game " stickman shooter elite strike force" every time I have crush during loading, tablet tootaly frozen and I have restart.

What reason can be ? I 've not rooted.

Data and Cache partitions in F2FS format.

I am not expert and cannot find root couse.

Could someone try to install this game and check it please ? This is not so havy game, so it's strange for me.......
[Nexus 7 Android Development] AICProcks!:
Okay, so I just tried this game 3 times, and each time it made the tablet completely stuck while loading. I held the power button for like 5 minutes until the tablet finally rebooted. It looks like Stickman uses a lot of RAM memory. :eek:
[Nexus 7 Android Development] grzesoliwka:
Many thanks for the test, I have exactly the same.

Do you think that can be difference with format of Data and Cache partitions in Ext 4 ? or this is just RAM problem nothing can do more ?
[Nexus 7 Android Development] AICProcks!:
F2FS is in theory faster than EXT4 because it does fstrim automatically.

You can try to find a RAM booster app such as "Greenify" and force quit all of your running apps besides the Android system. Just for your information, Android manages RAM differently than a normal computer so these RAM booster apps might be a placebo effect.

And also, you can change the resolution of the screen to a bad quality which should also in theory give more FPS frames per second. You can do this with SebGameMode app from https://xdaforums.com/showpost.php?p=68159266&postcount=74 but it requires root. If you decide to use this app as reference, for example, check mark to "Keep Aspect Ratio." What this app does is simply override the screen resolution via "wm size" and "wm density", which you can also do on your own in ADB shell or terminal. But this app may give you problems with the Power button when screen is off. The default resolution of Grouper is 1280x800 @ 213 density.

NOMone Resolution Changer app from the Google Play Store doesn't work for me, but NOMone made a note of the impact of screen resolution on FPS:

"34.1 fps at 1280x800

41.2 fps at 1024x640

47.0 fps at 800x500

49.0 fps at 480x300".

Rooting the tablet is very simple. Just flash SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip in TWRP and reboot.
[Nexus 7 Android Development] CamoGeko:
[MENTION=8323115]AICProcks![/MENTION]

Hey mate, any chance its possible to make this kernel boot on crDroid?? I tried last night with 3.8.5 and it just wouldn't boot sadly.

https://xdaforums.com/showpost.php?p=75004536&postcount=231

I'd love to have DT2W, and the possibility to OC.
[Nexus 7 Android Development] AICProcks!:
[MENTION=3301438]geko95gek[/MENTION] If you are talking about getting DC Kernel to work with this rom, I might have a build up in an hour or two with DC Kernel on it. However, you would be the first one to test it. :D If it manages to boot, I am expecting a lot of UI crashes, but maybe not. We will see...
[Nexus 7 Android Development] CamoGeko:
Yeah DC Kernel, would be really cool if you can incorporate that kernel into this ROM.

I'm happy to test it if you need. I have a feeling it will work just fine. :good: :D
[Nexus 7 Android Development] apocalypsenzn:
I'll test it today... praying to work :)

I've no data in this tablet, so I can test with my confidence that I'll not lost anything.

I wan't to put it in my car and Android 7.1.2 should be amazing (more than the actualy AOSP)

---------- Post added at 09:26 PM ---------- Previous post was at 09:19 PM ----------

Damn :( this rom is for grouper only :'(
[Nexus 7 Android Development] AICProcks!:
If you have Tilapia, just flash TWRP Grouper, and this rom will work; at least, the current available crDroid. Don't know about DC Kernel. :D Unless, of course, you need 3g.

I tried multiple times, with many different settings, to make crDroid available for Tilapia 3g, but it just refuses to build.

By the way, the DC Kernel rom will probably be up in 4 hours. Sorry to keep you waiting.
[Nexus 7 Android Development] CamoGeko:
[MENTION=8323115]AICProcks![/MENTION] Okay no worries, I'll test it tomorrow then. Its already late here.

Looking forward to it though.
[Nexus 7 Android Development] AICProcks!:
DC Kernel for crDroid

Okay, so my original plan failed to compile a new crDroid rom with DC Kernel. Then my backup plan to compile wilmsn's android_kernel_asus_grouper based on DC Kernel also failed with the same error.

As a last resort, I grabbed the boot.img from [MENTION=5880132]wilmsn[/MENTION] - December 2017 - Resurrection Remix 5.8.5 rom, and put it inside the DC-N-kernel-20170708-grouper zip by [MENTION=2311359]gps3dx[/MENTION]. And sure enough, it worked. The tablet booted with [MENTION=5880132]wilmsn[/MENTION] DC based Kernel. The PerformanceControl.apk was also outdated, so I updated it in case anyone was planning to use it. There are other apps that you can use, but this one seems to work just fine.

DC Kernel Installation:

1. To install DC Kernel on crDroid, you just need to flash this DC-N-kernel-20180220-grouper.zip.

2. Then, you need to root Grouper again by flashing SuperSU.

3. Rooting is needed for PerformanceControl.apk, and you need to Grant it Permission. (After granting it permission, I had to force close PerformanceControl.apk, but then it worked.)

Feedback after Flashing DC Kernel:

1. One of the first things I noticed is that the Power button was not responding as well.

2. Even though I set an overclock to 1.7 Ghz, the tablet only achieved 1.5 Ghz. You may need to adjust the voltage to achieve a higher overclock.

3. For some reason, one of my apps began force closing. Might just need to reinstall it.

4. The tablet is a little warmer for obvious reasons.

5. But yes, did I mention the Power button? :silly:
[Nexus 7 Android Development] CamoGeko:
Thanks for going through the trouble of making it work! I appreciate it.

What I did:

Flashed the kernel zip.

Flashed Magisk 15.3 for root.

Booted no problem. Magisk works fine, so does root.

Clock freq adjustable.

Undervolting possible.

Some issues:

The performance control app doesn't work for me. Keeps saying no root/no busybox installed, which is weird. This isn't too much of an issue because I use a custom version of the Kernel Auditor to control the kernel.

There's no DT2W option, which is why I wanted to run this kernel in the first place. I think the DC kernel from Carbon N ROM has it.

PS. I don't have any lag with the power button, it works almost instantaneously for me.
[Nexus 7 Android Development] johniem:
My nexus 7 doesn't wake up with this rom.

Anyone knows how to solve this issue?
[Nexus 7 Android Development] AICProcks!:
[MENTION=3301438]geko95gek[/MENTION] So I figured out how to add DT2W support to this rom, but now the regular build is failing. I need to figure out what's wrong with this build process. I keep getting a "build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed" error. I have a feeling its because the newest 'cm-14.1' wasn't merged into 7.1 crDroid source yet.

[MENTION=5564834]johniem[/MENTION] I also have a similar problem with the Power button not waking up the tablet. But, after a few restarts, it starts working correctly again. Try plugging in the tablet to wake it up, and restart it.

If you continue having problems with the tablet waking up with the Power button, try enabling the option to wake the tablet with the Volume button. Its a workaround, but works flawlessly. Enable it in Settings> crDroid Settings> Buttons> Wake device (underneath Volume buttons).
[Nexus 7 Android Development] apocalypsenzn:
But I've got a error for flash, it says that's not for your device. it is for grouper.
[Nexus 7 Android Development] AICProcks!:
Are you sure that you flashed TWRP for Grouper because you need to in this case?
[Nexus 7 Android Development] johniem:
[MENTION=5564834]johniem[/MENTION] I also have a similar problem with the Power button not waking up the tablet. But, after a few restarts, it starts working correctly again. Try plugging in the tablet to wake it up, and restart it.

If you continue having problems with the tablet waking up with the Power button, try enabling the option to wake the tablet with the Volume button. Its a workaround, but works flawlessly. Enable it in Settings> crDroid Settings> Buttons> Wake device (underneath Volume buttons).[/QUOTE]

Still the tablet doesn't wake. It's like it dies after some seconds while in sleep mode. I have to press the power button for some seconds to restart it.

Any other workarounds?
[Nexus 7 Android Development] AICProcks!:
Still the tablet doesn't wake. It's like it dies after some seconds while in sleep mode. I have to press the power button for some seconds to restart it.

Any other workarounds?[/QUOTE]

[MENTION=5564834]johniem[/MENTION] Unfortunately, that's the same problem I am having from time to time, but this just started happening after I flashed DC Kernel. Did you also flash it? But, I even restarted the tablet with the latest build without DC Kernel, and this problem persists. This leads me to believe that there might be a problem in the latest build. I hate to say this, but try installing the very first build from November 2017 to see if this problem persists. Before this week, the first build I ever installed on my tablet was the November 2017 build, and I just kept updating it to the present January 2018 build so maybe the problem wasn't present on my end, but now it is since I restarted the tablet with the newest build.

By the way, I recall experiencing this problem in the past with this tablet, but I just don't remember which rom I was using. It might have been Lineage OS or Resurrection Remix. Every concurrent update would inadvertently "solve" this problem. And every other subsequent update, the bug reappeared. I even experienced this error on my phone, which also had Lineage OS and Resurrection Remix. crDroid is based on Lineage OS. The optional DC Kernel is from the Resurrection Remix rom. But, Resurrection Remix is also based on Lineage OS. To make matters even more complicated, not everyone experiences this error.

If I recall correctly, I started experiencing this random error after Deep Sleep was introduced to the present Android versions. But, I also noticed that different Open Gapps versions give me this issue. Now, I even have a random Sign In issue with Open Gapps.

I have a feeling this error might be caused by Wake Lock from different apps, but I suspect Open Gapps. If you search on Google, you can see that this problem is real, and there might be a solution on the last post here: https://android.stackexchange.com/questions/69297/nexus-4-does-not-wake-up-from-sleep-randomly

By the way, I looked at your post history, and I see that you had this problem with a lot of roms above Android 5 on Grouper :eek:. Like the link above says, try out Wake Lock - PowerManager by darken. Use the

Partial Wake Lock

setting, and see if that helps. I am trying it out myself.
[Nexus 7 Android Development] CamoGeko:
So after a couple of days I ended up going back to the stock kernel included with crDroid. DC kernel just had some issues I couldn't get in with, one of which was accelerated battery drain. Even though it felt smooth and nice, the tablet itself got really warm and of course there's no DT2W.

I might try it again at some point in the future, but for now I'll stick with the stock kernel.

PS. I'm still having the weird systemui FC issues and freak outs, there are times when the systemui will force close like 2-3 times in a row then go back to normal. Wonder if this is just a low RAM issue or what, it's getting annoying now and I'm considering switching back to Kit Kat because of this.
[Nexus 7 Android Development] AICProcks!:
Do you experience the System UI force close issues when you pull down the Status Bar because that's the issue I sometimes experience after a reboot? And yes, its likely due to the low ram, but if you're looking for stability, I think you should start with the current AOSP rom. Lineage OS or even Unlegacy might also provide less force close issues. I would think that the less features available, the more stable. I mainly use crDroid for the SmartBar and Slim Recents. I found crDroid by chance when using it on my phone, and glad that I did because AICP stopped maintaining its rom source.

Also, I updated my Open Gapps to the February 24 build, and am experiencing less issues, (i.e. No sign-in error. Less force closes.) So maybe its Open Gapps related, but you probably don't use Open Gapps?

And yes, the optional DC Kernel also caused massive battery drain for me.

I also want to give an update regarding DT2W availability. I added DT2W to my current build (which is still on hold), but DT2W is not the problem in regards to the rom not building, so I contacted [MENTION=4936949]hokiealumnus[/MENTION] one of crDroid's developers about the issue. He claims that crDroid is done on developing the Nougat 7.1 source and is focused on Oreo 8.1 source, but they may continue providing the monthly Google Security Updates for Nougat 7.1. He also said that they would take a look at my build log.

Even though KitKat is more stable, I don't use it because it doesn't receive current Google security updates, especially after the October 2017 security patch.

P.S. I see that you have Dirty Unicorns on your OnePlus. If you haven't tried it yet, there is a Dirty Unicorns for Grouper from 23/11/2017. That's one of the roms I used before going to crDroid.
[Nexus 7 Android Development] JT1510365:
Thanks so much aicp rocks for your amazing work and time you put into this project! I simply love using this rom as my secondary rom and for me it rarely has issues and for the most part its been really stable for me:) Just give the tablet some time to rest its running on pretty old hardware compared to todays current devices.

One thing is can you please remove the sections in settings that i indicated and circled in the screenshots i attached our tablet doesnt need these in settings that would mean a lot to me and everyone else as these things in settings are not used or needed so please see screenshots i attached:)
[Nexus 7 Android Development] JT1510365:
also aicp rocks these sections need to be removed in settings also please see screenshots:)
[Nexus 7 Android Development] johniem:
[MENTION=5564834]johniem[/MENTION] Unfortunately, that's the same problem I am having from time to time, but this just started happening after I flashed DC Kernel. Did you also flash it? But, I even restarted the tablet with the latest build without DC Kernel, and this problem persists. This leads me to believe that there might be a problem in the latest build. I hate to say this, but try installing the very first build from November 2017 to see if this problem persists. Before this week, the first build I ever installed on my tablet was the November 2017 build, and I just kept updating it to the present January 2018 build so maybe the problem wasn't present on my end, but now it is since I restarted the tablet with the newest build.

By the way, I recall experiencing this problem in the past with this tablet, but I just don't remember which rom I was using. It might have been Lineage OS or Resurrection Remix. Every concurrent update would inadvertently "solve" this problem. And every other subsequent update, the bug reappeared. I even experienced this error on my phone, which also had Lineage OS and Resurrection Remix. crDroid is based on Lineage OS. The optional DC Kernel is from the Resurrection Remix rom. But, Resurrection Remix is also based on Lineage OS. To make matters even more complicated, not everyone experiences this error.

If I recall correctly, I started experiencing this random error after Deep Sleep was introduced to the present Android versions. But, I also noticed that different Open Gapps versions give me this issue. Now, I even have a random Sign In issue with Open Gapps.

I have a feeling this error might be caused by Wake Lock from different apps, but I suspect Open Gapps. If you search on Google, you can see that this problem is real, and there might be a solution on the last post here: https://android.stackexchange.com/questions/69297/nexus-4-does-not-wake-up-from-sleep-randomly

By the way, I looked at your post history, and I see that you had this problem with a lot of roms above Android 5 on Grouper :eek:. Like the link above says, try out Wake Lock - PowerManager by darken. Use the

Partial Wake Lock

setting, and see if that helps. I am trying it out myself.[/QUOTE]

You've notice right mate. Any version after 5.0.1 have the same sleep of death issue for my device.

I'm 100% sure that this is caused by Open Gaps, I've tested it and without the package installed the issue never happens.

I've tried any rom that i could find and none of them solved the issue.
[Nexus 7 Android Development] AICProcks!:
Let's get one thing right here [MENTION=5653319]JT1510365[/MENTION]. :D You should really be thanking [MENTION=4258086]firebird11[/MENTION], [MENTION=4478519]Cristiano Matos[/MENTION], [MENTION=4764217]davidteri91[/MENTION], [MENTION=4936949]hokiealumnus[/MENTION], [MENTION=3795148]neobuddy89[/MENTION], [MENTION=5880132]wilmsn[/MENTION], [MENTION=3729448]aaopt[/MENTION], [MENTION=2188693]AndDiSa[/MENTION], and [MENTION=5293805]GtrCraft[/MENTION]. Without them, crDroid wouldn't exist, and I wouldn't be able to build a crDroid rom for Grouper. Keep in mind crDroid depends on Lineage OS and AOSP.

Yes, the donor source is based on a phone mobile device, and I also never really liked this fact. I will try to find a seamless way to remove these unnecessary parts, but I am not making any promises, especially since the latest build is essentially broken for now.
[Nexus 7 Android Development] JT1510365:
what do you mean the latest build is broken i can try to remove them myself if you help me if i need help if thats what you mean but i am grateful for all the devs that have worked on making roms for this tablet and i am glad crdroid exist and i coudnt be more happy for it:)
[Nexus 7 Android Development] laugeek57:
Hello,

Could anyone test dolby atmos on this rom and tell me if it works i tested on rom aosp force close ... thanks :)

https://xdaforums.com/android/software/port-bq-aquarius-x5-dolby-atmos-t3752308
[Nexus 7 Android Development] AICProcks!:
[MENTION=5564834]johniem[/MENTION], I am confirming that OpenGapps (in this rare case) is leading to the Power Button glitch. Have you tried finding alternatives to OpenGapps? Because I have tried a few, but they all resulted in even worse errors. :D

Luckily, holding down the Power Button for approximately 4 seconds in most cases, allows my tablet to be unlocked. There are some instances where I wonder if the battery actually ran out, but nope, its just the Power Button. And that Partial Wake Lock app I recommended is counterproductive. It just drains the battery.
[Nexus 7 Android Development] AICProcks!:
This build error is what I mean by the build not completing:
[Nexus 7 Android Development] AICProcks!:
Tested it right now, and it force closes on this rom too. I extracted the zip, and tried to manually install DaxUI.apk. I get the following message: "The package appears to be corrupt."
[Nexus 7 Android Development] laugeek57:
Thank you friend :highfive: no hope that this sound module works on our old N7 ...:crying: