yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Curtis7990:
Are there specific instructions to install gapps?
[Nexus 7 (2013) Android Development] followmsi:
No.. As I don't own a Deb device I rely on you guys ;)

ro.telephony.get_imsi_from_sim=true

telephony.lteOnGsmDevice=1

Have a try and add the lines into your build.prop.

Right now I have no idea to make it working.

Different results from different testers.
[Nexus 7 (2013) Android Development] followmsi:
Since we use webview 62 (beta) the gapps installation problems should be fixed. (Pico packages)

Pls install stock gapps package using custom config file to include chrome into gapps installation.

https://xdaforums.com/showpost.php?p=73781660&postcount=630

Otherwise I have no idea what's going wrong for you ..
[Nexus 7 (2013) Android Development] Curtis7990:
I just didn't understand how to use the config file.
[Nexus 7 (2013) Android Development] memarama:
Look here: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Nexus 7 (2013) Android Development] Ænimal:
Battery life on my nexus got significantly worse (around 20% usage while idling), although I love having dt2w - maybe it can be optimized somehow..

Anyway, thanx for the rom
[Nexus 7 (2013) Android Development] followmsi:
For next Kernel/ROM all the stuff is disabled by default.

https://github.com/followmsi/androi...mmit/067014f55e5167b48fa3a2e04ec925d0fbfd43a2

You will need to activate the dt2w features via Kernel-Auditor, EX-manager or similar tools.

Same "battery" problem was on Nougat .. one reason for changing from EX sources to "stock" lineageos kernel sources at this time.

Not sure if this can be improved when activated ..

Cheers
[Nexus 7 (2013) Android Development] Curtis7990:
Thanks, gmail still crashes
[Nexus 7 (2013) Android Development] lollyjay:
... and this is after doing a fresh install?
[Nexus 7 (2013) Android Development] logitechor:
For me Gmail crashes upon opening too. I get the notification of an e-mail though.
[Nexus 7 (2013) Android Development] grmcdorman:
Installed the latest 8.0 beta [beta-8.3, from Oct 25th.], with micro OpenGapps as an upgrade to your 7.1.2 ROM. Did not clear data partition.

Some issues with apps as follows. The two that are big issues for me are Netflix and Google Play Books, as I use both frequently. I may be able to use something else for Google Play Books, as the books I read are purchased non-DRM ebooks.

Many applications need to be uninstalled and then reinstalled to get them working. May be because I didn't clear the data partition.

Crashing apps, even if the app is uninstalled and then re-installed:

Netflix.

As others have reported, GMail crashes. Fortunately this is not my primary e-mail client, I use Inbox, which works fine.

The following other Google apps also crash, even if uninstalled and then re-installed:

Google Newstand (opens but crashes as soon as I try to scroll)

Google Arts & Culture

Google Opinion Rewards

Google Play Books, when trying to open a book even if it's downloaded

Amazon App Store doesn't work, just says "Something went wrong" even after uninstalling/reinstalling.

Less important:

Adobe Acrobat Reader crashes. Uninstalled; there are other solutions for viewing PDFs.
[Nexus 7 (2013) Android Development] grmcdorman:
OK, re-installed and cleared the data partition this time. Apps are much happier now, pretty much everything works, including Netflix and Google Play Books. Lesson: when installing a new ROM like this, also clear your data partition.

Titanium Backup is also very, very useful for this, as it can restore the apps with their data, so with rare exceptions you don't loose anything.

