yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] lt6669:
Latest 10 beta issue Flow hidden WiFi

Clean installed 10 beta with pico GAPPS. everything works as described.

-*- one issue that I have noticed is inability to connect to hidden WiFi networks-*- :-0

---------- Post added at 07:32 PM ---------- Previous post was at 06:35 PM ----------

Thank you for the quick reply.

Just tried it. (I don't have lock screen enabled) Worked on my Flo clean install.

I'm a happy camper :) :victory: :svetius:

---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------

How do you disable NFC? (It is enabled by default, and grayed out :eek: ) <-- Found my answer.

-*- Type in terminal app with root rights .. "svc nfc disable" -*-

-*- Reboot. -*- :) :victory: :svetius:
[Nexus 7 (2013) Android Development] OSully:
I did a totally clean install for beta 10.

I'll try going back to see if I continue to have an issue and let you know.

I appreciate your work, believe me, just wanted to make sure I reported the issue for me. :)
[Nexus 7 (2013) Android Development] jerethi:
Anyone else feel like it takes a really *big* swipe to unlock the lockscreen on flo? Maybe it's just me.
[Nexus 7 (2013) Android Development] Ambious:
Same for Deb.
[Nexus 7 (2013) Android Development] OSully:
Yep, this is one of those instances of swipe issues on the screen I've been mentioning.
[Nexus 7 (2013) Android Development] followmsi:
Yep .. seems to be a common issue since 8.1.

Pixel devices have this problem too.

Like here ..

https://support.google.com/pixelphone/forum/AAAAb4-OgUsXLkysgY70FM/

https://www.reddit.com/r/GooglePixel/comments/7ir9uu/since_81_swipe_to_unlock_is_harder/

Maybe it's fixed in next monthly google release ..

Happy New Year [emoji3]
[Nexus 7 (2013) Android Development] Ambious:
Same
[Nexus 7 (2013) Android Development] OSully:
No issues in my pixel 2 xl.
[Nexus 7 (2013) Android Development] Ch3vr0n:
Perhaps, but this isn't a pixel 2 topic. So it would be irrelevant even if you were

Sent from my Nexus 6P with Tapatalk
[Nexus 7 (2013) Android Development] OSully:
No **** Sherlock... Did you bother reading the post I quoted before you jumped at the opportunity to be a jackass?
[Nexus 7 (2013) Android Development] juyil:
Same issue for me on bluetooth. Try pairing new device it it shows no devices and bluetooth turns off and back on after a moment.

I do notice however that my pixel 2 xl wont detect the bluetooth device for some reason either, so maybe that part is related to December 8.1 release, but the bluetooth turning off and on seems odd and is limited to the nexus 7 only.
[Nexus 7 (2013) Android Development] followmsi:
Will have a look into BT.
[Nexus 7 (2013) Android Development] juyil:
I just updated my phone to Jan 2018 8.1 and bluetooth would connect to the device I wanted to connect to again. So I'm guessing that's pretty good confirmation there is an issue with Dec 8.1 bluetooth (besides the bluetooth oddly turning off and back on).
[Nexus 7 (2013) Android Development] Buratei:
Does otg+charging work on this? I guess I may have to become a guniea pig myself to find that out :D
[Nexus 7 (2013) Android Development] followmsi:
January 2018 .. BETA 11

AOSP_8.1.0_r6_OPM1.171019.015_flo-ota-eng.followmsi_BETA-11.zip

AOSP_8.1.0_r6_OPM1.171019.015_deb-ota-eng.followmsi_BETA-11.zip

Changes:

- Based on android-8.1.0_r6 -> Jan 2018

- Reverted back to standard AOSP webview version

- We do not build AOSP "su" binary anymore (/system/xbin/su)

- Enabled ZRAM -> enable SWAP to improve I/O (testing - we may disable again)

- Adding wakelock to several services -> improve battery "idle" life time

- Added overlay to fix "big swipe" issue on unlock screen.

- Removed old and unused overlays.

