yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] cnsultnt:
Thanks for the suggestions, all. I'm trying the latest 8.1, and run SD Maid Pro. I thought fstrim is no longer needed, although I did run it a while ago. I'll run it again, can't hurt (I hope).

I'll give it a week to settle in. Biggest lag seems to be opening GBoard, sometimes system UI is slow.

Next try will be UA 7.1.2 (can I sorry flash a downgrade), if required.

And a big thanks to the devs who keep this going.
[Nexus 7 (2013) Original Android Development] tye_time:
I came from lineage 14.1 and I'm impressed with this ROM so far... Devs did a great job on ancient hardware!
[Nexus 7 (2013) Original Android Development] Clamor:
Oreo builds with December security patch are already available. There might be one more Nougat build with December patch, but since Google dropped support of security updates on N we highly recomend to use Oreo builds.

From next year we will drop Nougat updates for flo/deb, but November and December N builds would be still available for download. We will focus on maintaining Oreo and bringup of Pie.
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Can't see 9.0 in the builds link. Are they somewhere else?
[Nexus 7 (2013) Original Android Development] shuvabrata:
Am using Lineage 15.1 on my Flo right now. I am planning to move here. Do I need to clean flash? Or I can just dirty flash the latest build?

Let me know.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4831195]buffal0b1ll[/MENTION] no Pie builds yet, but there will be.

[MENTION=3440205]shuvabrata[/MENTION] ONLY CLEAN INSTALL! Factory reset or ideally /data + /cache format
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Sorry. I misread. It clearly says Oreo December. I only paid attention to December and thought pie. Thanks.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Oreo version users, please be kind to check if Russian (Русский) is in the list of languages supported by this ROM. A screenshot proof would be perfect.

Many thanks in advance!
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] all languages that are supported by AOSP are as well supported by Unlegacy Project (since it is based on AOSP). Including Russian.
[Nexus 7 (2013) Original Android Development] Marcus Llewellyn:
Hey! I've been very happy with Unlegacy and I would like to thank the members of the project.

I searched the forum, and saw that a dirty flash is the expected method for updating. What I'm not sure about is whether gapps will be preserved.

Thanks for the help!
[Nexus 7 (2013) Original Android Development] m00nlighter:
[MENTION=5424240]Clamor[/MENTION], [MENTION=5047191]cnsultnt[/MENTION], many thanks!

Unlegacy seems to be the best choice for migrating from the stock ROM because it's not bloated and everything is working—including NFC.

I have two more questions though

1. Does anyone use the latest ElementalX kernel (7.00) with the Oreo (8.1) version of this ROM? If you do, please share your experiences and feedback.

I'd really like to keep the overclocks I have now (CPU OC'd to 1.7 GHz and GPU to 450 MHz) and it looks to me that it's not possible with the vanilla kernel for this ROM.

2. Does the 1080p60 mode work for YouTube (or YouTube Vanced) in the Unlegacy ROM?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] try to use kernel that goes with rom. I never experienced any problems connected with lack of performance (CPU/GPU clock speed). Moreover, overclocking usually leads to overheat, excessive battery drain and general system instability.

Unfortunately, 1080p60 and 720p60 are glitchy right now (simple 1080p and 720p are perfectly fine). We might look into this later since this isn't a major bug (other Oreo roms have 1080p60 playback problems as I know).
[Nexus 7 (2013) Original Android Development] m00nlighter:
> I never experienced any problems connected with lack of performance (CPU/GPU clock speed).

For playback of 1080p60 videos in YouTube Vanced using the VP9 codec, the stock CPU/GPU speeds are just not enough. However with a modest overclock, most of 1080p60 content can be played with almost no frame drops.

>Unfortunately, 1080p60 and 720p60 are glitchy right now (simple 1080p and 720p are perfectly fine). We might look into this >later since this isn't a major bug

It's actually not a ROM bug. It's an issue with poor optimization for VP8/VP9 codecs in Adreno drivers. MX Player is able to play most 1080p60 video files just fine when its proprietary HW+ codec is used, so the hardware is perfectly capable of playing 1080p60 content but the software lacks necessary optimizations.
[Nexus 7 (2013) Original Android Development] VictorLapin:
I'm using EleX overclocked to 1620MHz, and everything is nice and smooth. No issues with battery life either.
[Nexus 7 (2013) Original Android Development] joep2k:
Thanks for the awesome ROM.

