yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] adstraylight:
74hrs uptime and no reoccurrence of any problems with AR, this suggests to me that the January build is more tolerant of tablets with faulty sensor connections than the latest build. I noticed that there's a commit on gerrit to do with SE policy and the sensors, don't know if this will help for the next release. Maybe [MENTION=5424240]Clamor[/MENTION] can enlighten us.

FWIW, here's a current log with the sensors still working.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=2583740]adstraylight[/MENTION] Commit I pushed to flo repo has interesting history. I have AR issues from time to time as well (huh, and who doesn't) reboot helped, but on January build I faced AR failure where even few reboots with wipe of cache and dalvic didn't help. I desided to regenerate sensors config in persist, removed my current config and than I realised that selinux status doesn't allow to rewrite sensors configuration file in persist. That's why I made that commit. Else if somehow persist sensors config is corrupted ALL sensors will be lost till it is regenerated (which won't occure at all with selinux state before that commit). Although, it shouldn't affect anything in working device. Except that commit and security patches, no other changes were included.
[Nexus 7 (2013) Original Android Development] adstraylight:
Based on this, I've just reflashed the February build with the latest gapps, I'll report back if there's any problems with AR etc. Strange how me and the other user had the same failure last time, hopefully just coincidence ?
[Nexus 7 (2013) Original Android Development] Clamor:
Builds with March security patch are available on Unlegacy download site. Resize is now included in build so UA for flo/deb supports any /system size natively.
[Nexus 7 (2013) Original Android Development] memarama:
Does that mean that I could easily switch to Pie ROM after just flashing latest build?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=5859854]memarama[/MENTION] nah, it means that you don't need to resize /system after dirty flash before gapps, now they can be flashed in one queue.
[Nexus 7 (2013) Original Android Development] Ziyan:
Today's build (Jenkins finishes with it soon) includes Android 7.1.2 :)
[Nexus 7 (2013) Original Android Development] boom1982:
Friend, thanks for the support n7!

(I do not lose hope, that my little dream of the night mode will also come true someday :))
[Nexus 7 (2013) Original Android Development] Ziyan:
A build tagged as NIGHT has been uploaded (https://builds.unlegacy-android.org/aosp-7.1/flo/ua_flo-7.1.2-NIGHT-20170430120823.zip). Basically, this adds support for the AOSP Night Light feature (under Display settings), same stuff as on the Pixel devices :) it seems to work great for me, so if anyone's interested, try and report back how it works :) more details at https://xdaforums.com/showpost.php?p=72081288&postcount=25.
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=2633638]Ziyan[/MENTION]

Dreams Come True)

Night mode works fine :)
[Nexus 7 (2013) Original Android Development] dnle71:
I second this, it works! Great ROM! Btw, in case if you didn't know about this yet, when flashing the ROM and then gapps (opengapps), it returns invalid because I was using an android '6.0' version so I tried rebooting to recovery and flash it from there. Unfortunately, it reboots directly to system and only then I'm able to reboot back to recovery and flash the remaining zips I needed.

These issues might be from the ROM itself as this is the only ROM I've encountered the produces these issues.
[Nexus 7 (2013) Original Android Development] Ziyan:
Alright, thanks for the feedback; it is now merged into the main branch, and will be featured in tomorrow's nightly (along with the May security patches) :)
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=2633638]Ziyan[/MENTION]

Does the server have a habit of collecting useless updates?

Or is it already fixed?
[Nexus 7 (2013) Original Android Development] Ziyan:
Unfortunately, it's still a work in progress (but the progress can be monitored on our Gerrit/GitHub).
[Nexus 7 (2013) Original Android Development] daitalos:
you did nice work [MENTION=2633638]Ziyan[/MENTION]! (Like in omap4)..Light fast and stable Rom.,works very well on my device without problem until now...Thanks!
[Nexus 7 (2013) Original Android Development] nAFutro:
Sadly I couldn't test the Rom. The setup wizard stops working after I choose to set it up as a new device or copy data. Using ua_flo-7.1.2-20170613052020, came from stock and did a full wipe.
[Nexus 7 (2013) Original Android Development] sa33afq:
Same for me, someone have tried other build befor this last?
[Nexus 7 (2013) Original Android Development] Ziyan:
Sounds strange, does anyone have a log? It seems to be fine for me :confused:
[Nexus 7 (2013) Original Android Development] BLemelin:
Just here : ;)

