yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] CamoGeko:
Yeah it happens sometimes when pulling down the notification bar, but also for me at least occasionally when I try to wake up the tablet. I'm really hoping this can be fixed, as at the moment it's my only issue with crDroid.

Thanks for letting me know about DU for Grouper. I'm tempted to flash it because I love how well it works on my OnePlus X, but I think I'll stick with your ROM for now. It's working perfectly well, apart from the SystemUI issue. Honestly if that would be fixed and you could add DT2W, it would be the perfect ROM for me.

Looking forward to your next build man! Hope you manage to get it out soon.
[Nexus 7 Android Development] AICProcks!:
DU for Grouper was great until I started experiencing UI closes. :p That's the reason why I transferred to Resurrection Remix. The caveat there was that I ultimately had the same reason to transfer to crDroid which has less UI closes so far... But yes, sadly they are still present.

I am surprised you don't have the power button issue. ? In fact, I experience the power button issue more than I do UI closes. On average, I experience less than 1 UI close per day. Yes, you read that correctly. And when I do, its basically when I try pulling down the notification bar. The last time I experienced this was a week ago.

Note: This is when I recently wiped the whole entire tablet including storage, (cache F2FS and data F2FS), and flashed the latest crDroid with OpenGapps Pico, specifically the 24/02/2018 OpenGapps.

I also think that the Internet Browser you use is important on this tablet. Try the Samsung Internet Beta Browser. The only issue would be when it sometimes locks up and tries to reload the last webpage that crashed it. :good:

I don't know if its a placebo effect, but I recently flashed the "Oreo Go" Low Ram mod available on XDA. Maybe, just maybe it helped make the tablet a tad bit smoother. It took more than 10 minutes for the first reboot after flashing the mod. It's available here if you're interested: https://xdaforums.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373

P.S. If you want to try the Low Ram mod, you first need to erase the "#" comment mark in build prop where it says "#ro.config.low_ram=true". It should be "ro.config.low_ram=true" without the #.
[Nexus 7 Android Development] AICProcks!:
[MENTION=3301438]geko95gek[/MENTION] I added [MENTION=550003]Danielhk[/MENTION] code for DT2W (Double Tap to Wake) directly to the latest crDroid build with the default kernel. You can enable or disable DT2W in "Settings>Display>Tap to wake". I like the feature, but unfortunately, the battery life is subpar with DT2W. According to danielhk, the reason is that this is a software implementation of DT2W unlike other native DT2W present in some phones, for example.

Anyways, you can try out the build here and let me know what you think ;) : https://www.androidfilehost.com/?fid=962187416754467218

P.S. You don't need to flash anything extra; DT2W is in the default kernel. In fact, I think the DC Kernel I provided before didn't include DT2W.
[Nexus 7 Android Development] AICProcks!:
A new crDroid build with the February 2018 Google Security Updates is up.

DT2W (Double Tap to Wake) is also included which might cause cases of lower battery life. So far, with OpenGapps and SuperSU root, I have similar battery life to before.

You can enable or disable DT2W in "Settings>Display>Tap to wake".

If anyone wants, I can make a separate build without DT2W if battery life becomes an issue.
[Nexus 7 Android Development] farhadsss:
tanx

i just whant to say Tanx i flash it on my nexus its ok

is there a android5 for nexus 7 2012 ?and is it faster thean 7?if ther ia pls give me the link

TANX
[Nexus 7 Android Development] SilentWhiz:
OTG Not working properly

Hello! I installed your ROM a couple of days ago on my old (and only) tablet, the Nexus 7 2012 of the ****ty-NAND fame. I'm using a clean install of it with FTFS cache+data partitions -no other mods - and minimal apps (no gapps). It's running smooth at the moment, much better than how it was before the install with a much older (Kitkat/Lollipop) official Cyanogenmod. Thank you for the hard work you've put into this project :)

However, it would appear that the OTG isn't truly On The Go. Meaning, say I have the device on and I plug in an OTG device, it won't recognize it. I'll have to restart or soft-restart the device with the OTG device plugged in to have it work.

This is especially troublesome, because the lower right-triangular portion of my screen is cracked and doesn't respond to touch (a little mishap) and so I use a Mouse with OTG to avail its functionality. Now say I need to transfer files to it from a USB, I detach the Mouse OTG and plug in the USB. The USB wont work, but neither will the mouse if I plug it back in without at least a soft reboot. Result: One USB-to-Internal file transfer taking two soft-reboots.