EDIT: By the way, the OpenGapps `aroma` installer is very useful to select a subset of the Google apps you want installed. I don't use GMail, so I don't know if installing it that way will fix things.
[Nexus 7 (2013) Android Development] js89:
Had same 20% drain on previous versions, with beta 8.2 I get good battery life when idle (so i'm still on that one). I don't know what caused it, but I noticed my own gapps-config included google camera, so might be my fault.

I've flashed kernel with only dt2w enabled, not noticed such big drain from that. You could enable powerkey suspend to wake gestures in order to manually disable dt2w and the like when you put the device to sleep. Note you then should also disable ambient display to prevent the screen from turning on and re-enabling dt2w.

No issues with gmail or any other apps. But sometimes the device is unable to find any wifi network or connect to a network, rebooting fixes that.
[Nexus 7 (2013) Android Development] MikiGry:
Im using latest 7.1.2 build. Recently i noticed, that idle battery consumption became much bigger. It used to be ~0,5%/hour and now its almost 2%/hour. I installed BBS and there isnt anything wrong. Tablet goes into deepsleep as it should, doze is olso working. Im using greniffy to calm down Facebook Messenger. What is eating my battery ?

Note : im using ElementalX kernel

I tried restarting it a few times - is didnt help
[Nexus 7 (2013) Android Development] followmsi:
Keep the kernel from ROM, do not use EX Kernel and check battery life again.
[Nexus 7 (2013) Android Development] MikiGry:
The problem is, that I have been using EX for about a month and idle drain was around 0.5%/hour and since one week it increased :/
[Nexus 7 (2013) Android Development] followmsi:
The Nougat ROM was using EX kernel sources for some time.

Due to battery drain issues I have moved to "stock" lineage kernel sources.

Already some time ago .. not since last month only.

I guess it's related to activated dt2w .. etc. .. not sure.

There are no (planned) changes for Nougat kernel anymore ..

Looking forward for the EX Oreo version .. ;)
[Nexus 7 (2013) Android Development] MikiGry:
I dont use dt2w and similar features...
[Nexus 7 (2013) Android Development] craigholm:
With the AOSP_8.0.0_r13_OPR1.170623.027_flo-ota-eng.followmsi_BETA-8.zip ROM, I can't enter a hex key as the Wi-Fi password.

Wi-Fi allows a password between 8 and 63 characters, or the actual key itself (64 hex characters). After flashing it with this ROM, however, the connect button is disabled if the length is more than 63.

With the 7.1.2 ROM it works correctly. I have another device running Oreo and this isn't an issue.
[Nexus 7 (2013) Android Development] followmsi:
Need to check .. will take time.

Will not validate on Nougat, I assume you are right and it's working ;)

Just tested on another device too .. Oreo AOSP ROM .. does not work either.

Only 63 digits .. does not accept 64 hex.

Which Oreo ROM is working ? .. for which device ?

EDIT:

Had a quick look ..

https://productforums.google.com/fo...ZLTTQlGJ4;context-place=forum/phone-by-google

Maybe "your" Oreo ROM has been fixed and we can cherry-pick the changes ..
[Nexus 7 (2013) Android Development] craigholm:
After further investigation, it looks like my Oreo device (a Nexus 5X) actually has the same issue--it seemed to work because the networks I set up before upgrading it (from Nougat) continue to work correctly, but it isn't possible to set up new networks without running into the same problem.

So, it definitely seems like a bug in the Oreo settings app, not a specific ROM. Thank you for your quick response.
[Nexus 7 (2013) Android Development] MikiGry:
Flo decided to fix itself. I have fully charged it during night, unplugged it in the morning and left it connected to WI-FI. And this is what i saw a few mintues ago

After 9 hours of standby it only ate 2% battery. So drain is gone. I hope its not going to come back
[Nexus 7 (2013) Android Development] MadHacker:
finally got the latest version (beta 8.3) to work with opengapps pico without play services crashing all the time..... Any on else not have OK GOOGLE working ????
[Nexus 7 (2013) Android Development] drewski_1:
OK Google working for me, but using Stock package with a GApps-Config file.

IIRC, you need Google Search as a system app, which isn't in Pico. you could try Nano, the next size up which has Google Search . . . or did that cause errors for you too?
[Nexus 7 (2013) Android Development] vagelis74:
What camera app working with rom;why after flash the rom lose twrp recovery;can boot to bootloader but cannot boot to recovery,recovery error f2fs
[Nexus 7 (2013) Android Development] followmsi:
There are still a few issues left .. for this reason I would like to keep the name BETA :)

AOSP_8.0.0_r28_OPR1.170623.032_flo-ota-eng.followmsi_BETA-9.zip

AOSP_8.0.0_r28_OPR1.170623.032_deb-ota-eng.followmsi_BETA-9.zip

Changes: (since BETA-8)

- New month .. new sources -> Nov 2017 security patches -> android-8.0.0_r28

- Launch QMUXD process as root user

- Enabled FunctionFS (USB)

- Build hidl health & thermal implementation

- Removed "earlysuspend" hack in system/core

- Added "signature spoofing" base patch (patch included; but not working yet)

- Created rild service in init.rc (deb only)

- Added HIDL radio implementation (deb only)

- Added gps.conf (deb only)

NFC: on/off toggle still buggy

Camera: We build HAL1 camera now .. like in Lineage too.

The AOSP camera app is NOT working.

Apps like the camera below are working fine ..

https://play.google.com/store/apps/details?id=com.peace.SilentCamera

RILD (deb only):