08-09 00:37:17.093 3865 3865 E AndroidRuntime: FATAL EXCEPTION: main
08-09 00:37:17.093 3865 3865 E AndroidRuntime: Process: com.google.android.setupwizard, PID: 3865
08-09 00:37:17.093 3865 3865 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method setWifiEnabled(Z)Z in class Landroid/net/wifi/IWifiManager; or its super classes (declaration of 'android.net.wifi.IWifiManager' appears in /system/framework/framework.jar)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at com.google.android.setupwizard.BaseActivity.tryEnablingWifi(BaseActivity.java:629)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at com.google.android.setupwizard.network.BaseWifiActivity.init(BaseWifiActivity.java:54)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at com.google.android.setupwizard.network.NetworkActivity.onCreate(NetworkActivity.java:214)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6682)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2619)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2727)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1478)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6121)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
08-09 00:37:17.093 3865 3865 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
08-09 00:37:17.095 567 1824 W ActivityManager: Force finishing activity com.google.android.setupwizard/.network.NetworkActivity

EDIT : For people having this issue, a workaround you can do is :

1. Plug your device into your computer via USB.

2. Start a command prompt.

3. Type "adb shell" and press "Enter".

4. Type "su" and press "Enter". (We need super user privileges for next step).

5. Type "svc wifi enable" and press "Enter".

That should do it. :)
[Nexus 7 (2013) Original Android Development] montvid:
update kernel 3.4.113

Hi, thanks for your great work, the flo rom is really smooth! I wanted to ask you to update the kernel from 3.4.108 to 3.4.113 for more security. I opened a request on unlegacy-android too.
[Nexus 7 (2013) Original Android Development] Sage:
amazing work thank you.
[Nexus 7 (2013) Original Android Development] Hatshipuh:
Had same issue and that workaround worked, thanks!

Tap-a-talked from my OP3
[Nexus 7 (2013) Original Android Development] Clamor:
Hi there! As your update method is currently in development, may there be added function to flash additional packages directly after a system update in one session (for example gapps or kernel or any other zip) like it is realized in OpenDelta of OmniRom?
[Nexus 7 (2013) Original Android Development] Ziyan:
On my TODO list :) Omni seems to use the UA kernel, with a few minor things on top of it (like 3.4.113). I'll try merging it by the weekend.
[Nexus 7 (2013) Original Android Development] :
[MENTION=2633638]Ziyan[/MENTION] any plans on bringing oms support to UA Nougat? Or should we just wait for UA Oreo (if you're going to support that ofc)
[Nexus 7 (2013) Original Android Development] Ziyan:
We aren't really planning to, but I hear it's almost fully functional out of the box nowadays, especially on O (which we're going to support once things stabilize on the Nexus 4 on which we're testing it, which is almost a Nexus 7 2013).

Not sure if you noticed, but the last build came with 3.4.113 :)
[Nexus 7 (2013) Original Android Development] memarama:
That's what I already did - but I used gapps pico from 12/2018 and had no problem.
[Nexus 7 (2013) Original Android Development] teaguecl:
I'm wondering if anyone can advise me regarding the 8.1 ROM. I own a flo device and it's currently running 6.0.1 stock. I have loved my N7, but In the last few months it's been getting slow, unresponsive and just feeling old. Switching browser tabs is frustrating and even typing on the keyboard has been problematic occasionally. I am not a tinkerer, just a consumer. In the opinion of those who have tried both, is the consumer experience better stock or with UA? I don't care about running the "latest", nor do I care about all the great features/security enhancements that have been added to AOSP in the last few years. I'm really asking "will web browsing and youtube watching be better with UA than stock?". My past experience with ROMS (on other devices) has been that it generally improved some areas, created problems in others, and required a LOT of tinkering. I don't mind a complex one-time upgrade experience, but I am not interested in reading the forums everyday to keep up with the latest activity nor experimenting with side patches that might help with one issue or another. I've always ended up back on stock, because as I a mentioned - I don't want to tinker, I just want to use the device. Any advice from those more knowledgeable?