- Removed NFC from build -> temporarily - until it's fully working.

- Enabled "WITH_DEXPREOPT" -> to speed up first boot.

- RILD (deb only) -> switched back to "CAF" branch -(staging/linage-15.1-caf)

New kernel -> 2018-01-04

- Fresh kernel (tons of lineage updates .. also for ZRAM .. etc.)

Again big thanks to [MENTION=5120185]flex1911[/MENTION] for all his work !

Opengapps:

Fresh packages .. 20180103

https://drive.google.com/drive/folders/1IY1JrNDlkk7OjXutlX3zGeASfWpSsRdl

Sources:

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

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2018-01-04

Enjoy :p
[Nexus 7 (2013) Android Development] Ambious:
Thanks!

On Beta 11 (DEB) Bluetooth is still not working, but this time at least it's crashing so I can trace a logcat (attached), maybe something here can help.

Also, (and I've had this issue on Beta10 as well), Google Inbox keeps crashing. Also got a logcat, which goes as such:

--------- beginning of crash
01-04 15:39:53.762 11319 11451 E AndroidRuntime: FATAL EXCEPTION: PlacesApiCallExecutor-0
01-04 15:39:53.762 11319 11451 E AndroidRuntime: Process: com.google.android.apps.inbox, PID: 11319
01-04 15:39:53.762 11319 11451 E AndroidRuntime: java.lang.IllegalStateException: GoogleApiClient is not connected yet.
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at ffi.b(Unknown Source:4)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at ffo.b(Unknown Source:9)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at ffj.b(Unknown Source:37)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at dow.run(PG:47)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
01-04 15:39:53.762 11319 11451 E AndroidRuntime:	at java.lang.Thread.run(Thread.java:764)
01-04 15:39:53.794 11319 11451 E bta : caz Uncaught Android Crash on thread PlacesApiCallExecutor-0 with tid 627 on version 1.62.179885387.release
01-04 15:39:53.794 11319 11451 E bta : java.lang.IllegalStateException: GoogleApiClient is not connected yet.
01-04 15:39:53.794 11319 11451 E bta :	at ffi.b(Unknown Source:4)
01-04 15:39:53.794 11319 11451 E bta :	at ffo.b(Unknown Source:9)
01-04 15:39:53.794 11319 11451 E bta :	at ffj.b(Unknown Source:37)
01-04 15:39:53.794 11319 11451 E bta :	at dow.run(PG:47)
01-04 15:39:53.794 11319 11451 E bta :	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
01-04 15:39:53.794 11319 11451 E bta :	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
01-04 15:39:53.794 11319 11451 E bta :	at java.lang.Thread.run(Thread.java:764)
01-04 15:39:53.811 579 2212 W ActivityManager: Force finishing activity com.google.android.apps.inbox/com.google.android.apps.bigtop.activities.InitActivity
01-04 15:39:53.818 579 611 I ActivityManager: Showing crash dialog for package com.google.android.apps.inbox u0

Clearing data and reinstalling app didn't fix it, and I'm currently googling the error but didn't find anything useful yet.
[Nexus 7 (2013) Android Development] followmsi:
No changes for Bluetooth are done for beta 11 .. tested connection on flo .. no issues.

But connected to already paired device.

Will test after clean install in the next days.

Now it shows battery status of the paired BT device in status bar ;)
[Nexus 7 (2013) Android Development] RazGame:
Dirty flashed from 10 Beta

When I toggle WiFi, it won't turn on and call system ui crash.

But I have this big on 10 beta too. Wifi for me very unstable.

And on 11 beta I have Bluetooth app stopped working, but bt is turn off.
[Nexus 7 (2013) Android Development] dealpapa1:
Does this beta 11 has the security patch from Jan 2018? Is camera working now? Thanks. :good:
[Nexus 7 (2013) Android Development] jerethi:
"Based on android-8.1.0_r6 -> Jan 2018"
[Nexus 7 (2013) Android Development] juyil:
Installed Jan 8.1 flo update.