- Data connection (3G/LTE) seems still to have problems.

- No changes are done for RILD anymore .. same changes as in 8.3

New kernel -> 2017-11-06

- DT2W, Sweep2sleep, Sweep2wake: disabled per default

(Pls use EX-Manager, Kernel-Auditor or similar apps/tools to enable DT2W, Sweep2sleep and Sweep2wake)

- Security patch for "KRACK" attack

- Latest Lineage changes

Sources:

https://github.com/followmsi/manifests/tree/flo-deb-aosp-o

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-11-06

Enjoy :p
[Nexus 7 (2013) Android Development] gege622:
It's OK Followmsi, dirty flashed your ROM.

I've installed your photo app, it works too.

Actually, I download and install EX-Manager to test the DT2W fonction.

Thank you.

---------- Post added at 23:06 ---------- Previous post was at 22:51 ----------

Could you, please, gimme a link for a EX-Manager ?

Mine crash on my nexus
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks msi. Your work is much appreciated...

Thanks again.
[Nexus 7 (2013) Android Development] lollyjay:
Tru Dat!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Indeed... ?
[Nexus 7 (2013) Android Development] jaucar:
Thanks for your work.

I have a problem with my device. the screen has ghost touches in a very small part down.

I can not swipe the TWRP button.

Would there be a way to install rom next to the kernel and super SU by ADB?
[Nexus 7 (2013) Android Development] followmsi:
Yes .. either you sideload the ROM.

https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/

Or if you have the ROM files on your device already use adb shell command ..

"adb shell twrp install /sdcard/file-name.zip"

Kernel.zip and supersu.zip should work too.

Good luck ..
[Nexus 7 (2013) Android Development] followmsi:
I am using kernel auditor actually ..

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
[Nexus 7 (2013) Android Development] gege622:
Thanks a lot,

I've activated the DT2W, it works !

I'll follow the battery.

Thanks again
[Nexus 7 (2013) Android Development] ZakSeven:
Google report sign-in from Nexus 7(2012)

Any particular reason why the device is identified as Nexus 7(2012) instead of 2013? I check with system check and all seem fine and properly seen as FLO. This seem to be causing issue with Google Play Services as the device is getting and error 505 when trying to install. The info, seem to lead that this is cause when the incorrect version is attempted to be installed. Wonder if the 2 are related.

I have tried all the troubleshooting and now on 3 wipe/re-install and the issue always return. Installing AOSP71..1 V2, Nano Gapps, and SuperSU. The device was running everything fine on rooted 6.0.1.

Zak
[Nexus 7 (2013) Android Development] Rammv:
I had the exact same thing happen with your updated twrp build installed and flashed rom, gaps, and su,in the correct sequience.I had to use power and down button to get into fastboot and fastboot flash recovery again and restored a backup. Never tried to use f2fs. Don't know what happened either
[Nexus 7 (2013) Android Development] followmsi:
How do you see that it's identified as 2012 version ?
[Nexus 7 (2013) Android Development] js89:
I assume he means the confirmation email you get when you first login to your google account on the device. The email says new login on Nexus 7 (2012) instead of Nexus 7 2013.

But last time I checked this was also the case with the official Marshmallow image from google, so I assume it's a fault on their side.
[Nexus 7 (2013) Android Development] followmsi:
This one? :)

https://support.google.com/nexus/forum/AAAANseOu18LGAU6qG--uA/?hl=en

When you get error 505 you can install the same apk via adb without problems?

Or do you get failure message via adb too ?
[Nexus 7 (2013) Android Development] js89:
Yep. :)

In my case I got a 505 in the play store when installing calendar using pico and nano gapps. Didn't try adb but installing the apk from apkmirror went just fine.

With the pico and nano gapps the google app also showed some strange behavior (search bar disappearing from the homescreen) and I was unable to select Google Now as launcher in settings.

However installing micro gapps solved all of the above. :) :good:
[Nexus 7 (2013) Android Development] ZakSeven:
As mentioned, this happened when sign-in the device after a wipe and installing this ROM. Notification from Google were sent to all my other device and associated email that I was sign into a new device Nexus 7(2012). When checking my devices on recently used device I can see both Nexus 7(2013) [While it was on 6.0.1] and now a Nexus 7(2012) of course those are essentially the same device as I never owned a 2012 edition.

Furthermore, when on Play.google.com and trying to do an install it now show, in addition of all my other android device, two Nexus 7. One with a Last Used: Null and the other with Last used date the day I installed 7.1.1. So essentially in my case, Google now think I own a Nexus7 on 7.1.1 while there's still a Nexus7 on 6.0.1 instead of thinking it was upgraded.

