yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] abhifx:
obviously.

---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------

@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.
[Nexus 7 Android Development] 52mm:
：手指划线：
[Nexus 7 Android Development] ho0o0o11111:
Thanks for bringing nougat to our beloved Nexus 7!!!

I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.

Any hints?

Thanks.
[Nexus 7 Android Development] daniel_hk:
If you want anyone to help, you have to provide details. ;)

The tested Gapps' are listed in OP. "No matter which gapps" ? :confused:

Can you tell us which one and version you actually tried?

What's your flashing procedures? etc.
[Nexus 7 Android Development] ho0o0o11111:
Procedures (clean flash)

- rom

- gapps

- supersu

- reboot

- no playstore/play services have been installed after reboot

I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.

the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)

Finally I got playstore installed as follows

- flash rom/gapps/supersu

- reboot

- uninstall some system apps I don't need

- flash gapps again

then the playstore appears in app drawer. (And it works)

However, I have another big problem after reboot.

My device is now stuck in bootloop after splashscreen.

It just shows message as follows and I can't enter recovery/bootloader.

Supported API: 3

E: unknown fs_type "f2fs" for /cache

E: Can't mount /cache/recovery/last_locale

In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.

http://xdaforums.com/nexus-7/orig-development/wip-linux-tegra-nv-3-4-bringup-t3128195/page46

still trying...

Any helps would be appreciated.

Thanks.
[Nexus 7 Android Development] daniel_hk:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.

You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.

You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.

Good luck! ;)
[Nexus 7 Android Development] ho0o0o11111:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.

I can't flash TWRP again as I am still struggling to enter bootloader mode.
[Nexus 7 Android Development] daniel_hk:
Which version? eariler version might have a wrong fstab which have issue on f2fs.

Make sure you got the latest version 3.0.2

You can't go to boot loader?

That means you press pwr+vol down and it won't reboot to bootloader?

That's strange.

"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.

You may try this:

1. connect to the charger

2. pressing the pwr button for > 8 seconds.

See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.

If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.

Good luck!
[Nexus 7 Android Development] webdroidmt:
[MENTION=4948627]daniel_hk[/MENTION]

Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.

A couple of observations:

As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.

I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL

After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.

Thanks again.

Mike T
[Nexus 7 Android Development] Ludespeed:
Do games work on this rom?
[Nexus 7 Android Development] paasoares:
Hi,

This is the best 7.0 ROM so far !!!

Smooth, video HW decoding is working, games work perfect.

As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.

All Apps/games that i installed are working properly.

Thanks Daniel_hk for your work
[Nexus 7 Android Development] 3yan:
Many thanks :D Works like a charm !

Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)

.

Can you post your manifest on Your Github for easier building ?
[Nexus 7 Android Development] fat-lobyte:
Hi, currently testing your ROM, looks awesome!

When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:

09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0

This message times * 100 for every page load.
[Nexus 7 Android Development] daniel_hk:
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.

I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.

1. Try factory reset before flashing.

2. Flash ROM+Gapps+SuperSU

3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)

Good luck! ;)

I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.

There is a shell command "getenforce" which you can check the SEPolicy status.

If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com. ;)

Good luck!

Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.

I already included some extra permissions which would be include in my later builds.

Anyway, we would encounter denials more often in apps. That's what newer Android intent to do. :D
[Nexus 7 Android Development] fat-lobyte:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener com.android.server.wifi.WifiConnectivityManager$3@e43c4fe
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed

This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain ;)

I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
[Nexus 7 Android Development] frov:
I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.

But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).

But the story ends well, as my video now works: great job ! :D
[Nexus 7 Android Development] paasoares:
Did you set "keep wi-fi on during deep sleep" to NEVER?

My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable
[Nexus 7 Android Development] fat-lobyte:
It was on "always".

I agree. I just thought it's an error that needs to be fixed.

[MENTION=4948627]daniel_hk[/MENTION]

Can you integrate the BFQ I/O scheduler into the Kernel?

Also, does anyone know good settings in Performance Control?
[Nexus 7 Android Development] mrgold2505:
sorry to ask but is teh GPS working ok?
[Nexus 7 Android Development] millosr:
I was getting the same error, for the clean flash on the official TWRP.

I get out from this by connecting tablet to PC with Windows and :

adb reboot bootloader

fastboot flash recovery twrp....

For some reason adb reboot bootloader didn't work for me on linux.

This happens because when creating ota package - recovery-from-boot.p and install-recovery.sh files are created and at the end of init.rc there is:

service flash_recovery /system/bin/install-recovery.sh

I guess that twrp has some mechanism to defend from this recovery flashing, but for some reason that doesn't work for everyone.

I've solved this problem by skipping creation of recovery patch: https://github.com/millosr/android_build/commit/d5a6bf6811a273652c9a68f3a143f7f34a011d5a

and commenting service flash_recovery lines in init.rc.

How did you fix hw decoder?
[Nexus 7 Android Development] daniel_hk:
For adb, it only work after the adbd on the tablet is running. If it work on your windows, you may check if the /etc/udev/rules.d/xx-android.rules file exists and included the vendor id of Google (and Asus). Fastboot would never work without it.

