yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] AndDiSa:
[MENTION=961756]dicko99[/MENTION] thank you very much! I'll add the permissions and start a new build ... unfortuately further missing permissions will occur only after those one is fixed ... :(
[Nexus 7 Android Development] goran_s:
Hi,

I updated to latest version and got: "Google play services stopped working", "MTP stopped working"... Erased my google account but could not log in after recreating acc "there was a problem communicating with the google servers"

Uninstall and reinstall of gapps didn't work, cleaning data and cache didn't work. Only wipe from TWRP and fresh start solved it.

Now the grouper is working ok but I had two hard crashes and reboots while watching movie in MX Player. There was also strange buzzing and crackling noise those times during reboot and at first google logo.

Best regards,

Goran
[Nexus 7 Android Development] dicko99:
I don't know if this is important but I just spotted this whilst running logcat during a restart of the device:

08-20 12:58:39.201 225 225 E RadioService: couldn't load radio module radio.primary (No such file or directory)
[Nexus 7 Android Development] AndDiSa:
[MENTION=961756]dicko99[/MENTION] I don't think so because also on the WiFi model I have that message. As far as I know it's for loading a new firmware which we do not have.
[Nexus 7 Android Development] pitflyer:
I reset my Nexus 7 (grouper) to factory and followed the steps including Bean Mini Apps... it took four tries before it would let me sign into Google Play. And now that I'm finally in, whenever I open Play Store it says 'Authentication required' and when I click Retry goes into a loop where it just asks me over and over again.

My first time using Bean Mini Apps, have others had success with it? Should I try opengapps or another distro instead?

EDIT: Just waited about ten minutes and tried a few more times, eventually it worked... thanks OP for keeping this device alive. :)
[Nexus 7 Android Development] AndDiSa:
I've built another Tilapia version including the permission issues [MENTION=961756]dicko99[/MENTION] found in his logs:

aosp_tilapia-7.1.2-ota-eng-20170820.ds.zip

No guarantee that it will work now but let's hope the best :)
[Nexus 7 Android Development] dicko99:
Still no SIM but a slightly different error msg:

08-21 06:59:39.070 542 542 W system_server: type=1400 audit(0.0:27): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-21 06:59:46.510 583 583 W am : type=1400 audit(0.0:32): avc: denied { execute_no_trans } for path="/system/bin/app_process32" dev=mmcblk0p3 ino=122 scontext=u:r:rild:s0 tcontext=u:object_r:zygote_exec:s0 tclass=file permissive=0
08-21 06:59:47.320 556 556 W ActivityManager: type=1400 audit(0.0:58): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-21 07:00:03.691 1442 1442 W am : type=1400 audit(0.0:90): avc: denied { execute_no_trans } for path="/system/bin/app_process32" dev=mmcblk0p3 ino=122 scontext=u:r:rild:s0 tcontext=u:object_r:zygote_exec:s0 tclass=file permissive=0
08-21 07:00:20.751 2384 2384 W am : type=1400 audit(0.0:91): avc: denied { execute_no_trans } for path="/system/bin/app_process32" dev=mmcblk0p3 ino=122 scontext=u:r:rild:s0 tcontext=u:object_r:zygote_exec:s0 tclass=file permissive=0
[Nexus 7 Android Development] AndDiSa:
[MENTION=961756]dicko99[/MENTION] I'll add that permission, too and provide you (most likely tomorrow) with a new build
[Nexus 7 Android Development] pierre_g:
Thanks a lot [MENTION=2188693]AndDiSa[/MENTION]! I followed exactly what you've written in the first two posts of this thread, and all is fine (Nexus 7 Grouper version).

I've been able to install and run Lego Boost app from Play Store, an app that require BLE (Bluetooth Low Energy), something that the stock Kitkat version didn't support. Great!
[Nexus 7 Android Development] AndDiSa:
Groundhog Day ... a new version for Tilapia to test :aosp_tilapia-7.1.2-ota-eng-20170821.ds.zip
[Nexus 7 Android Development] dicko99:
Another set of error messages:

- waiting for device -
08-22 09:32:04.080 455 455 W system_server: type=1400 audit(0.0:25): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-22 09:32:07.950 469 469 W ActivityManager: type=1400 audit(0.0:51): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-22 09:32:12.730 598 598 W app_process: type=1400 audit(0.0:58): avc: denied { write } for name="trace_marker" dev=debugfs ino=190 scontext=u:r:rild:s0 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
08-22 09:32:12.750 598 598 W app_process: type=1400 audit(0.0:59): avc: denied { execute } for path="/data/dalvik-cache/arm/system@framework@boot.oat" dev=mmcblk0p10 ino=237571 scontext=u:r:rild:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
08-22 09:32:18.330 468 468 W android.bg: type=1400 audit(0.0:81): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-22 09:32:23.857 598 598 W main : type=1400 audit(0.0:91): avc: denied { execmem } for scontext=u:r:rild:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-22 09:32:23.907 598 598 W main : type=1400 audit(0.0:92): avc: denied { execmem } for scontext=u:r:rild:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-22 09:32:24.857 598 598 W main : type=1400 audit(0.0:93): avc: denied { call } for scontext=u:r:rild:s0 tcontext=u:r:servicemanager:s0 tclass=binder permissive=0
08-22 09:32:24.857 598 598 W main : type=1400 audit(0.0:94): avc: denied { call } for scontext=u:r:rild:s0 tcontext=u:r:servicemanager:s0 tclass=binder permissive=0
08-22 09:32:42.207 1333 1333 W app_process: type=1400 audit(0.0:95): avc: denied { write } for name="trace_marker" dev=debugfs ino=190 scontext=u:r:rild:s0 tcontext=u:object_r:debugfs:s0 tclass=file pe

r
[Nexus 7 Android Development] dark0shark:
Dock no more recognized

After successfully updating to aosp_grouper-7.1.2-ota-eng-20170811.ds.zip my Nexus 7 does not recognize the Nexus 7 dock anymore: neither sound play-back nor battery loading works anymore. Since my Nexus 7 is attached to my HiFi-amp by dock and plays via BubbleUPnP I need that functionality. Does anybody else got the same prblem? Any idea to fix...?
[Nexus 7 Android Development] pjcanales:
On latest grouper version I'm getting error that Google play service has stop. I would keep getting error every now an then when tablet is on. Any solutions?

---------- Post added at 07:27 PM ---------- Previous post was at 07:24 PM ----------

What exactly did you do to get rid of the Google play services stopped. And even after you did it did the issue ever came back?
[Nexus 7 Android Development] AndDiSa:
[MENTION=3339124]pjcanales[/MENTION] try to have a look at the permissions granted to Google Play Services. [MENTION=5128593]dark0shark[/MENTION] I don't have a dock but did you try to revert t o the version from July? Is it then working again? [MENTION=961756]dicko99[/MENTION] there is the new Tilapia build: aosp_tilapia-7.1.2-ota-eng-20170822.ds.zip
[Nexus 7 Android Development] JouSePo:
I've recently updated my n7 with this rom and i experienced the same problem in charging. USB port has been replaced in july. My solution is to schedule a restart every night.

My n7 is used as a clock, radio and tv in my nightstand with the screen always on.

This rom is awesome in performance (like a normal tablet, no issues experienced, apps that runs and not doing before). Thx [MENTION=2188693]AndDiSa[/MENTION] for the effort!!!
[Nexus 7 Android Development] goran_s:
I first uninstalled google apps and reinstalled them but to no avail. Then I flashed BeansGapps-Mini-7.1.x-20170725.zip but problem remained. I went into TWRP and choose wipe, after that everything worked.

Best regards,