Brought my Nexus back to life.

---------- Post added at 09:06 AM ---------- Previous post was at 09:01 AM ----------

I did notice Netflix has an issue.

It either didn't play back anything, or I get error 5.7.

Anyone else have this issue. I'm using the 8.1 ROM
[Nexus 7 (2013) Original Android Development] maj_o:
[MENTION=279777]m00nlighter[/MENTION]: yes. 1980 MHz, undervolt 750, and GPU 570 - no issues, everything smooth like on devices from 2018.

Great ROM! Stable Kernel!
[Nexus 7 (2013) Original Android Development] Phanty:
Hi, I came from PureNexus ROM, wiped data, cache, dalvik and NFC isn't working for me on this ROM (latest December build). I tried installing Magisk and even ElementalX (did not work on stock kernel). Was there anything special you needed to do to get NFC working?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=4542831]joep2k[/MENTION] this issue is connected with drm. On all ROMs (not only Unlegacy) Nougat and higher this problem persists. We can reach DRM level 3 which is not enough for apps that work with drm protected content (like Netflix). Such apps require DRM level 1 for proper work. To prevent next questions, our drm-connected blobs won't work on N+ android version since they are designed for M and we can't use any other drm blobs that provide high level (1) since they are hardware specific.

[MENTION=5267561]Phanty[/MENTION] it just works, I personally tested by transferring files between my flo and hammerhead.
[Nexus 7 (2013) Original Android Development] joep2k:
Thanks for the quick response!
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Sideload this old unsigned Netflix apk. It won't allow downloads like newer versions, but it will work for wifi streaming on L3 DRM

https://androidfilehost.com/?fid=529152257862715472
[Nexus 7 (2013) Original Android Development] Phanty:
Interesting... Is there any sort of log I can provide to help troubleshoot this issue? I'm not really sure where to begin troubleshooting otherwise. Should I return to stock firmware before flashing? I haven't used NFC in the past but I'm looking to repurpose my tablet with this ROM and require NFC only now, so I am unsure as to when NFC stopped working for me. Everything else appears to be working.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Now this is what I'd call a good overclock :)

BTW how did you test your overclock for stability?
[Nexus 7 (2013) Original Android Development] LucentBirch:
Anyone having issues with their screen not turning on and having to restart their tablet after not using it for a couple of hours?
[Nexus 7 (2013) Original Android Development] TechnicsKuzya:
Have a problem at the 8.1.0 build with Unlegacy and Classic (followmsi) ROM. Details here.
[Nexus 7 (2013) Original Android Development] abhifx:
Hi [MENTION=5424240]Clamor[/MENTION] & [MENTION=2633638]Ziyan[/MENTION]

As seen the AOSP Classic thread, there seems to be a device similar to our called "Duma" (Asus Memopad 10) and has working android pie.

May the same could be of help for bringing up pie it has the similar hardware as flo.

Kernel Sources: https://github.com/yatto/ElementalX-Kernel-for-ME302KL/tree/ElementalX7-P

Vendor Tree: https://github.com/yatto/android_vendor_asus_duma/tree/lineage-16

Device Tree: https://github.com/yatto/android_device_duma/tree/lineage-16
[Nexus 7 (2013) Original Android Development] jaucar:
I have a problem with this rom. It's with the Netflix application. The application is installed well, the first reproduction, is carried out without problems, now, when leaving, re-enter, and replay, an error message is produced and it is impossible to reproduce again being necessary to reinstall the application
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Search "Netflix" in this thread.
[Nexus 7 (2013) Original Android Development] sir_bazz:
Just found this now after looking for alternatives to LOS.

Couldn't install the recommended micro gapps but Pico was fine.

Very nice work guys.
[Nexus 7 (2013) Original Android Development] .kaputnik.:
System partition too small? Ran into the same problem when moving to this rom. Also ended up installing the pico package instead, but if you need/want the additional apps in mini, you can always repartition the device.
[Nexus 7 (2013) Original Android Development] sir_bazz:
Thanks for the reply.

Yeah it was the partition size issue but really just happy that Pico installed without having to go down the resizing path.

Surprised how well Oreo runs on flo......it actually feels pretty smooth so will probably extend this devices life for one more year. Hah!

And I haven't even looked at the kernel yet for tuneables.

Next on the list will be a deb that's still chugging along with the now abandoned LOS 14.1, but feels a bit long in the tooth.

