[ROM & discussion][7.1.2_r11][Grouper|Tilapia][3May2017]AOSP - UNOFFICIAL

Search This thread

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,342
Hong Kong
In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there. :D

Known Issues: :(
 1. AOSP Camera App
 The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that.​
 2. "E:unknown command [log]"
 If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP.​
 3 Please report.

Tips: ;)
 1. DT2W
 At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results.​
 2. Built-in File Explorer
 There is an built-in file explorer in AOSP. We can explore the files as well as installing apks. ;)
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)​
Change log: :)
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
 - Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
 - Android-7.1.2_r5 (N2G47J)
 - PerformanceControl: boot up settings fixed
 - Fix Wifi hotspot
 - Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
 - Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
 - Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
 - Android-7.1.1_r13 (N6F26Q)
 - Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
 - Android-7.1.1_r6 (NMF26Q)
 - SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
 - Android-7.1.1_r4 (NMF26O)
 - Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
 - Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
 - Android-7.1.0_r4 (NDE36P)
 - Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
 - Android-7.0.0_r14 (NBD90Z)
 - Shield the occasional crash in MTP Document provider
 - USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
 - Android-7.0.0_r6 (NRD90U)
 - latest DC kernel (Android-7.0 branch)
 - PerformanceControl: version 2.1.6
 - Find a way to fix the hwcomposer for video/audio playback, need to review later
 - A few sepolicy patches for Gapps and Mediaserver
 - SELinux: Enforcing

Downloads: :highfive:
 Hosts: Android File Host MEGA mirror: 百度网盘
 Note: I only tested it in TWRP 3.0.2.
     PerformanceControl app requires ROOT access.
     Root access can be obtained by the systemless SuperSU from @Chainfire.
 Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested

Sources: :cool:
 Sources in github

Credits: :good:
 ** Definitely the AOSP
 ** The AndroidFielHost provide a FREE host with no limits and expiration.
 ** All the developers who help the Nexus 7 (2012) development
 ** All those who donate and/or help the developers. Giving us the resources and reason to carry on.

Donations: :angel:

2m8C9z7xQ5_src.png

show.htm
 
Last edited:

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,342
Hong Kong
Discussions
Anyone has any idea are welcome to post here :)
  • DT2W
    Sometimes it won't wakeup after a long DEEP_SLEEP
    When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
  • Fail after reboot
    Code:
    Supported API: 3
    E: unknown fs_type "f2fs" for /cache
    E: Can't mount /cache/recovery/last_locale
    Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
    @millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
    I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
    It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
    There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
    When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
    Code:
    /dev/block/platform/sdhci-tegra.3/by-name/APP		/system		ext4	ro		wait
    /dev/block/platform/sdhci-tegra.3/by-name/CAC		/cache		f2fs	noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry	wait,check
    /dev/block/platform/sdhci-tegra.3/by-name/CAC		/cache		ext4	noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic	wait,check
    Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.

    How to recover?
    Naturally, you have to flash TWRP again.
    First of all, you need to boot into bootloader (fastboot mode)
    Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
    If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
    If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
    1. Connect to a charger.
    2. Press the power button until you see the charging image
    3. Release the power button immediately.
    4. After that, press the volume down button first, and then the power button.
    It would go to the bootloader. ;)

    Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.

    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.
 
Last edited:

abhifx