Goran
[Nexus 7 Android Development] isharra:
Confirmed on one of my 3 groupers. Nasty speaker buzz when rebooted. Oddly enough the tablet is charging but it refuses to believe so. I thought my hardware was going bad but it is detected properly in twrp and unlegacy android (which loves to freeze.) Restored from backup. (This is my radio/alarm clock so the dock with it's sound connection is important to me.)

Open GApps is still unable to make it through the setup program on any of my tablets, and that's after dropping back to nano. Any larger package won't install due to a lack of space. I could eventually get through setup using Bean's mini gapps but random reboots and app crashes are discouraging.

These attempts are made after factory resets, when I could get through setup all permissions had been granted to Google play store and service.
[Nexus 7 Android Development] AndDiSa:
I can confirm the "not charging" issue. It happened to me yesterday, too, but after a restart everything was fine again. I think I'll have to do a deeper look into it.
[Nexus 7 Android Development] mafarric0:
Hi

I still use the tilapia version, but as I'm holidays I cannot do any tests untill I return home, within 3 weeks :cool:

I also brought back to life 2 other devices with this ROM and the users are making use of it. When there's a stable build I will update them as well.

Thank you very much for keeping this device alive.
[Nexus 7 Android Development] dicko99:
Still no joy on the SIM front. Here are the latest errors:

MacBook-Pro-4:platform-tools Richard$ ./adb logcat | grep ril
- waiting for device -
08-23 12:07:48.230 455 455 W system_server: type=1400 audit(0.0:25): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-23 12:07:53.940 472 472 W ActivityManager: type=1400 audit(0.0:51): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-23 12:07:57.040 529 529 W app_process: type=1400 audit(0.0:56): avc: denied { open } for name="trace_marker" dev=debugfs ino=190 scontext=u:r:rild:s0 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
08-23 12:07:57.050 529 529 W app_process: type=1400 audit(0.0:57): avc: denied { execute } for path="/data/dalvik-cache/arm/system@framework@boot.oat" dev=mmcblk0p10 ino=237571 scontext=u:r:rild:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
08-23 12:08:05.380 850 850 W Binder:455_7: type=1400 audit(0.0:81): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:rild:s0 tclass=process permissive=0
08-23 12:08:10.705 529 529 W main : type=1400 audit(0.0:91): avc: denied { execute } for path="/dev/ashmem" dev=tmpfs ino=5534 scontext=u:r:rild:s0 tcontext=u:object_r:ashmem_device:s0 tclass=chr_file permissive=0
08-23 12:08:10.845 529 529 W main : type=1400 audit(0.0:92): avc: denied { execute } for path="/dev/ashmem" dev=tmpfs ino=5534 scontext=u:r:rild:s0 tcontext=u:object_r:ashmem_device:s0 tclass=chr_file permissive=0
08-23 12:08:12.865 154 154 W servicemanager: type=1400 audit(0.0:93): avc: denied { search } for name="529" dev=proc ino=9321 scontext=u:r:servicemanager:s0 tcontext=u:r:rild:s0 tclass=dir permissive=0
08-23 12:08:31.055 2019 2019 W app_process: type=1400 audit(0.0:95): avc: denied { open } for name="trace_marker" dev=debugfs ino=190 scontext=u:r:rild:s0 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
08-23 12:08:31.065 2019 2019 W app_process: type=1400 audit(0.0:96): avc: denied { execute } for path="/data/dalvik-cache/arm/system@framework@boot.oat" dev=mmcblk0p10 ino=237571 scontext=u:r:rild:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0

No rush for a new version as I'm off on holiday for a couple of weeks.
[Nexus 7 Android Development] dark0shark:
... and if charging is not detected on the dock, the sound will not go thru that, too. I already tried rebooting with Nexus 7 on dock, but no luck. Also sound is crackling on the tablet itself, as stated above by another user.
[Nexus 7 Android Development] ruedihofer:
still having sound volume and charging issue

Hi @AndDiSa

I wrote in an earlier post about two problems which are similar to the ones mentioned above.

- having no music sound through speaker (but having music sound through earphones and having notification sounds through speaker)

- tablet not charging

This happend then and happens with the latest release as well.

I have attached a logcat. I'm glad if you could have a look into it again...

Thanks, ruedi
[Nexus 7 Android Development] AndDiSa:
[MENTION=8213790]ruedihofer[/MENTION] thank you very much for the log but unfortunately I do not see any important issues there. It looks very similar to my boot logs.
[Nexus 7 Android Development] adstraylight:
I'm running UA, but I guess with the same aosp code, and have been having the not charging issue with my dock for some time.

There seems to be a lag or problem with the system ui, and it often takes several attempts, manually disconnecting and reconnecting with the dock to get the system to recognise it. Don't know if it's a system resource thing, or just an artifact of the grouper's age.

I now routinely open the battery QS tab when docking, and fiddle with the dock connection untill it says charging on AC.
[Nexus 7 Android Development] Ahkah:
The speaker sounds awfully by design, but when playing a video I hear something. Be sure to increase the appropriate speaker level (that one with the musical note).
[Nexus 7 Android Development] ruedihofer:
Yes I know. Funny thing is, that the volume rocker for music jumps either to zero or full with speaker. With headphone it behaves correctly. Notification sounds volume rocker always does right ... ?!?
[Nexus 7 Android Development] gouchouya:
Hi

new ROM was so faster and reactive than old

that is very nice

however its too active to battery drain

so use "kernel adiutor" to set CPU conservative and lowest frequency from 51 -> 513MHz(old ROM is 340MHz)

but low frq always on 51MHz even with "performance control"

other issues are slow battery charging and sometime will reboot
[Nexus 7 Android Development] adstraylight:
Try this, shut down the tablet, put it on charge, and don't restart it until it is full. Then see what the usage is like.

I often have to do this after installing a new ROM to settle the background usage.
[Nexus 7 Android Development] AndDiSa:
[MENTION=5909756]gouchouya[/MENTION] I con confirm most of this issues:

- battery is draining a bit more then in the version before. I think it's due to more agressive lowmemorykiller settings. I am on it.

- frequency range is 51 -> 1300 Mhz using intelliactive (as intelliactive is build in in the power control, too, it's difficult to change the governor using kernel adiutor)

- slow battery charging can be caused by two situations:

a) the device didn't realize that it's on charger and so charging power is limited to 900mA (instead of 1800mA) which is equally to no charging with screen on because the device will use ~700-900mA with screen on or you ar using a charger which is not providing a stable voltage while charging (btw. I am getting the highest charging rates while connected to a usb 3.1 port and not with a charger)

b) there is a cpu high load on your device