Might try the modded TWRP you linked when the time comes for that job.

Cheers.
[Nexus 7 (2013) Original Android Development] .kaputnik.:
Yeah, happy with the pico package too. The N7 is something of a secondary device nowadays, play store is really the only gapp I can't manage without.

Also, seems like repartitioning adds slight complications if you clean flash roms later. Better to just leave the partitioning as is if you can do without it.

Yeah, also surprised of how well it works. Using the default kernel aswell. Haven't found a worthy successor to the N7 yet, very happy to be able to extend its life a little bit further :)
[Nexus 7 (2013) Original Android Development] HollyFredD:
I have the same issue (code 5.7) with Netflix... such a pity, everything else runs smoothly !

Anymore having this issue ? did you find a way to make it work ?
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Search this thread for 'Netflix' maybe?
[Nexus 7 (2013) Original Android Development] HollyFredD:
Already did. Did I miss something?.. recheck.

Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
https://xdaforums.com/nexus-7-2013/...nlegacy-android-project-t3578301/post78474215
[Nexus 7 (2013) Original Android Development] HollyFredD:
Of course I missed it.

Perfect solution ! Thank you

Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] daitalos:
I tested last build 8.1 - flo again after some time...It is very light rom,works stable & fast without problems for me until now

very good rom for this old device...nice job!

Thanks
[Nexus 7 (2013) Original Android Development] frankusb:
Thanks for the new build, ua_flo-8.1.0-20190119-1207.zip. This ROM is working great for me, super smooth and stable.
[Nexus 7 (2013) Original Android Development] Somname:
Hi!

Just found out about this ROM. But since I didn't hear anything about it until now, I'm a little unsure to flash it.

I looked into the official site and I can only find the builds. Anything else is old. Code seems pretty much updated.

Anyone can help me arguing in favor of its reliability/trust?

Thank you :fingers-crossed:
[Nexus 7 (2013) Original Android Development] abhifx:
Pretty stable rom and i guess its one of the fully functional rom.

Only down side I can think of is that external kernels could not be flashed.
[Nexus 7 (2013) Original Android Development] VictorLapin:
ElementalX is just fine here :confused:
[Nexus 7 (2013) Original Android Development] abhifx:
wasn't working before... hmmm i am surprised if everything is working?
[Nexus 7 (2013) Original Android Development] VictorLapin:
Slightly overclocked, working good
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Me too. EX working well. I like it for dt2w (which can be disabled when close magnetic cover to stop battery dt2w drain).
[Nexus 7 (2013) Original Android Development] sgtguthrie:
Hello. I just installed this on my Nexus 7, and the rom installs fine, but I get an error during installation saying the gapps are incompatible with the rom. I've now tried the 7.1 micro and 8.1 micro gapps linked to in the second post. Anyone have a link to gapps that work? Thanks in advance!
[Nexus 7 (2013) Original Android Development] adstraylight:
This error can happen if the /system partition is already mounted when you try to flash the Gapps package.

What I do to avoid this:

1 wipe the /system etc via the advanced wipe section, if its the first time with a new ROM, I wipe everything except internal storage.

2 in TWRP's mount section, I uncheck the /system partition.

3 Flash the ROM, make sure /system is still unchecked in mount, then flash the Gapps.

Hope this helps.
[Nexus 7 (2013) Original Android Development] sgtguthrie:
Thanks, I'll definitely try this. I've flashed a ton of roms, but not so many lately. I've never had to mess with mounting and unmounting to flash roms. I however don't believe I've ever flashed a device this old before either. Much appreciated friend...

---------- Post added at 06:28 PM ---------- Previous post was at 05:45 PM ----------

No. The log says both the 7.1 and 8.1 gapps aren't compatible with the rom, and it won't install them. ??*♂️
[Nexus 7 (2013) Original Android Development] sir_bazz:
Obvious question but are you downloading the gapps package for ARM ?
[Nexus 7 (2013) Original Android Development] eichenbast:
Thank u for that rom !! It is amazing how fast everything is working now on my nexus 7 lte (deb). Had also no problems with installing the gapps (pico). To be honest: it was really slow with lineage. Thanks !!!
[Nexus 7 (2013) Original Android Development] jaidoe:
I'm giving the ROM another try and I'm facing the same issue I had last summer. The device wont enter deep sleep. I'm using the latest 8.1 from 19th Jan, and have almost no apps installed. Wiped everything, etc, left the tablet on (even in flight mode I must say) over night and almost 25% of the battery has been draining. Any tips!? I had no sleep problems with other roms.
[Nexus 7 (2013) Original Android Development] frankusb:
Can you check wake locks?

