yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Geko45:
[MENTION=2188693]AndDiSa[/MENTION] just tried out the 02/07 Grouper release and really like it! A very smooth and clean AOSP experience. I did encounter one issue though, I could not get any content to play through Google Play Movies and TV. All attempts to play anything resulted in "Couldn't fetch license (error 901)." Play Music, Books, and Newsstand all seemed to work without issue, but I couldn't get any Google video to work at all.

To eliminate all other possible contributing factors, I wiped system, both caches, data and even deleted everything from internal storage other than the ROM and GApps zips (using Open Gapps nano for 7.1). I then flashed the zips, setup my Google account and installed the Movies app. No custom kernels or mods were loaded and I still got the same issue.

I was encountering this issue with your 6.0 ROM as well and never solved it. As a control, I did the same test with Pure Nexus and was able to play movies easily. So, I don't think it is a problem with my Google account. I'd much prefer to use your ROM though as it performs much better than the others and does best at providing a true AOSP experience.

My tablet is currently in a wiped state so I can try to test scenarios if that will help.
[Nexus 7 Android Development] vetzki:
Thats the terrible german word for mobile phone

regarding wifi:

on lineage it seems that wifi drops less

maybe some of their frameworks/opt/net/wifi changes would help (https://github.com/LineageOS/android_frameworks_opt_net_wifi/commits/cm-14.1) ?
[Nexus 7 Android Development] AndDiSa:
As far as I know you need to apply some patches to the ROM so that Substratum is supported, but I am not sure.
[Nexus 7 Android Development] AndDiSa:
[MENTION=4201184]Geko45[/MENTION] I can reproduce that behaviour here, too, but I am able to stream on my Chromecast. Seems to be another issue with DRM .. :(
[Nexus 7 Android Development] Geko45:
Since my tablet is wiped anyway, I've been trying pretty much every ROM here. So far, every ROM that shows "userdebug testkeys" in the build number has exhibited the same behavior. Is it possible that Google isn't streaming to any ROM not signed with official "release" keys?
[Nexus 7 Android Development] tomtom_38:
Bug report:

I observe a fast battery drain. I kill all apps but it does not change.

from 99% to 15% in 8 hours in stand by mode.

I measure with Ampere the consumption is 430 mA at least to compare my Nexus 2013 have a consumption from 170mA
[Nexus 7 Android Development] AndDiSa:
[MENTION=4336485]alezardstar[/MENTION] it's on my list, but I doubt to be able to integrate it already into the next build. I need to see what it to be integrated and how much work this will be

[MENTION=5377515]CROSP[/MENTION] looks to me as connection problems:

02-19 07:16:35.846 1887 7639 W DownloadManager: [6] Stop requested with status HTTP_DATA_ERROR: connect timed out

02-19 07:16:35.847 1887 7639 D DownloadManager: [6] Finished with status WAITING_TO_RETRY

other errors I cannot see within the log an
[Nexus 7 Android Development] AndDiSa:
[MENTION=6811049]tomtom_38[/MENTION] you should have a look at google play services. Especially after an update it's draining battery very much. From my side I cannot reproduce that behaviour. When unused battery drains less then 0.5% per hour, when using the tablet around 10-15% per hour.
[Nexus 7 Android Development] javi_fly:
hi, i am using this version 7.1.1_r20 en mi nexus 3g (2012) works fine, but not have tethering (hotspot) option for share my 3g conection by wifi.

Are there any packet to add and put this option en the menu??

In firmware 5.1.1 and before firmrs have a patch for this option. https://xdaforums.com/showthread.php?t=2535586

I have try this patch in 7.1.1 and not work.
[Nexus 7 Android Development] tomtom_38:
[MENTION=2188693]AndDiSa[/MENTION] google services I can t find in the Akku menu.

Have you a workaround if the google service is responsible for this?
[Nexus 7 Android Development] CROSP:
[MENTION=2188693]AndDiSa[/MENTION], but my connection is good enough and works well with other devices, the browser (web view default) works well. All other services works good as well.
[Nexus 7 Android Development] spark001uk:
[MENTION=2188693]AndDiSa[/MENTION], You've been hard at it again, thankyou for all your work! I'm still on r19 at the moment, it's working great for me. (I don't use google play so the DRM isn't an issue for me). I was just wondering if you were any closer to a solution for the fast charging yet? Don't worry if not, it's not that big a deal for me (but would be handy in the event of needing a quick top up when short of time or something maybe).

Add: Battery life seems a little unsteady, but I've a feeling that's partly down to the battery itself. Don't think Asus make brand new genuine ones anymore either, and I'm not sure if the unbranded ones for sale on ebay etc are trustworthy? Anyone tried one?
[Nexus 7 Android Development] AndDiSa:
[MENTION=4201184]Geko45[/MENTION] I found the solution, it's related to including the telephony services into a WiFi only device. In those cases deviceId is generated from the IMEI which is not available ....

Next build it should be fixed though ... ;)
[Nexus 7 Android Development] williamlaw:
After I change the \data partition from f2fs to ext4, it's succeed to boot into 7.0.

Is it caused by partition format ?

Otherwise, for SYSTEMLESS root, do I run command [echo "SYSTEMLESS=true" >/data/.supersu] in TWRP ?

Since I have tried to run in adb but failure.

Thanks !
[Nexus 7 Android Development] n3kf:
Alright. After I got rid of the play services constantly dying, the ROM is running pretty good. It is however pretty much a couple task oriented. That is, to much at once and the system gets extremely sluggish. For instance, if the playstore starts updating, everything will crawl to a halt. Although it is really old hardware. Another gig of memory would be nice!! I'll give it a couple days. Unfortunately, it seems like parrotmod may not be fully working on nougat and the creator is too busy to upgrade it.
[Nexus 7 Android Development] tpuserhp:
You might want to use a root editor/ kernel aduitor to update the system configs as in parrotmod script. I selected and modified some statements (like low memory killer and read ahead queue) and put them in a script and run it from terminal emulator app after each boot. It gives some performance improvements.
[Nexus 7 Android Development] AndDiSa:
[MENTION=6824216]n3kf[/MENTION] go into settings/developer settings and set max. background processes to max. 4.

In addition: keep at least 4GB free in the memory and run trim regularly I noticed a huge slowdown as soon as I had less than 3.5 GB free
[Nexus 7 Android Development] AndDiSa:
[MENTION=5333182]tpuserhp[/MENTION] I tried to play a bit with those settings, too, but for me they had no or almost no influence on the performance, at least after I reduced background processes to 4.
[Nexus 7 Android Development] AndDiSa:
[MENTION=3887645]williamlaw[/MENTION] f2fs should be supported (I cannot guarantee because I am on f2fs), but a logcat would help much to figure out that issue.
[Nexus 7 Android Development] tpuserhp:
It could be as YMMV. But I found changing /sys/block/mmcblk0/queue/read_ahead_kb to 0 makes a difference for me on performance. Memory management requires other changes and could depend on tasks running.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5333182]tpuserhp[/MENTION] probably I'll give it a second chance ... ;)
[Nexus 7 Android Development] n3kf:
Yes, I set max to 3. Wiill see if it helps. I have about 12gb free on the device. I do let fstrim run once a day. It really truly has a lot to do with only having 1gb of memory. I'll play a little with min free memory settings to see if I can make the memory manager a little more aggressive.