Edit: I have the 16GB model if that factors in
[Nexus 7 (2013) Original Android Development] daitalos:
edit: I have the 16GB model if that factors in[/QUOTE]

If you only want movies on youtube + browsing

stay in stock rom - especially in 16gb device ....this is my opinion

---------- Post added at 02:59 ---------- Previous post was at 02:52 ----------

I got the update 2215 (20190310) 8.1 in flo without problem

my device works very well....nice work guys

thanks!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=1998433]teaguecl[/MENTION] I'd advice you to try and check by yourself if this rom really suits you. If you find it not what you expected, stock can be flashed easily with TWRP.

From my personal experience, this ROM was made for stable usage, not for tinkering, and it is mostly "how would stock look if Google released one on N or O". There were time when I installed and used one build for a half of year without noticeable performance degradation.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Great news!

PS I wonder whether the bugs mentioned in #361 (Bluetooth address displayed improperly) and #365 (incorrect behavior of battery icon) have been ironed out.

---------- Post added at 12:38 PM ---------- Previous post was at 12:20 PM ----------

There're still some minor bugs (some people would even call them cosmetic glitches; I mentioned a couple of them above).

Talking about UX when browsing or watching YouTube, you'll get next to no improvements from UA itself.

Moreover, you won't be able to use the latest version of Netflix because there are no DRM blobs for Oreo and consequently no Widevine L1 support.

You might consider installing Kiwi Browser for better and ad-free browsing and YouTube Vanced plus NewPipe for better and ad-free YouTube experience.

(You can "share" 1080p60 videos that will otherwise be shown in 720p60 to NewPipe and then watch them in 1080p25/p30).

Add Customized Pixel Launcher for useful UI goodies from both Nougat and Oreo—and you will be pleasantly surprised at what the stock ROM is still capable of.

However, once the remaining bugs are ironed out, I'll be switching to UA because of the recent security updates and improved audio libraries avalable in Oreo builds.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] they were not ignored, I have no access to my PC and unlimited internet connection, that is why I can't work at this bugs; that is why I can't test Pie closely.
[Nexus 7 (2013) Original Android Development] Clamor:
Mostly working.
[Nexus 7 (2013) Original Android Development] kmygmky:
I look forward to it very much.
[Nexus 7 (2013) Original Android Development] frankusb:
This ROM is so stable on 8, everything just works perfectly. I look forward to 9.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Does it mean that there will be no more Oreo builds of UA?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] I didn't say that) moreover, bt mac address issue on Oreo was fixed, and this fix will be in April build. Charging indication is bit more complicated, but it actually occured only in settings in battery menu. Besides that place I have never seen it.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Well then charging indication is not an issue for me. If April build proves to be stable then it's switchover time :)
[Nexus 7 (2013) Original Android Development] abhifx:
Nice! I can see there are lots of patches still pending to be merged and Selinux seems permissive as of now. But cant wait to get oreo based in Unlegacy as it seems most stable (based on oreo experience)
[Nexus 7 (2013) Original Android Development] Clamor:
PIE

Unlegacy Users! Me and [MENTION=2633638]Ziyan[/MENTION], decided to show you a bit of our work. We are proud to present fully functional PIE builds for FLO and DEB!

Currently works everything I was able to test (including NFC and kernel in enforcing mode). Any feedback would be appreciated.

Additionally, you have to repartition your device, and have AT LEAST 1 GB of /system.

Builds with May security patch.

Downloads:

FLO

DEB

P. S. Google quietly abandones tablet support by making UI look ugly on big screens and non-notched phones. Well, we have what we have. Removing this cosmetic will require additional efforts, and take more time.
[Nexus 7 (2013) Original Android Development] JT1510365:
Amazing will test asap thank you so much but why is this build experimental?
[Nexus 7 (2013) Original Android Development] archish:
[MENTION=5424240]Clamor[/MENTION]