1. The last line in init.rc just defined the service flash_recovery which was never called

2. Same as the flash_recovery service, install-recovery.sh was there for a few versions. (Since JB or earlier??)

3. Only if you include it, we won't find those files anywhere in /system and the zip won't have the recovery image too.

I never experience it so I can only guess. I think there might be some residue in the old /system. Therefore someone from some ROM might ran into trouble. In any case, it seems wise to factory reset and wipe the /system before flashing.

For the hwcomposer, it is also a permission issue. OMX codecs are move to a new service MediaCodec. I tricked them by rename the codecs (inside the blob) to Google's name. It's not fully working and there are many extra permissions follow. I think there is a better way. I traced the source and I found something yesterday. I think I would come up with a formal and easier way soon. Will update you later ;)

Edit:

1. Seem no reason to rebuilt the kernel repeatedly, I use a pre-built kernel in this build. It might be the difference and recovery not included in my otapackage.

2. I think I found a simple fix for the hwcomposer. I'll test it further when return home. ;)

Since you asked a few times. I have tested the GPS today. In the 45 min. round trip drive, I tested a few apks. It is working fine. Locking and responding are all normal.

But, when I came out from a building. It take quite long to lock again. Some apks just fail to lock. I restart the apks and everything were back to normal. I didn't turn off the location so the hardware is not reset.

I think its data connection (and Wifi) related. I have a Tilapia without a sim card. Those apks like maps require a data connection (say to check the traffic status, etc.). Those Compass apks which don't require the data connection seems OK. It might be the Google location service or something else.

Anyway, restart the apk (or the location) again is not a problem for me. ;)
[Nexus 7 Android Development] AndDiSa:
Well there might be a different mechanism on N which I didn't understand fully yet, but if you built the ota package you will have a file "/system/etc/recovery-resource.dat" and I suppose that this recovery resources are patched against the recovery installed on the device when you are flashing the ota package. I think it's sufficient to not create that file. I'll have a deeper look at the build tools.

Edit: As the ota-package files are incremental updates there might be also a problem with existing recovery patching tools / scripts in /system/bin which will not be deleted
[Nexus 7 Android Development] eNVy:
Can any kind of theme-ing be done on this ROM ? Layers or Substratum ?
[Nexus 7 Android Development] RastaFATian:
Substratum will be great, loved it in pure nexus rom. ;)

Edit: this rom seems to have implemented it.

http://xdaforums.com/showthread.php?t=3467335
[Nexus 7 Android Development] fat-lobyte:
Touchscreen going crazy after long sleep

Hi, after the Tablet has been to sleep for a longer time, and I try to unlock it, the Touchscreen goes crazy.

First, it doesnt register touches properly. Then it registers them somewhere where I didn't touch. Then it just makes touches without my fingers being even close!

I have a logcat available if you want. Do you want the full boot or only since the unlock?
[Nexus 7 Android Development] DaveConnor:
Hi everyone,i am also facing the same problem and can't get into the bootloader/recovery....so please if someone has any leads on this please tell!
[Nexus 7 Android Development] ur6an:
If just shows message

Supported API: 3

E: unknown fs_type "f2fs" for /cache

E: Can't mount /cache/recovery/last_locale

1. Connect the tablet to PC (you must have adb and fastboot)

2. adb reboot bootloader

3. fastboot flash recovery recovery.img
[Nexus 7 Android Development] ho0o0o11111:
This doesn't work.

adb and fastboot commands can't be passed to tablet. Tried many times.
[Nexus 7 Android Development] ur6an:
Try reinstall adb drivers.
[Nexus 7 Android Development] ho0o0o11111:
I have tried already.

Doesn't work.

Besides Nexus 7, I have two more Nexus devices and both of them are fine with adb drivers in my PC. So reinstall or not is not the problem anyway.
[Nexus 7 Android Development] uffi69:
Same problem here. if there is any solution, please tell me
[Nexus 7 Android Development] paasoares:
I had the same problem yesterday.

Dont Panic !

When you turn on the tablet you only get :

Supported API: 3

E: unknown fs_type "f2fs" for /cache

E: Can't mount /cache/recovery/last_locale

In my case it was like in a loop always showing the same above message.

What i did was connect the USB cable and run "adb reboot bootloader". it will work even if the tablet seems to be in a loop, Bootloader will show up.

After that you can do whatever you want with "fastboot" command.

Cheers,
[Nexus 7 Android Development] AndDiSa:
Looks as if f2fs for cache is not supported by your recovery. You can try to wipe cache / reformat cache with ext4.
[Nexus 7 Android Development] daniel_hk:
For those interested, I have detail this problem and the solution in Post #2.

Hoping it helps... ;)

After stuggling with the MTK kernel for a week, I finally managed to make it work. :highfive:

I was hoping there will be new release of AOSP but it's still 7.0.0_r14. Anyway, it time for an update.

In this build:

The occasional crash of MTP Document provider is shielded.

USB and Bluetooth tethering is enabled.

Cheers! :D
[Nexus 7 Android Development] ho0o0o11111:
You saved my life! :good:

I can enter bootloader now. Just adb to push the recovery.img again and now flashing your new build of rom.

Thanks a lot!! :laugh:

---------- Post added at 07:44 PM ---------- Previous post was at 07:06 PM ----------

"For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula."

After flashing the new build of rom and reboot, I still face the problem of that reboot failure issue.

This time I could push adb command easily and installed the recovery.img again.

(Flashing Carbon rom to see if this happen too)
[Nexus 7 Android Development] 239:
Installed it yesterday and works great so far, had to reflash TWRP after reboot (unknown fs_type "f2fs" for /cache), though.

Only issue I noticed is that Music app just crashes but I just disabled it anyway. Will report again if there are more problems.

Thank you very much for making the Nexus 7 usable (for Surfing/YouTube/Neflix) again!
[Nexus 7 Android Development] Hubird:
I STRONGLY advise people NOT to install this, I am having the same bootloop problem as others

I have a feeling the tablet is bricked

When you turn on the tablet you only get :

Supported API: 3

E: unknown fs_type "f2fs" for /cache

E: Can't mount /cache/recovery/last_locale
[Nexus 7 Android Development] daniel_hk:
I think I was clear but seems I'm having communication issue.

What you said didn't draw a picture of anything.

Pressing pwr+vol down is the ultimate way.

If you follow the steps, you should see the charging image. Otherwise, either the charger is not properly connected or you forgot to mention or else. I just don't know how to help.

If that's so hard to explain, can you ask someone to take a video? It can show what you have actually done and what really show on the screen. etc. ;)

First of all, I never encounter this situation. This is something that bother someone not just here but a few other ROMs from different developers. So I take sometime to study why.

I never ask anyone to install it. As I mentioned, its for people with some experience, either good or bad. At least you know how to handle yourself when things go south.

I can dig deeper if there is further info. May be the last_kmsg after reflash TWRP. I just answered to the message being reported.

I have flashed a few time with different combination. I have reboot a few times a day too. I didn't have what you people said. I don't know if there are different batches or variants of devices. There is nothing to go on.

Anyway, I second you. Just don't flash any of my ROM. It might kill you and your device. :D

Thanks! But we have to get use to it. Find a target to blame is usually the easiest way out. Sooner or later we have to learn how to forgive.

I want to know why too. I have tried different combination. The difference is I never flash other ROMs but mine. That's why I told people to wipe the system before flash. It's just another guess of course.

Anyway, I can close the thread if I really kill someone or something with my work. :D
[Nexus 7 Android Development] daniel_hk:
I didn't design the device to use the pwr+vol. down to go to bootloader. I just told you what I read and tried.

OK, that means pressing the pwr button will reboot but fail to have the charging image show.

If a charger or USB cable is connected, the device would start up quietly and go to charging mode. Pressing the power button to reboot would be something like power off and then on again. If a charger is connected, it should go to charging mode first. Anyway, you may try release the pwr button right after the Google logo disappeared. See if you got the charging image.

I'm on Linux most of the time. If you are on Windows, you need a driver to work with adb. There are guides for that.

I didn't see you mentioned the messages, just the boot logo. I want to know more.

The solution I post is for the following:

1. they flash the ROM and reboot.

2. It works

3. after reboot they got a message

Are you in the same situation or you never successfully boot up after flashing?

These cases are different.

If that's not what you encountered, can you remember what files you have flashed and what had happened after that?
[Nexus 7 Android Development] AndDiSa:
[MENTION=4336485]alezardstar[/MENTION] if your device is in a bootloop, pressing vol+ / vol- *only* should be sufficient to reboot into recovery or bootloader mode. It depends a bit on whether you have a kernel bootloop or a system bootloop. If you are on a system bootloop you probably need to switch off first the device by holding the power button for about 10 sec.

If you press vol+/vol- in parallel you might end in APX mode which is a bit tricky to leave, because the device seems to be switched off (screen is dark), but actually it's still powered on. In that state you can neigther use fastboot nor adb commands.
[Nexus 7 Android Development] ho0o0o11111:
I can confirm that daniel_hk's instruction in post 2 works.

Completely switch off the device, plug in to charger and see the charging icon are important.

Although after that it still took me a while to try to enter bootloader finally, but this really works and saved my device.

So for those still having the problem, just try. :D
[Nexus 7 Android Development] Hubird:
I warn people that flashing this build may get their tablet in a bad state that isn't easy to rectify and you complain about capital letters :eek:

Capital letters, bold, italics, underline the end result is the same ,do a few upper-case words really offend you that much :D

[MENTION=4948627]daniel_hk[/MENTION]

Your efforts are appreciated and I don't hold you responsible for anything that goes wrong, we all know there are risks doing this sort of thing however my comment was warranted and if it saves others from being in the same predicament then mission accomplished

Hopefully you get to the bottom of the issue soon :good:
[Nexus 7 Android Development] pincher65:
at connection to the computer, you will see him as the APX device. but you have not

it can be broken buttons vol. try to use Wug's Nexus Root Toolkit . there is a mode for the "device in bootloop"