---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------

You mind posting the script? No use reinventing the wheel!!! Thanks.
[Nexus 7 Android Development] tpuserhp:
I just pick and choose statements from parrotmod script with minor changes. See attached.
[Nexus 7 Android Development] n3kf:
Thanks. That does seem to help my device alot. Guess when I have time I'll make it a start up script.
[Nexus 7 Android Development] AndDiSa:
[MENTION=4336485]alezardstar[/MENTION] I posted the link to my blog only for giving you a hint how to configure adb / fastboot access, it was not intended to guide you for MTP setup, because opensuse 11 is already a bit old and go-mtpfs probably is no longer maintained. You can use any other mtpfs implementation, it doesn't really matter.

Important for accessing bootloader / recovery via fastboot resp. adb are those two lines in the udev-rules file:

# Google Nexus 7 16 Gb Bootloader & recovery mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="ds" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="ds" # Recovery

The first line enables fastboot access when the device is in bootloader mode, the second line enables adb access when the device is in recovery mode.

For adb access of a running system, the situation is a bit different: the last bit of the product id is changing in rspect to the protocol selected, i.e. '4e44' instead of '4e43' when using PTP or '4e42' instead of ''4e41' when using MTP protocol:

# Google Nexus 7 16 Gb PTP mode (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e43", MODE="0666", OWNER="ds" # PTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="ds" # PTP media with USB debug on