- there is an issue with intelliplug hotplug control which is causing reboots from time to time You can disable intelli_plug by

echo 0 > /sys/module/intelli_plug/parameters/intelli_plug_active
[Nexus 7 Android Development] gouchouya:
thx your opinion ^_^ b

https://mega.nz/#!psUF0Z7R!mDWTOuJfUD5KN3krjqSm0dreZoAC9HN3it25UyRgZGI

here is what I want to set lowest frq 513MHz

but i can't change anymore(and highest frq can be changed)

will try to disable intelli_plug_active

I appreciate it :):good:
[Nexus 7 Android Development] adstraylight:
My opinion was based on experience, it is my perception that the new ROM background load (compiling the apks etc) causes a wakelock that gets stuck, ie not released, and that a long period with the system shutdown clears this condition.

Of course I could be completely wrong, and would love to know why turning the system off cuts persistent battery drain from the denial of deep sleep.
[Nexus 7 Android Development] dark0shark:
Yes, I reverted back to July, had to fiddle around a bit with the settings for Media playback via Dock, but now sound is coming thru the docking plug again.
[Nexus 7 Android Development] AndDiSa:
Currently I am testing a new release which hopefully has fixed all / most of the issues reported in the last days. Give me one / two additional days for testing.
[Nexus 7 Android Development] isharra:
Thanks very much for the hard work on this.

Is anyone else having the navigation buttons remaining on screen when the device goes to daydream?
[Nexus 7 Android Development] DumF0rGaming:
Del
[Nexus 7 Android Development] Charles IV:
If people are still having the annoying swiping to unlock the screen issue, I just spotted on their subreddit: https://www.reddit.com/r/LineageOS/...ength_of_the/dm8oth6/?st=j6wk2ztz&sh=3458628b

something to do with HIL apparently.
[Nexus 7 Android Development] andy_96:
-UI lag (swiping)

-Sound lag (player and youtube)

no load on cpu and battery is good

Tilapia, fresh install with full wipes

P.S.

btw, if i install grouper version, only sim function will be lost?
[Nexus 7 Android Development] AndDiSa:
[MENTION=5736135]andy_96[/MENTION] yes, you can install the Grouper image on Tilapia, too, but you will not have any 3G functionality.

As I wrote I was testing a new build and I've now uploded them:

aosp_grouper-7.1.2-ota-eng-20170828.ds.zip

aosp_tilapia-7.1.2-ota-eng-20170828.ds.zip

I am still not sure whether the Tilapia build is running well, as it seems still too small to me ... probably I'll need to unpack an old version and try to find out what file(s) are missing ...

The other issues should be fixed now, even if I am still not happy with the speed ramp up after waking up from sleep. I did not update the OP yet as I would like to get some feedback from you, first.
[Nexus 7 Android Development] mausbock:
I will test the tilapia build this evening and try to provide the relevant logcat.
[Nexus 7 Android Development] dark0shark:
Sorry to inform you that also with new version the dock is not detected: no charging symbol, no sound.
[Nexus 7 Android Development] mausbock:
Thanks [MENTION=5054799]DumF0rGaming[/MENTION] for providing the logs. I got similar output.

http://cloud.tapatalk.com/s/59a5bff037afb/bugreport-NZH54D-2017-08-29-17-46-00.rild.txt

[MENTION=2188693]AndDiSa[/MENTION]

I also tested the kernel and memory optimization and I still get higher CPU usage in idle mode and system RAM usage is still swinging between 300 and 350 MB all the time in idle mode.
[Nexus 7 Android Development] AndDiSa:
[MENTION=6755201]mausbock[/MENTION] [MENTION=5054799]DumF0rGaming[/MENTION] [MENTION=5128593]dark0shark[/MENTION] Sorry guys, currently I am running a bit out of ideas ... best would be to return to the June/July version though.
[Nexus 7 Android Development] LELBOT:
[MENTION=2188693]AndDiSa[/MENTION] just got my mobo replacement for grouper, unlocked and flashed twrp, instant flash the latest test build and stable release.