Please see if the issue can be checked, I will be forever obliged, because it'll be a while before I can buy a new tablet.​
[Nexus 7 Android Development] AICProcks!:
[MENTION=9016801]farhadsss[/MENTION] As far as I know, there is no crDroid Android 5 version available. With the other available roms I tried at least, Android 5 was not faster than Android 7 on this tablet. If anything, you can have a look at an Android 4.4.4 rom if you are really looking for stability.
[Nexus 7 Android Development] AICProcks!:
[MENTION=5991507]SilentWhiz[/MENTION] I just tested OTG and it works for me with the default settings. I can change between an OTG mouse and OTG USB flash drive without having to reboot.

That said, I have a feeling your situation might have to do with the fact that Android USB debugging is enabled by default. However, I have it enabled, and OTG still works for me.

Did you try plugging in the tablet to your computer and granting access to the debugging feature?

Also, you can just try disabling USB debugging in Development Settings.

And also, try to change default USB from charging to MTP.

There have been reported cases of OTG not working on Nougat randomly for other devices, while it was working great for others who had the same devices. :silly: However, OTG should function properly on this tablet; at least it does for me...
[Nexus 7 Android Development] SilentWhiz:
I think the Charging->MTP was the fix, because I tried it first and it started working right! Muchos gracias for the swift response :D
[Nexus 7 Android Development] AceJaseq:
I have flashed the rom and this has worked fine but for the life of me I cannot get opengapps pico to install, I keep getting error 70 space issue, I did copy all 3 files crDroid ZIP and openGApps ZIP and gapps-config-grouper.txt but still giving me the error.

Any ideas at all ?

Cheers
[Nexus 7 Android Development] AICProcks!:
[MENTION=5745883]AceJaseq[/MENTION] You need to make sure that gapps-config-grouper.txt is in the same exact directory or folder as the Open Gapps Pico ZIP.

I also recommend clearing the entire tablet before installing the rom and Open Gapps Pico.

If you still encounter this issue, you may need to remove a few unnecessary System apps since the System partition is very small. Refer to Post #76 for a simple way to remove some System apps. https://xdaforums.com/showpost.php?p=75559564&postcount=76
[Nexus 7 Android Development] ericcostes:
stay on welcome screen at rom first start

Hi,

I just installed 712-r5 on my grouper

with pico and gapps txt

rom starts with the welcome screen and offers 2 choices :

copy your data from cloud

or setup as new from zero

in both case when selected I come back on the same welcome screen !!

nothing is started ! :crying:

please help :)

regards

eric
[Nexus 7 Android Development] AICProcks!:
[MENTION=4345211]ericcostes[/MENTION] Try flashing [MENTION=5653319]JT1510365[/MENTION]'s Setup Wizard Fix from https://drive.google.com/file/d/1Sl3mLc9davcYZ6roVsBDPA1gdzpPxD_6/view
[Nexus 7 Android Development] Qusaiqwhl:
Need help please

Please note am not expert and I need your help, I tried to flash this rom however am getting stuck with zip file is corrupted!

Am not sure where is the problem I got no system currently in my nexus 7 I got only the recovery installed, please let me know where am going wrong

---------- Post added at 07:08 PM ---------- Previous post was at 06:53 PM ----------

Jut to add I tried 2 roms so far and facing the same issue :crying:
[Nexus 7 Android Development] AICProcks!:
[MENTION=9056183]Qusaiqwhl[/MENTION] I also had this issue many times with different websites, especially Google Drive. Downloading the zip file again usually worked. You can extract the zip file on your computer to make sure if the zip file is corrupt.

Are you using TWRP recovery? You should also make sure to install the latest TWRP recovery from https://dl.twrp.me/grouper/.
[Nexus 7 Android Development] cmenghi:
Hi, i'm found a little laggy with flipboard, i'm using to read and share with this app. Anyone has similar lag ?