# Google Nexus 7 16 Gb MTP mode (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="ds" # MTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="ds" # MTP media with USB debug on

This configuration principals should be valid for all linux distributions.
[Nexus 7 Android Development] AndDiSa:
Android 7.1 AOSP on Grouper

For those of you, who would like to try Android 7.1, I've uploaded Android 7.1.0_r4 [NDE63P].

It looks really promising, the only downside: /system is even more occupied and as BanKs didn't provide a dynamic gapps version for 7.1 yet, only pico-Gapps will work with this build.

You can flash the zip as described in the OP. If you are already on AOSP 7.0 there is no need to wipe, coming from other ROMs, it's probably better to do so.

For this ROM you will need Gapps which support SDK 25, i.e. gapps for 7.1!

and as always: flash on own risk!
[Nexus 7 Android Development] AndDiSa:
[MENTION=4336485]alezardstar[/MENTION] probably it's better to change the thread, because this adb / fastboot configuration stuff isn't really related to this ROM ...

About your question: the name of the rules-configuration file isn't really interesting, it only defines the sequence in which the rules files will be exectuted. You should have only *one* android-rules configuration file, so either 50-android.rules or 51-android.rules but not both. Otherwise there might be some interdependencies ...

Regarding accessing a running system via adb: you need to have switched on remote debugging on the device, otherwise adb is not able to connect. If you connect the first time, you also have to accept a signature, otherwise adb connections will be rejected by the device.

If you are in recovery mode, normally adbd on the device is started automatically, so there should be no problem to access the device via adb, at least as long as you are running a custom recovery like TWRP or CWM.

Regarding fastboot, you *cannot* access the device by adb, but you need to use fastboot. adb will not find any connected devices, while fastboot will do.

Hope that will help you a bit further. If you have other questions, we should switch thread

Btw.: @demkantor 's thread about adb and fastboot may be helpful, too.
[Nexus 7 Android Development] tpuserhp:
I've found out I missed copying one vm heapsize statement. Sorry. I include the modified script as attached. Hopefully get less crashes.
[Nexus 7 Android Development] abhifx:
this is wonderful! good amount of thanks as i am going to try this
[Nexus 7 Android Development] Bakica:
How can we use this script? Gave us a quick manual, please. Thanks in advance
[Nexus 7 Android Development] AndDiSa:
Next version of the ROM will have included most of the settings provided by the script.

If you want to apply the script by yourself, you need to open a root shell and run the script as a shell script.
[Nexus 7 Android Development] AndDiSa:
Improved 7.1.x version uploaded

I've updated the OP with a new version of the 7.1 ROM. ParrodMod-Tweaks are inlcuded, kernel is updated with fix for Dirty COW (CVE-2016-5195).