Not sure if this is relate to the build or something with open gapps: When I wipe -> flash ota + gapps, then do a restore from cloud using google backup of my tablet from a couple days ago, I go through the setup, selecting apps to auto redownload, etc. Once that's done it brings me back to the prompt to setup a device rather than a progress page or something. I can then click skip device setup and it'll just proceed to the home launcher, and my apps are installing in the background.

Also confirmed, bluetooth still crashing, and not showing the device I want to pair to or any other available devices for that matter.

Curious, can I do anything to the tablet once I'm done with setup to make it where I can install the netflix app again? Figured wiping + clean install of the aosp would have removed any root I had setup? Perhaps its more of an issue that I'm using open gapps now?
[Nexus 7 (2013) Android Development] js89:
This works now. Thank you
[Nexus 7 (2013) Android Development] followmsi:
For me it sounds hacky as well .. :)

But it seems to be normal .. lineageos is doing it too.
[Nexus 7 (2013) Android Development] crazyates:
I got a weird problem: I'm running the newest TWRP from the link in OP. I did a wipe of everything (Dalvik, system, Data, Internal Storage, & cache). I'm using EXT4, not F2FS. I try to install the zip, and I get this message:

"E3003: Can't install this package (Tue Mar 14 09:45:04 CET 2017) over newer build (Thu Mar 16 14:06:36 CET 2017)."

It does it with v3 and v2. The original version seems to work fine.
[Nexus 7 (2013) Android Development] followmsi:
Again :)

Yes .. due to newer TWRP version :)

Like discussed in this thread already ... AOSP puts automatically a line into the OTA package ..

(!less_than_int(1489585876, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Wed Mar 15 14:51:16 CET 2017) over newer build (" + getprop("ro.build.date") + ").");

TWRP is newer - so it fails.

Pls use this versions below ... I removed this single line now :)

AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v3_no-check.zip

AOSP_7.1.1_r28_N6F26U_deb-ota-eng.followmsi-v3_no-check.zip

The next build will have newer date - so the problem will not occur.

Cheers
[Nexus 7 (2013) Android Development] ZakSeven:
Installed V3 and the initial identification was fine. I also used gapps micro to see if that prevent some issue experienced with G apps. So far no problems there either. Google now, play services and gmail are fine.

Good job.

Zak
[Nexus 7 (2013) Android Development] crazyates:
Thanks! I figured it was TWRP related, but I didn't see the no-check versions on the Drive.

It's all up and working. Thanks again!
[Nexus 7 (2013) Android Development] followmsi:
This is an annoying issue .. always comes back - if there is a new TWRP available :)

As we work with the sources .. I removed this line now - finally - forever :)

For reference ...

https://github.com/followmsi/platform_build/commit/0aaef274189f1a9821499dde0e98e5f2527a4769

Cheers
[Nexus 7 (2013) Android Development] Isambard Prince:
From Google:

"The Assistant will be available on Android Marshmallow and Nougat phones with Google Play Services, this does not include tablets."

Via Android Police:

http://www.androidpolice.com/2017/0...der-assistant-rollout-will-not-reach-tablets/

Google Assistant arrived on my N7 2013 FLO a few days ago.

I am using v1 of this fantastic ROM.

Is this just normal for AOSP?

Just curious. Thanks!

Edit: Flashed open gapps micro. I'm wondering if I somehow ended up with a phone Google Play Services later on. Got open gapps from the official app in the Play Store rather than the website.
[Nexus 7 (2013) Android Development] rajsris:
I've actually been trying to get assistant on this, and it never was activated for me unless I did a Google pixel experience zip
[Nexus 7 (2013) Android Development] rajsris:
I would suggest f.lux app from the Play Store to enable night mode. Requires root, but is exactly like my Pixel with night mode.

https://play.google.com/store/apps/details?id=com.justgetflux.flux

I even use the exact same app on my Windows PC.