Same ui lag and idle load, test build is good but not for daily usage.

Will try the july build and hope for the best.

Thanks for continued support.
[Nexus 7 Android Development] andy_96:
Please, tell about sound in youtube and music app?

Is it lagging?
[Nexus 7 Android Development] abhifx:
lag is almost same on both build which is kind of ok for our device... this build however seems to drain faster
[Nexus 7 Android Development] LELBOT:
Well for usage, i flashed naosp.

As for YouTube, the sound was good on beta build.
[Nexus 7 Android Development] Ahkah:
music player problems

With the August OS version I tested two music players: Speaker volume is extremely low, and I cannot move the position slider for FLAC files. The same FLAC files behave normally on my Nexus 5 with standard OS. Both music players show the same symptoms. Unfortunately I did not perform these tests with the July version.
[Nexus 7 Android Development] n3kf:
I had moved up to the August release a couple weeks ago. I use a task killer and notice with the July release I can get about 480 mb of available memory. With the August release, that number goes down to the low threes pretty fast. I know people say that Android manages memory, but with grouper, once the memory gets low, it goes out to lunch and then it usually reboots.. I was digging around to try and see what may be using memory, but could not find it. I wonder if there might be a leak. I tried setting the memory management to very aggressive, but that did not help. I am back on the July release and the device is much more stable.

Also, I notice that the USB port has been charging very slowly up through the July release. I have not tried any work arounds to see if I could improve that since a put a QI receiver in and charge wirelessly. The USB charging worked very well on the August release. Not sure if there were any fixes there or not.

As usual, thanks for all your hard work AndDiSa . It's appreciated!
[Nexus 7 Android Development] AndDiSa:
[MENTION=6824216]n3kf[/MENTION] within the July release I had an additional 85mb of free memory configured which I removed in the August release. Probably it's better to re-introduce this configuration again.

Regarding slow charging, I am on the idea that it's much related on power consumption while running, I.e. higher CPU frequency and many active cores are reducing the charging speed. On the August release I am getting easily up to 1000mA/h while on the July release it's more 400-500mA/h ...

I'll be on vacancies the next time .... Lets hope the September build will be better
[Nexus 7 Android Development] Ahkah:
Hoping that you did not mean „Stellenangebote” (vacancies) I wish you pleasant holidays (English) resp. vacations (American).

;)
[Nexus 7 Android Development] n3kf:
Thank you. Enjoy your holiday, you deserve it!
[Nexus 7 Android Development] AndDiSa:
... who knows ... (vielleicht ein freud'scher Vertipper ;))
[Nexus 7 Android Development] Fitz Creativ:
No lag after flash these apps with rom!!

[MENTION=2188693]AndDiSa[/MENTION] I flashed the build that is dated August 28, 2017 or 29th on my Nexus 7 (2012) + Plus ParratMod & SuperSu + Pixel Experience (optional)....

My device runs really really really smooth... NO LAG

Thanks alot for that latest build but the default launcher could be changed in a next update so I would not have to flash the Pixel zip
[Nexus 7 Android Development] Alex_Lyt:
Hi,please tell is it a risk to get apx if I already have root, twrp and 4.4.2 rom installed? I've already bought one grouper with a broken screen and would like not to buy one more ))
[Nexus 7 Android Development] AndDiSa:
Your device will go to apx mode if you erase your bootloader resp. flash a wrong bootloader otherwise Nexus devices are quite resistant.
[Nexus 7 Android Development] Alex_Lyt:
I'll tell You my story, if You don't mind. Please tell me, what did i do wrong

I had cm13 installed and it worked fine, but one day I've decided to try Pure Nexus build. I've just full wipe and flashed build and gapps. My nexus turned on fine and worked for a few minutes. I've even managed to take a look at that build's menu, etc. But then tablet simply freezed with a screen on. After a minute or so i've pressed and hold a power button. Tablet turned off and gone to apx.

What was my mistake?

Thank You!
[Nexus 7 Android Development] DumF0rGaming:
You haven't tried to keep Power button pressed for 30+ seconds, try fastboot and recovery combinations, plug it on charge. I got my tablet recovered twice this way
[Nexus 7 Android Development] Alex_Lyt:
It is an old story )))

I've tried everything, believe me. All ended with the new donor motherboard.

That is why i'm asking, what NOT to do in order not to get apx again.

---------- Post added at 02:06 PM ---------- Previous post was at 02:00 PM ----------

Upd: apx mode means, that one of your bootloaders is dead. Yes, it is two of them at nvidia- based nexus. Nvidia bl is factory crypted, so no one able to recover your nvidia bl if it is corrupted.