Pie is so far working well on my flo. Noticed small issue with the additional icons.

Thanks for the great work!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4577365]archish[/MENTION] that is part of UI issues I mentioned. Thanks Google!
[Nexus 7 (2013) Original Android Development] archish:
Why do you say UI is ugly on tablet? Apart from app switcher the UI feels same as Oreo. Personally I do find UI smoother on Pie than Oreo.

Is dark mode broken for you as well? The ROM feels almost perfect!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4577365]archish[/MENTION] apart from rotation/ime button between main navi bar, I find ugly next things:

- when pull down notification panel there is HUGE space on top, it is ridiculous to leave this enormous gap on normal phones and especially on tablets.

- notification/quick access panel has roughly cropped shadow, which shows that UI isn't made to use on tablet.

- card view of resents looks silly, even more, it is dumm waste of space on tablet, instead of those giant cards/previews would be better to use same layout as MIUI has - list of cards (like notes is Keep app).

- also there was problem with quick access toggles, but I used an overlay hack to fix it temporary.

I attached screenshots to show what I mean.

P. S. This are not Unlegacy issues but general issues of Pie on ALL TABLETS!
[Nexus 7 (2013) Original Android Development] JT1510365:
just change dpi to 480 instead of 320 in build.prop in system folder and this fixes all the issues for all pie roms including ua pie except for one issue which is dark mode in the rom because that has to be fixed later on by the OP:)

Many thanks your hard work and thank you for still supporting this device you guys are awesome:)
[Nexus 7 (2013) Original Android Development] archish:
[MENTION=5424240]Clamor[/MENTION]

Can you please add lower display brightness curve on pie build. The current minimum feels very bright.
[Nexus 7 (2013) Original Android Development] abhifx:
Tested the new Pie ROM and everything is great including battery life. could not check if wireless display is working or not. can anyone confirm?
[Nexus 7 (2013) Original Android Development] frankusb:
I'm confused, I cannot recreate these issues. Did you update the build? Everything looks great in the 5 minutes I've been using it.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4577365]archish[/MENTION] might be due to Google experiments with automatic brightness adjust, brightness levels didn't change and if we change them for Pie, Oreo will have same change (decrease).

[MENTION=3771488]frankusb[/MENTION] stuff I wrote was only my opinion, if described isn't problem/can't be repurposed, than this build is fully functional (and bugfree I hope, since no bug reports were till now). Have good user experience!)
[Nexus 7 (2013) Original Android Development] archish:
[MENTION=5424240]Clamor[/MENTION]

Is the adaptive brightness working? It doesn't seem to learn from my preferences. On my other pie devices after few days of adjusting it learns and works very well.
[Nexus 7 (2013) Original Android Development] frankusb:
I am having a great user experience, thank you and all who contributed. The only oddness I have seen is when I got home last night the tablet was completely powered off with 100% battery and I did not power it off. Once I powered it on, I used it for a while and it was great. This morning it was as I left it and slept nicely.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4577365]archish[/MENTION] it is, I checked on my flo, brightness changed in different light levels (dark room, indirect led light, outdoors at cloudy and sunny weather), moreover, it worked way better than on my N5 (which looks like has too sensitive sensor).

Check if all your sensors work correctly with test app.
[Nexus 7 (2013) Original Android Development] archish:
[MENTION=5424240]Clamor[/MENTION]

I was referring to personalization of brightness control detail in this blog: https://android-developers.googleblog.com/2018/11/getting-screen-brightness-right-for.html?m=1:

Anyway I will wait for few more days to see if it makes any difference.

BTW Pie is unbelievably smooth compared to Oreo. For whatever reason the webpages seem to also render faster in pie. Thanks again!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=5653319]JT1510365[/MENTION] using 480 dpi transforms my 7" tablet into giant phone. Bad idea IMHO
[Nexus 7 (2013) Original Android Development] JT1510365:
i love it in my honest opinion
[Nexus 7 (2013) Original Android Development] adstraylight:
Any chance of a screenshot? I'm holding back at the moment as Oreo looks great and works very well for me...