This never happened before with any of my devices to be reported incorrectly, and I have android device since original Motorola Zoom (still in use) and first HTC G1 (long retired). Not sure where it comes from but may be the source of installation issue for some if the device is incorrectly shown like that. I will remove the extraneous one from my list of device, it may help but if it is somehow incorrectly seen by the store that may explain some install issue.

Zak

---------- Post added at 07:34 AM ---------- Previous post was at 07:28 AM ----------

Interesting, in my case never had the issue on any prior wipe/install on that device. The fact that it is now showing as two devices in my account is also strange and maybe indicative of an issue on Google side of thing.

I did no install via adb, but simply pulling APK of the offending app from another device with extractor and then installing on N7 worked for me.

Zak
[Nexus 7 (2013) Android Development] followmsi:
Sorry .. can not replicate your issue.

I do install various ROMs onto the flo .. also for testing.

Never had this problem .. additional registered devices.

If you keep your old data partition there might be issues.

But after factory reset there should not be any issues.. should :)

For me pico version works fine .. I want play store only.

The few google apps, calendar too, are installing fine ..no error 505.

Pls try micro version as suggested above ..

Did you try older/newer gapps versions too ?

Sorry again .. I am not able to help you better here ..
[Nexus 7 (2013) Android Development] Tomen8r:
I can confirm the Nexus7(2012) build listed in settings, with the build previous to this one. Since then I had changed ROMS to LineageOS last week and no longer have this AOSP installed
[Nexus 7 (2013) Android Development] followmsi:
If you get this message..the custom recovery image has been overwritten with stock recovery - which is not able to "understand" the fstab.flo entries for f2fs.

Can't tell you why SuperSU installation has not successfully blocked "install-recovery.sh" script and has removed the custom recovery.

For me it's working fine .. I am using v2.79 ..
[Nexus 7 (2013) Android Development] revcp:
Yes, I'm using your TWRP, although I'm using 3.1.0-0, as I can't find where to download 3.0.3-3. Rooted, yes. Do you happen to have a link for the gapps that everyone is using? Perhaps I'm grabbing the wrong one.
[Nexus 7 (2013) Android Development] followmsi:
I believe you :)

It seems some people do have problems ...

Will have a look again ... there might be something related to this topic.

Maybe we need a V3 release :)
[Nexus 7 (2013) Android Development] revcp:
Arrrgh! I finally installed a TWRP that I could boot into--twrp-3.0.2-0-flo.img from the official Team Win site. I wiped, installed the Rom, but now when I try to install gapps (open_gapps-arm-7.1-nano-20170314.zip) I get the message **incompatible Android ROM detected** THis GApps pkg is for Android 7.1.x ONLY... It's asking for a gaps for 6.0.1. What gives?
[Nexus 7 (2013) Android Development] followmsi:
Gapps checks get.prop .. but from recovery - which is compiled on Android 6. :)

There are 2 issues ..

1. Loosing custom recovery

2. Not being able to install gapps successfully

When you install TWRP version 3.1.0-0 and install supersu only.

Do you keep the custom recovery ?

This has to work .. independent of gapps.

Due to system less rooting install the OTA again, or just the elementalx kernel only .. and then install supersu.zip again - to let supersu modify the ramdisk correctly.

Once done, reboot into recovery and back into system - twice :)

All ok ?

You did not loose TWRP ?

Now start with gapps installation only ..
[Nexus 7 (2013) Android Development] revcp:
Looking good so far. Recovery is staying. GApps 7.1 pico has installed.

Now rebooting to see whether the Google Apps are actually there.

Yay! Playstore is actually there! Thank you so much! No idea what the issue was, but hope it's now behind me.
[Nexus 7 (2013) Android Development] followmsi:
Checked this one too .. works for me.

If I open my case there is no message.

I can see the system is starting to get all my messages - even the old ones which I got on other devices before.

Pls test in V3 again .. uploaded soon :)
[Nexus 7 (2013) Android Development] followmsi:
Nice .. Don't know what you have done differently .. but now you have done it correctly ;))

It's important to use a "fresh" boot.img to let SuperSU.Zip do the work ..

The ramdisk needs to be modified correctly in times of systemless rooting.

This way we make custom recovery like TWRP persistent !

Enjoy your 7.1.1 installation ..

Cheers
[Nexus 7 (2013) Android Development] followmsi:
AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v3.zip