Thanks.
[Nexus 7 Android Development] AICProcks!:
[MENTION=3085747]cmenghi[/MENTION] Navigating in Flipboard is not that bad, but when you combine sharing, then yes, its unusable. Unfortunately, sharing seems to be built in to the app. I was going to suggest a lightweight alternative to Android Share, such as Andmade Share or AppChooser... :(
[Nexus 7 Android Development] AICProcks!:
March 2018 Google Security Updates

A new build is up with the March 2018 Google Security Updates!

The "Experimental" DT2W is still included since battery life seems to be the same with Gapps installed. If you experience battery life problems, I can provide a version without DT2W. :good:
[Nexus 7 Android Development] grybouille:
Can I ask you for a version without DT2W ? It seems it caused battery drain for me with the 2018-03-11 build ; I disabled the option but the battery drain occurred again and again : that's why I came back to 2018-01-19 version...

Thanks for your work, My tablet loves your rom ^_^
[Nexus 7 Android Development] AICProcks!:
[MENTION=5125287]grybouille[/MENTION] As requested, I uploaded a version without DT2W to the first post.
[Nexus 7 Android Development] grybouille:
Thank you so much !!

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 Android Development] grybouille:
In fact, the tablet didn't boot with the "without-DT2W" Rom. I did a clean install, tried several times, wiped everything but it staid stuck on the logo.

Does anybody else have the same issue ?

No such problem with the "DT2W" Rom : it boots normally ; if I have no issue concerning battery drain, I'll stay with it. I'll test...
[Nexus 7 Android Development] argonavtik:
Same story :(
[Nexus 7 Android Development] greatdudguy:
Download keeps failing. Tried both server options multiple times. No problems downloading the last build (2018-03-11, 7.1.2_r5) so it's not a problem with all of Android File Host.
[Nexus 7 Android Development] AICProcks!:
[MENTION=7824604]greatdudguy[/MENTION], [MENTION=5125287]grybouille[/MENTION], and [MENTION=1274017]argonavtik[/MENTION] Thanks for informing me about this issue. It was a corrupted zip file. I uploaded the latest version without DT2W again. It should work now.
[Nexus 7 Android Development] greatdudguy:
I actually meant the one with DT2W, but if the one without it is working then I'll give that a shot
[Nexus 7 Android Development] AICProcks!:
[MENTION=7824604]greatdudguy[/MENTION] Now both the DT2W and noDT2W versions should work.

Similar to a problem a previous poster had, the zip file was corrupt for some reason when I uploaded it to my Google Drive, which then resulted in a corrupt file upload to Android File Host.

On a side note, I did have trouble finding a fast working Android File Host server today.
[Nexus 7 Android Development] grybouille:
Great ! Works fine now !:good: thanks :)
[Nexus 7 Android Development] JT1510365:
same issue for me here:(
[Nexus 7 Android Development] AICProcks!:
[MENTION=5653319]JT1510365[/MENTION] Did you try the newest upload? It appears to be working for [MENTION=5125287]grybouille[/MENTION] now. :confused:
[Nexus 7 Android Development] JT1510365:
Yep just flashed your newest build as a secondary ROM with opengapps nano in multirom and all is good and is fully working here:) Seriously bro thanks so much for your hard work and time for us its much appreciated. I didn't see your previous post so sorry bout that:)
[Nexus 7 Android Development] JT1510365:
Yeah not hating or anything but IMO androidfilehost seems to be hit or miss right now. I don't know what's going on as sometimes its hard to download my files from there or other peoples files. Hopefully they can get that worked out soon because I love androidfilehost more than basketbuild imo.
[Nexus 7 Android Development] AICProcks!:
April 2018 Google Security Updates

A new build is up with the April 2018 Google Security Updates!

Note: If you have battery problems with the DT2W version and don't need it, try the normal version. Both versions are up! :good:
[Nexus 7 Android Development] Cocalarix:
It's actually amazing how good the performance is on this old beast, so thanks for the effort OP. It's also amazing that we have double tap to wake on a 2012 device.

Although, it is a bit unstable sometimes. Apps sometimes hang a lot, I got a few sudden restarts. Is there anything to help with that? Should I avoid any apps, like Xposed? Magisk?

And what apps do you guys use for battery saving? Greenify?
[Nexus 7 Android Development] AICProcks!:
[MENTION=5348241]Cocalarix[/MENTION] The previous build was actually quite stable for me for more than two weeks, and then today it suddenly started experiencing crashes whenever I pulled down the notification menu... :rolleyes: These UI crashes are indeed random, but I mostly get them when trying to pull down the notification menu.