Maybe something in the logcat would show the problem?

I'm sitting at 89% deep sleep.
[Nexus 7 (2013) Original Android Development] m00nlighter:
Guys,

Are there any plans to update the Oreo build with the February security patch? Note I'm not asking for the exact ETA date— but it would be really great to know if a new build is released this month.

And BTW— how are the things going with the Pie builds?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] previously I wrote that builds with security patches will be publised till approx. 10th day EVERY (!) month. N support is dropped but builds are available as well as sources. Pie builds will come soon.
[Nexus 7 (2013) Original Android Development] daitalos:
post delete
[Nexus 7 (2013) Original Android Development] Clamor:
Builds with February security patch are delayed due to problems it brings.

[MENTION=5976373]daitalos[/MENTION] provide logs (logcat and dmesg) so we could debug this problem. Ziyan and me have no problems with bt.
[Nexus 7 (2013) Original Android Development] m00nlighter:
While working on the February build, can you check whether these "developer preview" user mode binaries are any good with Oreo—of course if you haven't done that before?

https://developer.qualcomm.com/software/adreno-gpu-sdk/tools

(see the "Driver" section at the end of the page).

PS I'm aware of the workaround solution for Netflix available here:

https://xdaforums.com/showpost.php?p=78474215&postcount=313

but this is merely a workaround for a single DRM dependent app only...
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=279777]m00nlighter[/MENTION] that pack represents only graphic blobs from qcom, drm blobs are provided by device vendor and are device and OS version specific.

P.S. those blobs are buggy for builds, I tried them and they caused soft reboots
[Nexus 7 (2013) Original Android Development] bamtan2:
just installed the latest version and this weird hidden ssid bug still happens :silly:
[Nexus 7 (2013) Original Android Development] Clamor:
Builds with February security patch are already available.

[MENTION=4545566]bamtan2[/MENTION] take logcat and dmesg when this occures.
[Nexus 7 (2013) Original Android Development] Uchihi:
Those of you that have used this rom for a while, is there any issues? Battery life? Lag? Thanks
[Nexus 7 (2013) Original Android Development] adstraylight:
All great here, (8.1/flo), I've been using this ROM and updating with each iteration for months now.

You can see by the lack of issues brought up in this thread that it must be working well for most people.
[Nexus 7 (2013) Original Android Development] HollyFredD:
The only issue I see is about GPS. The initial fix is very long and the overall precision is not very good.

Anyone shares that issue? (Flo)

Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] daitalos:
*_Yes you are right! No problem with Bluetooth

(I deleted the post above)

I flashed Rom from the beginning (clean) + mob30x before, because I was coming from another Rom + custom kernel (my fault)

all works fine now

:good:
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=503322]HollyFredD[/MENTION] try to reinstall rom with clean install (including format of internal storage). GPS should work same as on N and M. I had to test it a lot when we bringed up O.
[Nexus 7 (2013) Original Android Development] m00nlighter:
[MENTION=5424240]Clamor[/MENTION], I wonder how things are with 720p60 support for YouTube. Still glitchy?

PS I checked the datasheet for our SoC and it is clearly stated there that hardware acceleration for 1080p60 /H.265/VP9 is not supported. So It's not a drvier issue—it's just the outdated hardware.
[Nexus 7 (2013) Original Android Development] HollyFredD:
This is the way I installed the ROM. On a cleaned (including internal storage) ... Weird.

Maybe an hardware issue?

Am I the only one ?

Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] daitalos:
Really nice work guys...build 17/2 works fine on my device

no problem anymore :)
[Nexus 7 (2013) Original Android Development] braveheartleo:
Here's a (cosmetic?) issue that I found so far:

I'm using ua_flo-8.1.0-20190217-2122.zip and noticed that the bluetooth address does not show properly. See the attached screenshot.

However, getprop shows the proper address

[persist.service.bdroid.bdaddr]: [D8:50:E6:xx:xx:xx]

Does anybody else noticed their bluetooth address not showing properly? Bluetooth turns on and works just fine despite this.
[Nexus 7 (2013) Original Android Development] Tmzdroid:
Could somebody post a decent video showing this rom in use please? A quick demo of some games and browsing mixed with a bit of YouTube would be helpful thanks.
[Nexus 7 (2013) Original Android Development] eichenbast:
Update