I mean, I know what pie looks like as I use it on my n4, I'm just curious as to what the dpi mod looks like on the n7.
[Nexus 7 (2013) Original Android Development] archish:
There is no visual size difference between Oreo n pie build. All looks same.
[Nexus 7 (2013) Original Android Development] EoloTheWindKing:
Hello, can a developer trigger a new Nougat build for flo (for the new security patches)?
[Nexus 7 (2013) Original Android Development] JT1510365:
Sure I am on aosp extended pie right now so it will look pretty much the same as stock aosp Oreo and pie but here are some screenshots
[Nexus 7 (2013) Original Android Development] sir_bazz:
Will give this a try.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4819463]EoloTheWindKing[/MENTION] I can trigger, but Google abandoned patches for N, only unofficial backports might be merged, but I'm not sure they are.

P. S. Today will be available Oreo builds with April security patches
[Nexus 7 (2013) Original Android Development] m00nlighter:
That's great news, thank you very much! Is the Bluetooth MAC display fix included in the March build for Oreo?

And one more question: what's the Widevine level for the Pie builds? Same as for Oreo an Nougat?
[Nexus 7 (2013) Original Android Development] sir_bazz:
Is there a secret trick for downloading ROMs from Jenkins.

I can't get more than about 10% of the way through the download before it suddenly terminates.
[Nexus 7 (2013) Original Android Development] Android-Andi:
N has March backports merged, but there's a few bt patches missing which didn't applied clean. Google pushed new 7.0.0 and 7.1.1 sources which might help getting the missing patches in.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] it is, as I wrote before) Widevine level is 3, same as on N and O. We won't get higher.

P. S. I made a mistake, Oreo builds have April patches, not March.
[Nexus 7 (2013) Original Android Development] brewer75:
Great Battery life for Android Pie

I have been using another Pie build for a bit and I liked it but the battery life was terrible and it seemed like it never went into deep sleep. This build is working great and the battery life is phenomenal. Thanks for the build and I look forward to more builds and security updates!
[Nexus 7 (2013) Original Android Development] abhifx:
Feels like same stability as oreo ulegacy build, in fact it seems more smother. Same great battery life. Plus the only pie rom where NFC is working.

Although haven't had time to fully test the build though.
[Nexus 7 (2013) Original Android Development] daitalos:
thanks for support N7 flo guys...I got the update 4/4 in 8.1 without problem...

my device works very fine ..Nice work!

:good:
[Nexus 7 (2013) Original Android Development] m00nlighter:
Well you cannot have your Pie and eat it :)

Wish there was a way to backport those security patches to stock 6.0.1.
[Nexus 7 (2013) Original Android Development] noam212:
Great work and kudos to all the developers.

This is unbelievable to see Pie rom on such old device.

Before I start the hole process of flashing custom recovery, rom and karnel can you tell me if the new Netflix version works on the latest pie build? If not, can you recommend a custom rom that does (even nougat rom)?

I bought it for my flights and the Netflix download option is really important for me.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=7983020]noam212[/MENTION] you need old or modified Netflix app, original won't work on ANY ROM higher than M.
[Nexus 7 (2013) Original Android Development] daitalos:
try this version : https://androidfilehost.com/?fid=529152257862715472

works for aosp 8.1 but IDK for 9...Just try
[Nexus 7 (2013) Original Android Development] olliebean:
That version doesn't have the download option, though.
[Nexus 7 (2013) Original Android Development] frankusb:
I had a spontaneous reboot over the weekend. The UI froze and then after a bit, it rebooted. This never happened on Oreo on this hardware. Other than that, Pie has been great!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=3771488]frankusb[/MENTION] if you, or anyone else, will get something like this, pull last_kmsg and we will be able to fix it or at least figure out why it happened.
[Nexus 7 (2013) Original Android Development] frankusb:
I have not rebooted since so I believe this should be valid.