Since you have the DT2W version, I recommend getting OpenGapps. With OpenGapps, I had excellent battery life, but the "true" DT2W dissipates in that it randomly works from time to time probably because of wake lock. But the temporary DT2W is quite useful for me, plus the battery life is nearly equal to the normal version (but only with OpenGapps and SuperSU root; at least that's how it was in my case :D). Otherwise, the screen is always "awake" which causes the battery loss.

And yes, I try to avoid Xposed since it causes stability issues for me.

The app that hangs the most for me is Google Maps. ES File Manager sometimes hangs, so I try to use the default crDroid File Manager. As for the Internet Browser, I recommend Samsung Internet Beta.

All in all, taking into consideration the age and limited RAM of the tablet, I recommend mapping the Back Button to "force end" occasional hanging apps. :D
[Nexus 7 Android Development] shawnploo:
+1

This is the smoothest rom so far. All of the other roms have UI lag. I had to OC some of the other roms for the UI to act normal. So far I've been using crDroid for 3 weeks to graph with the Torque Pro app in order to diagnose a minor engine problem. I leave Torque Pro open with the screen on for 20-30 minutes and bluetooth enabled. Torque has never crashed with this rom. I wanted to get a good feeling for this rom before I posted anything here. I hope the OP continues to support this rom because it's the best rom for the the N7 right now.

:fingers-crossed: :highfive: :good:

Build 2018-04-06 (7.1.2_r6)
[Nexus 7 Android Development] nmark1999HUN:
Map problem

I'm so glad the rom is good.

But for me, the waze navigation program does not work. black map. Or do you have some kind of google service not install? Google map works.

Thank you in advance for your answer!

(My English Level Beginner)
[Nexus 7 Android Development] AICProcks!:
[MENTION=7907151]nmark1999HUN[/MENTION] I also had this problem before on this tablet with a different rom, but I could not figure out what was wrong. This problem was also present on my phone before.

Currently, Waze magically works on that phone with crDroid. However, Waze still does not work on this tablet with crDroid. :(

UPDATE: Waze 4.34.1.0 works! Thanks [MENTION=1971572]jonalowe[/MENTION]

I tried backing up Waze on my phone with Titanium Backup to transfer to this tablet, but that did not work. :(

For some reason, the Waze maps are not displaying on the tablet. But, I think they are there. It must be some kind of permission problem with the rom.

To add to the problem, Google Maps works, but it randomly stops working. :(
[Nexus 7 Android Development] antoniocaser:
No space for gapps

Friends, ROM installs and does not have room for the Gapps ...
[Nexus 7 Android Development] AICProcks!:
[MENTION=4958857]antoniocaser[/MENTION] As stated in the first post, you need to use Open Gapps Pico and the Open Gapps System Size Fix https://androidfilehost.com/?fid=745849072291693897

Paste the fix in the same folder as Open Gapps zip.
[Nexus 7 Android Development] ZandroRev:
Brightness slider with auto-brightness turned on is mal-configured on my device. 1/3 and below turns the lamp off completely, which can cause my device to be soft-bricked as I lose sight of the control to turn it back up. I have already factory reset once as a result of this, and find auto-brightness to be too dangerous to enable until this can be fixed.
[Nexus 7 Android Development] AICProcks!:
[MENTION=9126631]ZandroRev[/MENTION] Assuming you have root access, check to make sure the following value is not less than 10 in /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
[Nexus 7 Android Development] ZandroRev:
AICProcks!, thank you for the tip. 10 was already set in the file, and increasing this value does dynamically adjust the brightness. 10 is indeed equivalent to the lowest setting in the manual brightness slider. Now I'd like to learn where the setting to change the range for the auto-brightness slider is.

*Update, I was unable to create a min_brightness entry using the integrated file manager (root access enabled).
[Nexus 7 Android Development] AICProcks!:
Yes, I had to use ADB shell to change the value. I had a similar problem to yours with a Samsung phone, but can't seem to reproduce it with this tablet. It looks like I need to modify the framework.jar in the rom to better Auto Brightness values, but I still need to research this a bit more.

**For now, in case anyone experiences this problem, shine a flashlight at a 45° angle on the screen in a completely dark room (you need to "unlock" the screen with the power button to make the screen go on from sleep as usual). You should be able to very dimly see the screen to adjust the brightness setting. If you don't see the screen, ask someone else. They might see it better.**
[Nexus 7 Android Development] AICProcks!:
[MENTION=9126631]ZandroRev[/MENTION] Is this the first time you have ever experienced this auto brightness issue? Are you sure you didn't experience this issue in Lineage OS or AOSP roms, or even the stock Nexus 7 2012 rom?

From my research, I have gathered the following:

Some users with the stock rom (no modifications) have experienced this issue out of the factory; while others have not...

This crDroid rom is based on Lineage OS and AOSP so it should have the same Auto Brightness values; it seems to have the same values when I checked underneath config_autoBrightnessLevels https://github.com/wilmsn/android_d...rameworks/base/core/res/res/values/config.xml and https://github.com/AndDiSa/android_...ameworks/base/core/res/res/values/config.xml.

The above source files appear within /system/framework/framework-res.apk in the crDroid rom.

It looks like these values were last modified in 2012 so maybe you need to calibrate your light sensor.

It seems like users of various devices recommend Lux to "smartly" calibrate the "automatic" light sensor. Judging by your past experience, you should proceed with caution though: https://www.howtogeek.com/168127/how-to-improve-your-android-phones-automatic-brightness-with-lux/ and https://forums.androidcentral.com/s...e-auto-brightness-gesture-100-brightness.html
[Nexus 7 Android Development] AICProcks!:
Double Post
[Nexus 7 Android Development] ZandroRev:
I was on cyanogenmod 11 since 2013 until this week, and was without this issue. Too long ago to remember if stock did this, and I went straight to this mod without testing vanilla LineageOS, so those points of reference are missing. Your flashlight recommendation makes me realize that my problem only occurs in dim light conditions. I even thought that the feature to adjust brightness by sliding across the status bar (bottom of the crDroid's Status Bar settings tab) had something to do with it, but in testing it seems to have equivalent range to the quick controls' slider with autobrightness enabled. I find it odd that static brightness setting has a higher minimum overall.

Okay, Lux is nifty. That reminds me, I used f.lux before the switch. It would be prime suspect material, but it shouldn't have any lasting effect after system wipe, should it?
[Nexus 7 Android Development] AICProcks!:
If you only wiped the System partition, then there would still be remnants in Data and Internal Storage.

Regarding Lux, you can also set custom values to your liking and situation.
[Nexus 7 Android Development] ZandroRev:
I gave it a full wipe of all partitions, even updated twrp before reformatting to be safe. Lux's granularity is irrationally good. Its default 0-point looks like the old manual brightness min (10), but their sub-zero range dims smoothly all the way to barely visible in full darkness, never completely blacking out. Because it overrides the sliders, it's a perfect workaround. Thank you for your research!
[Nexus 7 Android Development] dtnosk:
Can't install pico app package not enough system space. Coming from a fresh full
[Nexus 7 Android Development] AICProcks!:
[MENTION=4343225]dtnosk[/MENTION] As stated in the first post, you need to use Open Gapps Pico and the Open Gapps System Size Fix https://androidfilehost.com/?fid=745849072291693897

Paste the fix in the same folder as Open Gapps zip.
[Nexus 7 Android Development] cnterr:
Hi guys, I tried to install both standard and DT2W versions, I followed the instructions to the letter, no problem during installation, the device works well and it's fast but to every reboot the terminal takes about 5 minutes to start. Is it normal?

After the Google logo the screen goes black for about 5 minutes before the animated crDroid logo.

I've a Tilapia device with Grouper TWRP and DATA/CACHE formatted in F2FS.
[Nexus 7 Android Development] AICProcks!:
[MENTION=5624747]cnterr[/MENTION] This is not normal. Did this happen before with different roms?

Also, before you began installing custom roms, did you upgrade to the latest available firmware? (I remember that Lollipop gave me a lot of slow downs, so I downgraded back to KitKat. Then if I recall correctly, after the downgrade to KitKat, I began installing custom roms.)
[Nexus 7 Android Development] cnterr:
Nothing to do!

I've...

...restored the KitKat 4.4.4 factory image with original recovery, updated 4.2.3 bootloader and latest radio image for Tilapia. No boot issue.

...flashed Grouped TWRP 3.2.1.0 from adb...

...wiped any partition...

...formatted data and cache with F2FS file system...

...installed crDroid and open gaps pico...

...factory reset and wipe data again...

...reboot.

The device works well and fast but the slow boot issue continue.

With integrated root the boot stuck on Google logo for approximately 5 minutes, after Magisk installation instead the Google logo disappear after a few seconds and the screen goes black for approximately 5 minutes.

In any case after approximately 5 minutes appear the crDroid logo and boot continue normally.

Could it be a problem due to having installed a Gruoper rom on a Tilapia?