Thanks again [MENTION=5480152]followmsi[/MENTION] for keeping our device great! ElementalX is also working great with f2fs data and cache.
[Nexus 7 (2013) Android Development] nigelhealy:
So today I fastboot flashed TWRP_flo_3.1.0-2.img, into recovery, did a full wipe, then wiped /system dalvik, changed /data to f2fs, changed /cache so f2fs. I installed the AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v3_no-check.zip and today's opengapps open_gapps-arm-7.1-nano-20170317.zip

Initially I had a problem of the opengapps failed due to vendor differences say I was on a 6.0 rom, so another full /system wipe got rid of that.

I'm now still with one outstanding proble, opengapps appears to install correctly, but I do not have Play Store icon anywhere.

I'll keep experimenting, my try the resize and possibly try to pico gapps but if anyone has better ideas please help!
[Nexus 7 (2013) Android Development] crazyates:
I had the same issue when installing just yesterday. I think I wiped the system maybe 4 or 5 times before I got it to work?

I finally fixed it by wiping the system, flashing v3 of the ROM, newest Gapps, and then ElementalX. Boot into tablet, and Play store isn't there. Reboot back into recovery, flash just the Gapps (no wiping of anything), and reboot into ROM and it was there for me.
[Nexus 7 (2013) Android Development] nigelhealy:
I thought this odd, that when I did an adb shell and a df I saw /system nearly empty, so I'm figuring the f2fs implementation in the TWRP is buggy, so I closed /system then reoponed it after the ROM install then again after gapps install then again after supersu install, this would flush the writes.

Then it worked. It could have been coincidence.

But I'm installed now! Golly this is as fast as I remember it, I moved from Pure Nexus when it died to the AOSP but it died then to LineagOS which made my tablet really laggy, now back to this and the nippiness returns! Still life in the ole' device. Thanks to followmsi for the fresh AOSP build.

I'm /data and /cache f2fs, I know from this N7 on earlier ROMs that f2fs made a real difference on the older devices.
[Nexus 7 (2013) Android Development] followmsi:
I will put this on first page soon ..

If you wipe system the partition get automatically mounted afterwards.

Pls unmount the partition manually in TWRP mount menu before you start the installation of ROM, gapps and supersu.

It seems to help in some cases.

As you saw the ext4 /system partition .. you figured out a TWRP F2FS bug ?

Which one ? :)
[Nexus 7 (2013) Android Development] nigelhealy:
Trial & error and prior experience, yes judicious use of unmount /system seems needed in THIS TWRP version, but not all. Just in case I did it every step which sounds overkill. Yes put it in OP to save the next person an hour of random efforts.
[Nexus 7 (2013) Android Development] followmsi:
The manual unmount is required once only - just after system wipe.

Then you can install ROM, gapps and SuperSU in one go .. without another unmount of system.

The problem does not occur for all ROM users/installers ..

Anyway .. enjoy your Android N installation now :)
[Nexus 7 (2013) Android Development] ZakSeven:
For me to avoid the Gapps complaining of incorrection version 6.0, I wiped system/dalvik/cache, installed ROM alone, then when presented with wipe dalvik/cache or reboot, I back one step and flashed Gapps alone, then backed again to flash SuperSu. After all 3 installed rebooted and all was fine. Essentially instead of adding all zip at once for TWRP to flash together, which seem to lead to the wrong version, I get ROM done first which ensure when Gapps proceed all is in place and detect 7.1.

- Wipe

- Flash ROM,

- back to select what to flash, Flash Gapps (I used micro). No complaint about 6.0

- back to select what to flash, SuperSU (optional only if you want Root)

- Reboot

- All was fine

Zak
[Nexus 7 (2013) Android Development] crazyates:
This is how I always flash my zips, and I still had the problem.
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Hi, how I can install Quanta kernel at last AOSP build? I used it at the Nexus 4 with Fake Nexus - perfect, but I can't install it at the your Nexus 7 rom.
[Nexus 7 (2013) Android Development] followmsi:
What happens if you install the kernel ?