Senior Member
  • Feb 20, 2011
    1,497
    735
    Chandigarh
    Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.

    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.
     

    ho0o0o11111

    Senior Member
    Jun 18, 2007
    198
    70
    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.
     

    daniel_hk

    Inactive Recognized Contributor
    Nov 12, 2012
    1,634
    5,342
    Hong Kong
    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.

    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.
     
    • Like
    Reactions: snoeky

    ho0o0o11111

    Senior Member
    Jun 18, 2007
    198
    70
    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.

    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://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
    still trying...
    Any helps would be appreciated.
    Thanks.
     

    daniel_hk

    Inactive Recognized Contributor
    Nov 12, 2012
    1,634
    5,342
    Hong Kong
    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://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
    still trying...
    Any helps would be appreciated.
    Thanks.

    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! ;)
     
    Last edited:

    ho0o0o11111

    Senior Member
    Jun 18, 2007
    198
    70
    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! ;)

    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.
     

    daniel_hk

    Inactive Recognized Contributor
    Nov 12, 2012
    1,634
    5,342
    Hong Kong
    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.

    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!
     

    webdroidmt

    Senior Member
    Dec 20, 2011
    1,674
    1,156
    NJ
    @daniel_hk

    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
     
    Last edited:

    paasoares

    Senior Member
    Oct 3, 2006
    155
    54
    Lisbon
    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
     
    • Like
    Reactions: daniel_hk

    3yan

    Member
    Jul 8, 2015
    7
    2
    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 ?
     

    fat-lobyte

    Senior Member
    Oct 3, 2012
    110
    27
    Hi, currently testing your ROM, looks awesome!

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

    Code:
    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.
     

    daniel_hk

    Inactive Recognized Contributor
    Nov 12, 2012
    1,634
    5,342
    Hong Kong
    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

    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! ;)

    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 ?
    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!

    Hi, currently testing your ROM, looks awesome!

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

    Code:
    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.

    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
     
    Last edited:

    fat-lobyte

    Senior Member
    Oct 3, 2012
    110
    27
    Code:
    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 [email protected]
    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.
     

    frov

    Senior Member
    Dec 31, 2014
    428
    188
    Tilburg
    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
     

    paasoares

    Senior Member
    Oct 3, 2006
    155
    54
    Lisbon
    Code:
    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 [email protected]
    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.

    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
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 28
      In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
      Here is for sharing of experiences and discussions.
      There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there. :D

      Known Issues: :(
       1. AOSP Camera App
       The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that.​
       2. "E:unknown command [log]"
       If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP.​
       3 Please report.

      Tips: ;)
       1. DT2W
       At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results.​
       2. Built-in File Explorer
       There is an built-in file explorer in AOSP. We can explore the files as well as installing apks. ;)
      Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)​
      Change log: :)
      Code:
      [COLOR="Blue"]2017/5/3[/COLOR]
       - Android-7.1.2_r11 (NHG47L)
      [COLOR="Blue"]2017/4/9[/COLOR]
       - Android-7.1.2_r5 (N2G47J)
       - PerformanceControl: boot up settings fixed
       - Fix Wifi hotspot
       - Performance patches
      [COLOR="Blue"]2017/3/8[/COLOR]
       - Android-7.1.1_r28 (N6F26U)
      [COLOR="Blue"]2017/2/8[/COLOR]
       - Android-7.1.1_r21 (NOF26W)
      [COLOR="Blue"]2017/1/6[/COLOR]
       - Android-7.1.1_r13 (N6F26Q)
       - Camera: Fix video recording
      [COLOR="Blue"]2016/12/16[/COLOR]
       - Android-7.1.1_r6 (NMF26Q)
       - SEPolicy update
      [COLOR="Blue"]2016/12/7[/COLOR]
       - Android-7.1.1_r4 (NMF26O)
       - Fix the Camera
      [COLOR="Blue"]2016/11/11[/COLOR]
       - Android-7.1.0_r7 (NDE63X)
      [COLOR="Blue"]2016/10/24[/COLOR]
       - Android-7.1.0_r4 (NDE36P)
       - Remove every recovery related resources
      [COLOR="Blue"]2016/10/14[/COLOR]
       - Android-7.0.0_r14 (NBD90Z)
       - Shield the occasional crash in MTP Document provider
       - USB and Bluetooth Tethering support enabled
      [COLOR="Blue"]2016/9/23[/COLOR]
       - Android-7.0.0_r6 (NRD90U)
       - latest DC kernel (Android-7.0 branch)
       - PerformanceControl: version 2.1.6
       - Find a way to fix the hwcomposer for video/audio playback, need to review later
       - A few sepolicy patches for Gapps and Mediaserver
       - SELinux: Enforcing

      Downloads: :highfive:
       Hosts: Android File Host MEGA mirror: 百度网盘
       Note: I only tested it in TWRP 3.0.2.
           PerformanceControl app requires ROOT access.
           Root access can be obtained by the systemless SuperSU from @Chainfire.
       Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested

      Sources: :cool:
       Sources in github

      Credits: :good:
       ** Definitely the AOSP
       ** The AndroidFielHost provide a FREE host with no limits and expiration.
       ** All the developers who help the Nexus 7 (2012) development
       ** All those who donate and/or help the developers. Giving us the resources and reason to carry on.

      Donations: :angel:
      11
      This latest AOSP Android-7.1.0_r4 builds are out.
      I have triple checked. Every recovery related resources are removed.
      If there is still reboot issue, it can not be from this. ;)
      9
      This doesn't work.
      adb and fastboot commands can't be passed to tablet. Tried many times.

      Same problem here. if there is any solution, please tell me

      Try reinstall adb drivers.

      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,

      Looks as if f2fs for cache is not supported by your recovery. You can try to wipe cache / reformat cache with ext4.

      Sent from my HTC One_M8 using XDA-Developers mobile app

      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
      8
      The latest Android-7.1.1_r6 test builds are out. ;)
      8
      The latest Android-7.1.1_r13 test builds are out. ;)