AOSP_7.1.1_r28_N6F26U_deb-ota-eng.followmsi-v3.zip

V3

For deb and flo I have added the latest release keys (android 6) -> build.prop.

This should help to identy the device clearly as deb or flo device.

flo:

PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=razor \
BUILD_FINGERPRINT=google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys \
PRIVATE_BUILD_DESC="razor-user 6.0.1 MOB30X 3036618 release-keys"

deb:

PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=razorg \
BUILD_FINGERPRINT=google/razorg/deb:6.0.1/MOB30X/3036618:user/release-keys \
PRIVATE_BUILD_DESC="razorg-user 6.0.1 MOB30X 3036618 release-keys"

I hope this solves all the Nexus 7 (2012) issues .. at least from my side :)

Enjoy ..
[Nexus 7 (2013) Android Development] nbehary:
Yeah, I took those out of [MENTION=4318865]DevSwift1[/MENTION]'s stuff because I thought I had found a better fix. (cause that still seems hacky to me) I don't think I really did though.
[Nexus 7 (2013) Android Development] rajsris:
New Rom appears to be the correct designation in Google Play as expected.

[MENTION=5480152]followmsi[/MENTION], Thanks so much for keeping our Nexus 7 alive the way Google always intended! Great ROM :)
[Nexus 7 (2013) Android Development] jaucar:
How should I do it? In a terminal session, from the device itself or connecting it to a PC?

Thanks again
[Nexus 7 (2013) Android Development] followmsi:
Yes .. use ADB when connected to PC/Mac.

Have a try to type into recovery console .. but without "adb shell" in front .. just "twrp install /sdcard/file.zip"

Otherwise .. Google search is your friend ;)

Cheers
[Nexus 7 (2013) Android Development] MadHacker:
I had problems for the first time ever with gapps installing period.

Where exactly does the config file go, inside the gapps zip file?

Thanks
[Nexus 7 (2013) Android Development] jaucar:
Thanks for your help.

Using the TWRP terminal, it has been very easy.

Thanks again
[Nexus 7 (2013) Android Development] js89:
Same folder as gapps zip file, see https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#gapps-config-file-location

Rename to .gapps-config or gapps-config.txt
[Nexus 7 (2013) Android Development] Deeco7:
Does this rom support Timur's Kernel?
[Nexus 7 (2013) Android Development] followmsi:
This ROM should support all Oreo kernels.

I guess Timurs kernel has not been prepared for Oreo.

There are quite some changes required for Oreo.

Hope this helps ..
[Nexus 7 (2013) Android Development] rajsris:
I cleaned installed beta9, coming from beta8.3.

I wiped system, data, dalvik, cache, and then installed the rom, magisk, and opengapps nano. No complaints about space issues. I even deleted the Android and data folders in sdcard.

All installed fine, but Google play services always crashes after connecting to WiFi. Even if I skip setup and then log into Google play/Gmail, it will still crash.

I will retry with opengapps pico today.
[Nexus 7 (2013) Android Development] lollyjay:
See posts on how you to flash stock GApps with gapps config file. That is the only way to get what you need. Just place the gapps config file in the same folder as gapps zip
[Nexus 7 (2013) Android Development] followmsi:
If you go into developer settings and check webview implementation .. which version do you have ?
[Nexus 7 (2013) Android Development] mick3lson:
I've installed 8.0.0_r28_OPR1.170623.032 BETA-9 all work flawlessy on nexus 7 2013 wi-fi, only minor issue is DoubleTap2Wake that not work with kernel adiutor. I would know if the kernel is integrated in the firmware, i've installed "flo-deb-aosp-kernel-oreo-20171106" I don't know if it's correct for nexus 7 wifi version.
[Nexus 7 (2013) Android Development] rajsris:
It actually says webview implementation: None

Ultimately, the only way I got it to work was to use stock opengapps with followmsi's gapps-config file. webview had an update upon first boot, so something wasn't getting set up with that app in earlier attempts

EDIT2: The camera that came with beta9 seems to work for me

EDIT3: Netflix somehow worked on this version for me
[Nexus 7 (2013) Android Development] followmsi:
I did test clean install without opengapps at all .. you can check developer settings and you will see webview 62.xx is active.

If you install opengapps the problems starting :)

Not sure why webview is not recognized after gapps installation .. this problem happens on other devices too.

But as you said .. to bypass the problem just install chrome via opengapps.

Hopefully we will find the root cause soon ..

Cheers