The 7.1 version seems to me better/with less issues than the 7.0 versions, beside the issue, that camera is not working :(
[Nexus 7 Android Development] Windsor1959:
I pulled out my old grouper and installed 7.1 with pico gapps and systemless root. Installation was flawless; the ROM seems pretty stable at first glance. My Galaxy Tab S2 (which doesn't have 7.0 yet, let alone 7.1) is a bit envious! Thanks for the good work!
[Nexus 7 Android Development] Geko45:
[MENTION=2188693]AndDiSa[/MENTION], great news! And makes sense, all those ROMs that pull directly from AOSP sources were also the ones displaying the behavior. Would it be to much to ask for an update to your 6.0 ROM as well? I'm a big fan of Xposed and GravityBox (which already work well with your MM) and those aren't available yet on Nougat. I'd be willing to make a donation to support the effort. I realize your time is valuable.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5377515]CROSP[/MENTION] what gapps package do you have installed? Is it the one I've linked in the OP or a different one? Searching the internet several sources give a hint that this might be caused by an incompatible gapps package.
[Nexus 7 Android Development] AndDiSa:
[MENTION=4201184]Geko45[/MENTION] I am not sure to be able to provide a 6.0 build, too, it's some work to be done and my time is a bit limited ... we'll see.
[Nexus 7 Android Development] CROSP:
[MENTION=2188693]AndDiSa[/MENTION] Thank you for the reply, I have install Gapps package listed in the OP https://www.androidfilehost.com/?fid=529152257862697269 . Also I have tried to install another ROM (Lineage) with OpenGapps Pico, the similar problem, can't download anything from the Google Play. (but error messages were not the same, something about permissions)

I have no idea what can be wrong. Also I have installed TWRP suggested in the OP.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5377515]CROSP[/MENTION] did you try to check whether all permissions needed by the play start / google services are set correctly? Go to app permissions, select show system applications and check whether all google services have been granted all the permissions they are requesting and if somthing is missing, grant that permission to those applications.
[Nexus 7 Android Development] aolins:
[MENTION=2188693]AndDiSa[/MENTION] Thank you for your hard work on this ROM. I have Tilapia and switched to this ROM from nAOSP. This ROM seems much smoother and more stable than nAOSP. The only issue I am facing is that the tablet is occasionally dropping the 3G connection. It happens when tablet is idle and is not in use for some time. If I try searching for network operators then, I am getting error (cannot connect to network). In such case if I switch Airplane mode on and off, tablet even does nor ask for SIM pin. It seems like no SIM is not detected or radio is not responding. The only thing that helps is a hard reboot. This never happened on nAOSP ROM. Any idea what could cause this behavior? Anyone else having issue with 3G?
[Nexus 7 Android Development] AndDiSa:
[MENTION=5773494]aolins[/MENTION] thank you for your reply. Unfortunately I don't have a Tilapia device so it's very difficult for me to check this behaviour. Can you provide me with a logcat which contains your observed behaviour?
[Nexus 7 Android Development] aolins:
OK. I will create and post the logcat next time my Tilapia losses 3G and fails connecting to network. However, this is not a severe issue for me, since I can always hard reboot the tablet after what everything works fine for a while, and the booting takes about 1,5 minutes.
[Nexus 7 Android Development] Hightower68:
Great to have 7.1 on my old nexus 7. Thanks for keeping it updated.

Just one thing I cant seem to solve. My battery status is always 0%. I never know how full or how much time left. It will say charging but thats it. No battery stats either.

Tried factory reset. Reflashing., battery apps, and disconnecting reconnect the battery cable. All to no avail. Any solution?
[Nexus 7 Android Development] AndDiSa:
[MENTION=4214308]Hightower68[/MENTION] No, I've never heard of such an issue. You could probably try a 3rd party app (e.g. 3C battery monitor to compare the values with the system ones.
[Nexus 7 Android Development] CROSP:
[MENTION=2188693]AndDiSa[/MENTION] Hi, thanks for reply. All permissions were set correctly. I finally found the problem. Something wrong is going on with my home router. After rebooting the router everything works fine. But after some time this happens again, so I need to reboot the router again. The interesting thing is that only my tablet and only the google play app suffer from this problem. Maybe the Google Play app is sending some special traffic so it gets blocked by the router. I will try to investigate the problem and let you know.

Thanks.
[Nexus 7 Android Development] Hightower68:
Thanks for the suggestion but ive tried many including that one. Still shows 0% for some reason. Will keep searching.
[Nexus 7 Android Development] mausbock:
I have same issues from time to time but I don't use 3G not very often. For me is it acceptable to reboot if the connection is lost.

There is a bug in the original Nexus 7 3G Firmware "xmm_power_wakelock" and a kernel patch available to minimize battery drain. The patch was published on a German forum http://www.android-hilfe.de/thema/k...id-os-bug-baseband_xmm_power-wakelock.666283/ and is based on a kernel https://xdaforums.com/showthread.php?p=36908034 here at XDA. But there is an issue with this patch. If You minimize the battery drain to much You will get 3G connections lost sometimes.

May be [MENTION=2188693]AndDiSa[/MENTION] also applied this patch directly or indirectly via kernel in his ROM. There are some custom kernels with this patch in the wild.
[Nexus 7 Android Development] AndDiSa:
[MENTION=6755201]mausbock[/MENTION] Yes, the fix is applied, so we have identified the problem, but unfortunately no solution yet ... :(
[Nexus 7 Android Development] mausbock:
[MENTION=2188693]AndDiSa[/MENTION]

There is a second version of the patch available in post #13 of the german forum thread. That will make mobile connection more stable as You will see in post #15 but results in a little bit more battery drain. In the past I applied this second version of the patch and had stable 3G connection. May be You can analyze the difference between this and the patch You applied.
[Nexus 7 Android Development] sweetsuicides:
Thanks everybody. I have to report, too, that 3g disconnects after a while. I only tested it once, but after reboot the connection didn't work (the pin question screen disappeared before I was able to complete the log in). It worked after a second reboot. I hope I am somehow contributing.
[Nexus 7 Android Development] adstraylight:
I may have found a solution to the intermittent WiFi dropouts, I stress the word "may" though...

In build.prop there is an undefined value: ro.wifi.channels, setting this to the number for my region, in my case 13 as I'm in Europe, seems to have stabilised the connection. Of course only time will tell, but wanted to share in the hope of finally putting this issue to bed. I rebooted after setting the value btw.

I hope this helps others

Edit: To be clear, the setting relates to the maximum number of channels available, not the specific channel your router is using. eg. My router uses channel 3, but I set the build.prop value to 13, as this is the standard number of channels allowed on European systems.

In the US this standard is 11 channels, other regions may vary.

As long as the router's channel is within the range set in the build.prop, you'll be ok..
[Nexus 7 Android Development] vetzki:
did you use the 3.4 kernel before? not sure but I think I had the same issue when I tested 3.4 kernel.
[Nexus 7 Android Development] Hightower68:
I cant recall. But kernel right now is 3.1.10 from dsyoda
[Nexus 7 Android Development] psiphi:
Power off take off back and disconnect the battery. Press power button to fully discharge. Reconnect battery and put back together. Fully Charge but don't power on. Now use the tablet without charging until empty. Now fully charge with power on. If that fails you could reflash stock to verify but think might be failing hardware. You might need new battery and/or motherboard.
[Nexus 7 Android Development] Reeka:
thank you! thank you! thank you! Works perfect :good:

Edit: Of course you have to choose the Channel your Router is using for WiFi. In my case it is luckely 13 ;)
[Nexus 7 Android Development] adstraylight:
The setting defines the number of channels available for use, not the specific wifi channel you're using. My router is set to use channel 3, but I set the build.prop to 13 as this is the standard number of channels allowed on European systems.

In the US it is 11...

If you google international WiFi channels, you can read all about it, but but beware it gets very technical very quickly.

Anyway glad it's working for you ?
[Nexus 7 Android Development] vetzki:
Thanks that was how I fixed the problems back then, not sure but as far as I remember disconnecting and reconnecting battery already fixed it for me
[Nexus 7 Android Development] adstraylight:
Substratum support would be very cool indeed, particularly with the apparent imminent demise of CMTE, I'm betting all the themers will be using it soon.
[Nexus 7 Android Development] frankusb:
For building from source, it looks like the correct location for this would be in full_grouper.mk?

PRODUCT_DEFAULT_WIFI_CHANNELS := 13
[Nexus 7 Android Development] adstraylight:
I'm not a developer, so I've no idea about that, all I do know is that setting the build.prop value has made the connection so much more stable and reliable.

It's pure speculation, but maybe the driver for our 'legacy' hardware, or some other runtime component obtains this parameter from the build.prop, as opposed to anywhere else.

My lead for this (as yet unproven) fix came from googling "ro.wifi.channels blank", finding this post: http://freaktab.com/forum/tv-player...an-and-streaming-connection-stability-problem

and simply trying it out...

NB: I didn't try any of the other perameter changes, as setting the channels alone has so far solved the problems.

Had a thought that maybe this should be set by the setup wizard in first run, as it is a locale specific variable.
[Nexus 7 Android Development] frankusb:
Building from source results in:

Starting build with ninja

ninja: Entering directory `.'

ninja: error: 'out/target/product/grouper/kernel', needed by 'out/target/product/grouper/boot.img', missing and no known rule to make it

make: *** [ninja_wrapper] Error 1

From research this appears to be an AOSP default setting, to use a prebuilt kernel. Any hints?
[Nexus 7 Android Development] AndDiSa:
[MENTION=3771488]frankusb[/MENTION] did you apply all the patches from my repository? In that case a kernel build target should be available and you can build the kernel from the sources.
[Nexus 7 Android Development] frankusb:
I performed:

repo init -u https://github.com/AndDiSa/platform_...ouper-AOSP.git -b ads-7.1.0

repo sync (... and go out for lunch ...) (skipped lunch, it's early yet)

. build/envsetup.sh

lunch 7

make

---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------

Oh I see, I missed https://github.com/AndDiSa/platform_manifest-Grouper-AOSP/blob/ads-7.1.0/README.md