[ROM][6.0.1_r67][MTC20K][F2FS/EXT4]Android 6 AOSP on Grouper

[AndDiSa]

@gavster26 can you describe the steps what you have done and in which state you are now?

 

[gavster26]

@AndDiSa I fastbooted boot.img system.img then fastboot format cache then booted to system then booted to twrp to flash the latest ota zip

 

[AndDiSa]

Well there is no need to fastboot flash boot.img / system.img if you later on flashing the OTA. TO be sure that everything is clean, I would do the following steps:
- fastboot erase boot
- fastboot erase system (-w if you would like to erase userdata, too)
- fastboot flash recovery (latest TWRP, if not already installed)
- fastboot reboot recovery
- flash latest OTA
- flash gapps
- reboot

 

[gavster26]

Well there is no need to fastboot flash boot.img / system.img if you later on flashing the OTA. TO be sure that everything is clean, I would do the following steps:
- fastboot erase boot
- fastboot erase system (-w if you would like to erase userdata, too)
- fastboot flash recovery (latest TWRP, if not already installed)
- fastboot reboot recovery
- flash latest OTA
- flash gapps
- reboot

I tried just flashing just the ota zip but it wouldn't boot past the splash screen for some reason and it wouldn't logcat either. Is there a way to see if my storage is corrupt

 

[AndDiSa]

@gavster26 Not that I am aware of ...
Are you in a bootloop? In that case the first thing I would try is wiping data. If this does not help either you could try to boot to recovery by pressing the vol- button only and then in recovery have a look at /proc/last_kmsg probably there you can find a hint what's wrong during boot.

 

[gavster26]

@gavster26 Not that I am aware of ...
Are you in a bootloop? In that case the first thing I would try is wiping data. If this does not help either you could try to boot to recovery by pressing the vol- button only and then in recovery have a look at /proc/last_kmsg probably there you can find a hint what's wrong during boot.

@AndDiSa the os is running fine it just seems to think there's no storage

 

[AndDiSa]

@gavster26 that's really strange ... did you already try a fsck on /data (/dev/block/platform/sdhci-tegra.3/by-name/UDA)? Probably it's corrupt and it cannot be mounted during the boot.

 

[gavster26]

@AndDiSa no I don't know what that is lol

 

[AndDiSa]

@gavster26 here the steps in short
- boot into recovery
- connect your pc with the device
- open an adb shell on your device
- umount /data
- umount /sdcard
- e2fsck /dev/block/mmcblk0p9 (if your /data partition is ext4 formatted)
- fsck.f2fs /dev/block/mmcblk0p9 (if your /data partition is f2fs fromatted)

But you probably should be a bit more familiar with these things before using it.

 

[kc8sbv]

Mine is running great, and TWRP reports its size as 1 gig approximately. What size storage are yours running???

 

[thierry+]

Can you enable Blutooth V4.0 (BLE) on this ROM?

Hi AndDiSa i love this ROM and it has been the only one i have used during 2016 when i changed from stock lollipop. Can i implore you to consider one last task for this ROM before you drop its development completely and that is to enable BLE. Apparently the BT chip has the capability but was not enable as cited
in this link....http://stackoverflow.com/questions/20669590/ble-on-nexus-7-me370t-with-android-4-4-2

"Basically, it seems that the Broadcom Bluetooth chipset within the 2012 Nexus 7 is Bluetooth 4.0 LE/Low Energy (BLE) capable, however, Google never certified it as such, only certifying to the then current v3.0 spec."

This link...https://github.com/manuelnaranjo/android_device_asus_grouper/commit/31756f3c0f364c9c7d07e8813a8b806ec0ddaded....has patches to enable it.

it has also been done by this chap here....http://forum.xda-developers.com/showpost.php?p=44948765&postcount=65.

I would add that this is probably relevant to the Android 7 development that you have started on this forum. I wait expectantly.

regards

 

[lollazzo]

where I can download superuser?

 

[AndDiSa]

http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip


Sent from my Nexus 7 using XDA Labs

 

[lollazzo]

I am a newbie with nexus toolkit.
What I have to do to flash your rom? I have to put the file into the tablet and then flash it under the recovery, isn't it?

 

[AndDiSa]

@lollazzo yes, it's sufficent to flash the ROM, gapps and then SuperSU (if you would like to have su enabled). Nevertheless I would suggest you to try the 7.1.1 version. It's more up to date and more stable than the 6.x one.

 

[eschoenawa]

Forced "Do not disturb"-Mode

A minor bug I found: reducing the notification sound level to zero forces the "Do not disturb"-mode on, that doesn't happen on my other Android 6 device.

 

[Geko45]

A minor bug I found: reducing the notification sound level to zero forces the "Do not disturb"-mode on, that doesn't happen on my other Android 6 device.

That's not actually a bug, that's default AOSP behavior. My Nexus 5 (running MM straight from Google) behaves like that. I don't really like it either, but it is what it is. Your other MM device must have overridden it somehow. I do think there is an Xposed module that can change that behavior.

 

[Moosach]

Yes, I can test this myself, but it costs a lot more time than a quick answer here from some friendly fellow who did it already: Is this 6.0.1 AOSP here faster than 7.1.2 AOSP?

I'm using my grouper only for car navigation with TomTom app (because of the excellent traffic informations). For this usecase I'm looking for the best custom ROM, because the original last 5.somewhat is very slow, espc. when booting ...

Any comments or recommendations?

Thanx in advance.


Update: I'm now running the optimized CM11 version of user animatrix999 and am quite happy with it. Just what I was looking for.

 

[konnarides]

Works GREAT,, for Nexus 7 2012, very good !!!

 

[skymaule]

Sound from headphone jack

I've installed the 20160908 build for 6.01 and it seems to be working very well. One problem is that when headphones are plugged into the jack, no sound from the phones nor does it cut off the speaker sound. So, in essence sound only comes from the speaker whether or not headphones plugged in. Has this been reported? Could this be a hardware problem, rather than software?

Thanks for any reply ...Edwin