Which twrp version did you use to install ?

Also tested with last official TWRP version ?

On other AOSP ROM it works ?
[Nexus 7 (2013) Android Development] followmsi:
AOSP does not have a setupwizard .. 8.1 opengapps packages are not yet official.

Maybe the unofficial packages are not fully working on Oreo 8.1.

Which gapps did you use before ?

Yes .. will look into bluetooth !

If you install a new ROM you overwrite the boot.img - where most of the "root modifications" are done.

Just install Magisk after every ROM update .. if not done via restore script automatically.

Once Magisk (hide) installed you will be able to install Netflix via Playstore.

But latest Netflix version will give you error (5.2) when streaming content.

I was able to stream succesfully using old Netflix version 4.8.5.

Cheers
[Nexus 7 (2013) Android Development] logitechor:
I would say that with each new build it's easier to install and the tablet is running well on 8.1
[Nexus 7 (2013) Android Development] anthi01:
Hy, is there any other way to download? I've always problems with my google drive. It always show me an empty folder :(

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] :
[MENTION=5480152]followmsi[/MENTION] any update on signature spoofing? I really want to settle on this rom for good like on 8.0 but that's pretty much the only thing I'm waiting for.
[Nexus 7 (2013) Android Development] wavedashdoc:
[MENTION=5480152]followmsi[/MENTION] build 11 is running great. No longer having any touch screen issues. Very stable. Thank you?
[Nexus 7 (2013) Android Development] followmsi:
Pls use web browser to download from Google drive.

Just use browser instead of gdrive app.

Sorry .. the signature spoofing patch is not yet part of 8.1.

Will be part of next release.

Cheers
[Nexus 7 (2013) Android Development] rajsris:
Beta 11 is running great! The touch screen issues are gone, and sleep is much more battery efficient. SilentCamera works fine. Bluetooth won't pair to new devices, but this is a known bug.

However, this morning the rotation bug kicked in. It simply would not rotate to portrait from landscape mode even though auto rotate was on. I forgot to try to manually force it to portrait under display settings.

In addition, I'm not sure if night mode requires certain parts of gapps to be flashed, but it rarely respects the sunset to sunrise scheduling. Minor issue as it is very easy to turn on/off.
[Nexus 7 (2013) Android Development] followmsi:
HotFix release .. BETA-11.1

AOSP_8.1.0_r6_OPM1.171019.015_flo-ota-eng.followmsi_BETA-11.1.zip

AOSP_8.1.0_r6_OPM1.171019.015_deb-ota-eng.followmsi_BETA-11.1.zip

Changes:

- Fix Bluetooth pairing issue !

- Added "signature spoofing patch" - code from Android 8.0 - needs to be tested.

- Minor changes for framework/base.

Opengapps:

Fresh packages .. 20180103

https://drive.google.com/drive/folders/1IY1JrNDlkk7OjXutlX3zGeASfWpSsRdl

Sources:

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

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2018-01-04

Enjoy :p
[Nexus 7 (2013) Android Development] js89:
I have the same problems with autorotate, but recently USB also not staying connected. So I cleaned/reconnected the ribbon cable in tablet on both sides. And now everything works like brand new.:D:cool:

So might be hardware issue, since it's a known issue with n7.
[Nexus 7 (2013) Android Development] :
Seems like spoofing patch is working, at least that's what MicroG is telling me. Will see about actual notifications.
[Nexus 7 (2013) Android Development] rajsris:
Can you link some information on how to clean this ribbon cable?
[Nexus 7 (2013) Android Development] juyil:
Thank you so much for getting bluetooth fixed! One thing I'd just note for feedback purposes, battery level isn't showing anymore, but I'm fine with this as I can uses bluetooth again. :) Could just be a matter of the device I'm using not reporting that info.
[Nexus 7 (2013) Android Development] alirezaircn:
I followed exactly the instructions but after reboot, it's stuck in "android" logo....I tried clearing cache, data, dalvik and even factory reset but it ends up same situation. Any comments? (my N7 2013 is wifi only and I used "flo" files)
[Nexus 7 (2013) Android Development] Beachbum2049:
Thanks for the update!