Hi; using now the Feb-build. It was not possible to update from january-build to the latest. Had to download the feb.-build and flash it.

Is it a bug? ua_deb-8.1.0-20190217-1902.zip : no problems, still runs like a shot. Thank u for that rom.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=9244976]braveheartleo[/MENTION] huh, interesting, I have same bug) never noticed it before since bt worked as intended. Cosmetic problem I suppose.

[MENTION=9504344]eichenbast[/MENTION] if you mean OTA updates, Unlegacy ROMs don't support them (at least yet). You have to download new build from our download site and dirty flash manually over your current build (with gapps and other packages that were flashed before, since like AOSP Unlegacy ROMs don't support init.d scripts).
[Nexus 7 (2013) Original Android Development] braveheartleo:
Notice also how the battery status indicate Plugged in, can't charge right now, but the tab isn't really plugged in? Another cosmetic issue I guess.

EDIT: I just confirmed from another Bluetooth device that it sees the tab's address as indeed the one indicated in the status page.
[Nexus 7 (2013) Original Android Development] gorunks84:
OTA Update

[MENTION=2633638]Ziyan[/MENTION]

flashed a couple of weeks ago on my Nexus 7 2013 Deb, oreo.

Amazing!!! it works really well. I installed micro gapps and then just the pixel launcher from aroma gapps

Now I am going to flash on another devices, Flo.

Just one question. About OTA Update? how does it work? I saw an update on the web site, checked with my nexus 7 but it seems not working.

do I have to flash it mannualy via Twrp?

Thanks
[Nexus 7 (2013) Original Android Development] abhifx:
No OTA. Flash manually.
[Nexus 7 (2013) Original Android Development] gorunks84:
Ok, thanks a lot.

[MENTION=2633638]Ziyan[/MENTION]

I just noticed an issue with screen autorotation.

in both devices the screen never rotates.

I think that could be a bug.

Is there anyone facing the same problem?

Thanks
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Take a look at these links

https://xdaforums.com/nexus-7-2013/development/rom-pure-nexus-substratum-t3576447/post73074511

[youtube]LLCAeBe2hVU[/youtube]
[Nexus 7 (2013) Original Android Development] m00nlighter:
[MENTION=5424240]Clamor[/MENTION] can you please check if this cosmetic bug is easy to fix when working on the March build?

The thing is that I use a wireless charger quite often (that's why I still keep my good old deb—there are NO modern tablets with Qi wireless charging + FullHD screen).

And I'd really like to be sure whether the tablet is charging or not when using a wireless charger.

The stock ROM shows charging status correctly.
[Nexus 7 (2013) Original Android Development] abhifx:
Autorotation issue can sometime be hardware issue which is very common in nexus 7 2013. Check youtube on how to fix it.
[Nexus 7 (2013) Original Android Development] adstraylight:
Possibly, I have the hardware issue that causes AR to break, but whilst running the previous build I fixed it via the means of bits of tape and cardboard. Since running this latest build of 8.1, it has broken altogether so that not even a reboot would restore it. I've just rolled back to the 01/19 build and it's working again.

I need to run it for a few days to confirm that the build is the most likely issue, but I've attached a log from when it was broken on the latest build that is filtered to the keyword "Sensors"..
[Nexus 7 (2013) Original Android Development] hegyre:
Hello guys,

I'd like to install 7.1.2 over the official latest stock 6.0.1.

Some few questions:

1. I'll use TWRP 3.2.3. Is that fine for this android version 7.1.2 ?

2. Before flashing, should I repartition first using the Non-destructive repartition script ?

3. I saw we should wipe some partitions, including formating /data (seen on this wiki page). What if I do not wipe /data (because I really do not want to re-install and re-configure all my apps and games) ? Will it works anyway ?

Thanks in advance.
[Nexus 7 (2013) Original Android Development] daitalos:
1: yes

2: No...no need

3: format data can help you decrypt etc (if you want)... It is different to wipe data from format data

it just needs a clean installation

for apps you will choose a package gapps(Read post#2)

---------- Post added at 13:48 ---------- Previous post was at 13:24 ----------

No...I do not have auto rotation problem on / flo aosp 8.1 latest build 0217

all works fine