Should we be flashing the kernel dated Dec-07-2017 as well?
[Nexus 7 (2013) Android Development] followmsi:
When I was testing the BT fix battery level was shown.

You may try to format data as ext4 .. and try again.

No .. fresh kernel is always part of the ROM !
[Nexus 7 (2013) Android Development] dealpapa1:
dear followmsi are you going to release a new version for twrp 3.2.0
[Nexus 7 (2013) Android Development] followmsi:
No need as official version is up-to-date ..

https://dl.twrp.me/flo/twrp-3.2.1-0-flo.img.html

https://dl.twrp.me/deb/twrp-3.2.1-0-deb.img.html

Cheers
[Nexus 7 (2013) Android Development] dealpapa1:
you should update your google drive :cowboy:
[Nexus 7 (2013) Android Development] kromo94:
hi [MENTION=5480152]followmsi[/MENTION] sry for the offtopic, can you have the rom you made for the emish x800 tv box? :D thanks :D
[Nexus 7 (2013) Android Development] alirezaircn:
I tried formatting with Ext4 and done but the result is same. I'm stuck in "android" while booting...:(
[Nexus 7 (2013) Android Development] jaibar:
Many thanks! It only gets better and better :)

On a side note, I think it could be easier to find the correct files in the google drive folder (where all the good stuff is :) ) if the filenames were written in a different order for example:

deb-BETA-11_AOSP_8.1.0_r6_OPM1.171019.015_-eng.followmsi.zip

(instead of "AOSP_8.1.0_r6_OPM1.171019.015_deb-ota-eng.followmsi_BETA-11.zip")

Then it will make much easier to pick the right zips, as the filenames are quite long (at least for N7 in portrait mode) it only shows the beginning of the filenames and differences such as "deb" / "flo" are hidden behind three dots

[OT] I have installed Xposed beta- didn't try many modules but those which I did, seem to work fine with BETA-11. I suppose with time more modules will get updated and work on 8.1. [/OT]
[Nexus 7 (2013) Android Development] jacopastorius:
Is double tap to wake and swipe to lock activated by default or do I have to install elementalx kernel? Thanx!!
[Nexus 7 (2013) Android Development] aquatix:
Same here... Wiped stock from my device by wiping system, cache and dalvik, and after a fashion also data. Then installed the flash, gapps pico and supersu 2.82-SR5. Still, it seems to be stuck on the 'Android' logo. I'll wait a bit longer :)

I first flashed TWRP 3.2.1 by the way, after that I did all the wiping and flashing.

---------- Post added at 04:35 PM ---------- Previous post was at 03:57 PM ----------

OK, not sure exactly what fixed it, but I did the following:

- flashed factory ROM to everything except userdata

- wiped everything again except Internal Storage

- adb sideloaded this ROM

- adb sideloaded gapps pico

- skipped SuperSU

And now it has booted fine and I'm doing the setup wizard. Actually, just succesfully finished it. Good stuff :)
[Nexus 7 (2013) Android Development] followmsi:
done :cowboy:

Tested clean install on 11.1 too .. no problems.

But I am using magisk 15.2 .. and my existing gapps installation - just did factory reset via TWRP.

Will need logs of the boot process .. adb logcat > log.txt

Yes, will adjust the name .. for the next release.

You need to enable via "Kernel Adiutor" or similar tools ..

I doubt the last EX kernel will boot at all .. too many changes were done for Oreo.

Like written above ..

Tested clean install on 11.1 too .. no problems.

Again - I am using magisk 15.2 and my existing gapps installation - just did factory reset via TWRP.

Normally SuperSU should work fine too.

Did you try older gapps package and/or Magisk as well ?

Will need logs of the boot process .. adb logcat > log.txt

Thanks