yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] OhioYJ:
On FLO, everything seems to be working fine. Clean install though, using the SU addon (not sure if that makes a difference or not). The setup assistant ran through just fine. (3-14 Build)

Have you tried a different kernel? I'm using the ElementalX kernel, but so far using the 3-14 build (just finally updated to Lineage from CM13) I think it's fine. I disable a lot of background, and startup stuff too, perhaps that helps. If anything this maybe a bit snappier for me.
[Nexus 7 (2013) Original Android Development] Bingley:
I've not, but I don't see why it should be so slow compared to stock 6.0.

I don't know how to test real world usage ie this game Dominations and compare if you've not used it before, but I can't see a kernel suddenly unburdening the cpu of a ton of graphical work onto the gpu :/
[Nexus 7 (2013) Original Android Development] OhioYJ:
The kernel controls everything about how the memory is used, how the GPU is used, how the CPU is used, when it ramps up, how quickly it ramps up, controls everything regarding performance. It completely controls performance and battery life. However I've tweaked both Lineage, and the ElementalX settings to the way I want.

I've never played the Dominations game. I did download it, and tried it. It doesn't lag for me. That being said I'm just starting out, so it's not like I have a huge amount crap on the screen either. To be a semi fair comparison, I grabbed a second Nexus 7 (I have 3 Flo's in the house) but this one running CM13 and tried it. If anything I would say it lagged more in CM13. The third one is also CM13, I don't have any running stock software.
[Nexus 7 (2013) Original Android Development] Bingley:
Great info, thanks. I suspected it was the kernel, and switched to https://xdaforums.com/nexus-7-2013/development/rom-resurrection-remix-v5-8-0-t3507680 this rom and it works great on it, generally much quicker and lag-free, too. I may try ElementalX kernel after I get this set up.

Thanks so much for testing on a few devices!
[Nexus 7 (2013) Original Android Development] Bingley:
Edit: received everything and started afresh with this week's build and all is great on Lineage OS :) Awaiting first update to see how it goes.
[Nexus 7 (2013) Original Android Development] Bingley:
I found a delta updater (ie only changes, not whole rom) for Lineage OS - posted over at https://xdaforums.com/lineage/help/delta-updater-lineage-os-t3576689 - works fine for me. You'll need to add root app to be flashed after to re-root, but this can be auto done.
[Nexus 7 (2013) Original Android Development] OhioYJ:
[MENTION=3453224]Bingley[/MENTION] nice find. I still prefer clean flashes, I seem to avoid any problems that way. I wish [MENTION=4598799]hazzer[/MENTION] would at the links to the SU add-ons to the OP. Maybe it did get posted somewhere? (I found them from the 5X thread, and looking in that directory)

All devices here:

https://lineageos.mirrorhub.io/su/

Flo Lineage SU add-on here:

https://lineageos.mirrorhub.io/su/addonsu-arm-signed.zip

Remove SU from Lineage Flo Zip here:

https://lineageos.mirrorhub.io/su/addonsu-remove-arm-signed.zip
[Nexus 7 (2013) Original Android Development] harryyoud:
Since your device is now officially supported, please move your comments to the official nightly thread.

Deleting this thread. PM me if you need anything from me
[Nexus 7 (2013) Original Android Development] OhioYJ:
Since that thread specifically says LTE, and is in the DEB section, I think it's easy to see why people end up over here. There almost needs to be a thread in the FLO section as well, just for people to ask questions, or offer advice, in my opinion.
[Nexus 7 (2013) Original Android Development] butterbeanmash:
https://xdaforums.com/nexus-7-2013/orig-development/official-cyanogenmod-14-1-nightlies-flo-t3502494
[Nexus 7 (2013) Original Android Development] pijetri:
Security updates

[MENTION=4598799]hazzer[/MENTION]

Is this rom updated with security updates?

or can someone else tell me that?
[Nexus 7 (2013) Original Android Development] harryyoud:
It is, however they often lag behind AOSP by 3-7 days. Presumably you are asking about official ROM?
[Nexus 7 (2013) Original Android Development] pijetri:
Yes i have, i will flash lineageos on my nexus 2013 if security patches / strings are updated.
[Nexus 7 (2013) Original Android Development] ripee:
My daily builds for deb and flo

If anyone's interested, I'm building (almost) daily for both variants from LineageOS repos, because I have a flo myself and I'm too impatient to wait for official weekly builds :D I include built-in root and repo sync before each and every build, so security updates are promptly available. Links in my signature. Thank you, hazzer, for all your hard work.
[Nexus 7 (2013) Original Android Development] Bright09:
so is this still in development?
[Nexus 7 (2013) Original Android Development] tombraga:
setup wizzard problem

i have the last cm-14.1-20161225-nightly-flo working fine on my Nexus 7 wifi - never had problems with network connection

i tried to install now the newest Lineage 14.1-20170418-nightly-flo with open_gapps-arm-7.1-nano-20170425 and then rooted with supersu 2.79

installing ok, also the Lineage OS started, but after the choosing the language i got problems on setup wizzard. get the message when i choose new device.

and when i try to use existing cloud account, there is message no networking discovered...

and there is no skip button to make the setup later, nothing to do...

somebody can help?
[Nexus 7 (2013) Original Android Development] Bingley:
Fast.com speed test always at 4meg, line is 17meg on every other device. Fine otherwise.
[Nexus 7 (2013) Original Android Development] Bright09:
how do i get google camera on i know nano package works but if i tired aroma etc before it wont when i select a few apps would love to have a better camera thought i was kinda getting flickering from it last night
[Nexus 7 (2013) Original Android Development] coremania:
Are your Los builds for flo with oms support? Which root is inbuilt? Magisk?
[Nexus 7 (2013) Original Android Development] ripee:
I use official Lineage sources, so if they merged OMS then it's in there. The built-in root is the one added with the "export WITH_SU=true" line, not Magisk.
[Nexus 7 (2013) Original Android Development] coremania:
Thanks, I don't think this will happen in the near future, that's why I was hopefully asking.
[Nexus 7 (2013) Original Android Development] RunNgun42:
Maybe update the OP to reflect this, your original links all point to a dead page
[Nexus 7 (2013) Original Android Development] sidamos77:
I have a problem installing Lineage official on FLO. I installed newest TWRP. Then wiped everything. Then installed lineage-14.1-20170502-nightly-flo-signed. Then open_gapps-arm-7.1-nano-20170504 and addonsu-arm-signed.

I have done the same (but with Pico GApps) on my Nexus 5 without problems.

But with FLO, the setup wizard crashes all the time. So, I rebooted to TWRP and deleted it. Then I can boot the system. But now I can not activate developer settings (tapping dozens of times on build number does nothing) and I cannot download anything from the Play Store (after adding my Google account).

Also, in fastboot mode, the PC does not see the device anymore, so I can't transfer other files, for example different versions of Lineage or GApps.

I can only reflash everything but then I have the same problem with the setup wizard again.

Any ideas would be greatly appreciated.

BTW, the setup wizard offers emergency calls, although I have Wifi-only FLO.

Edit:

It was the missing internet connection. When the setup wizard crashed again, I was able to access settings and configure WiFi. With the next try, everything worked.
[Nexus 7 (2013) Original Android Development] Aaron9788:
Home button not working

I have flashed the latest nightly build for my Nexus 7 WiFi version and the home and multitask buttons will not work. The back button works just fine it's just those two. Also, I cannot install anything from the Play store, it just says download pending and never starts. Any advice would be appreciated!
[Nexus 7 (2013) Original Android Development] androidfr33k:
I don't even see the Nexus 7 2013 listed on his link?
[Nexus 7 (2013) Original Android Development] coremania:
It's now officially supported, that's why.

https://download.lineageos.org/flo

https://download.lineageos.org/deb
[Nexus 7 (2013) Original Android Development] sidamos77:
The N7 only charges with <1 A with the original charger. Is this a known problem with LOS? I just got the tablet and immediately installed LOS.
[Nexus 7 (2013) Original Android Development] pilotv:
No problem here with my N7 2013. I use any available charger in home without issues.
[Nexus 7 (2013) Original Android Development] beachfl:
Did you try a factory reset/wipe clean first?

---------- Post added at 06:42 AM ---------- Previous post was at 06:40 AM ----------

Nope, all LOS nightlies charge fine for me.
[Nexus 7 (2013) Original Android Development] knotle:
I had the same problem. What you have to do is pull down the notifications shade and click settings icon to get to your WiFi setup. It will then let you continue.
[Nexus 7 (2013) Original Android Development] Bright09:
is there going to be double tap to wake or is there a mod i could add it to kinda missing the feature
[Nexus 7 (2013) Original Android Development] sidamos77:
The Glitch kernel has this feature, but I did not test it.
[Nexus 7 (2013) Original Android Development] pilotv:
Use ElementalX kernel. It's working on my N7 2013.
[Nexus 7 (2013) Original Android Development] r.sorujlall:
Hi, were you about to find a fix for the download option on netflix? i ask because i really need this feature. i no longer have wifi where i live so i want to use my tablet to download my shows while i'm at work and watch at home
[Nexus 7 (2013) Original Android Development] fruity101079:
Hello

Noob question:

What're the differences with the official rom? Why should I flash yours instead of the official?

You wrote : "The ROM is basically CyanogenMod but with changes to the name. "

But what does it mean? Only related to CM which became Lineage os?

Thank you.

edit: Nevermind, i took the official realease, it works great.
[Nexus 7 (2013) Original Android Development] Bingley:
No new build for this week? Deb had it on 22nd
[Nexus 7 (2013) Original Android Development] beachfl:
Flo nightly is up there now.. named 20170524. :) Running it as I speak. Thanks LOS team!
[Nexus 7 (2013) Original Android Development] Bright09:
Is magisk defaulted now?
[Nexus 7 (2013) Original Android Development] Skyrocket2Paradise:
delete
[Nexus 7 (2013) Original Android Development] Piksou:
Is everyone else also having the N7 2013 identified as N7 (2012) ? Nobody can get this info to the maintainer ? :(
[Nexus 7 (2013) Original Android Development] beachfl:
It's happened to me (and others) before, but not lately to me, and I don't think I've ever had that issue with LineageOS. When it was wrong, it would report it wrong inconsistently, too - to Google online and to some on-board utilities it would report as 2012, but not all. :confused:

Here's an old thread on it, tho - https://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/nexus-7-2013-wi-fi-2012-model-720p-t3441018 . I'm currently running LineageOS' 20170613 nightly.
[Nexus 7 (2013) Original Android Development] Piksou:
Ah so this is weird and also worse than what I have.

My resolution is fine and I just have the model incorrectly listed. Assumed it was a build.prop issue but apparently not if you guys are fine ? I am using 20170613 too but I updated from older build so maybe it's an old bug that's surviving updates and I need to once again full wipe.
[Nexus 7 (2013) Original Android Development] defim:
I tried to update CM-14.1 to LOS-14.1. This failed with error 7. So i found that i need an "experimental" LOS build. But sadly they are no more available. I think "lineage-14.1-20170124-experimental-flo-signed.zip" MD5: 4dae04329df8ae3c28efa2b01d086d3d should work. Has anyone this file and could share it?
[Nexus 7 (2013) Original Android Development] Bright09:
Can I dirty flash update from 6-13 to current 6-20 I just installed yesterday and I haven't dirty flashed for a long time.
[Nexus 7 (2013) Original Android Development] Spyr0s:
On my good old i9100 (Samsung S2) running LOS I'm getting a battery meter next to the Bluetooth icon that shows the remaining battery of my bt headset but on Nexus flo this doesn't happen. Is this a hardware limitation or just something that was disregarded. I thought that bt battery on taskbar was a LOS feature.
[Nexus 7 (2013) Original Android Development] beachfl:
Yup. The official advice says you can, and I do. I do clear cache and Dalvik/ARM tho.
[Nexus 7 (2013) Original Android Development] jstsmblaz:
Does live display work for you guys?
[Nexus 7 (2013) Original Android Development] Konstigt:
Me too at least. You can do it?

https://wiki.lineageos.org/bugreport-howto.html
[Nexus 7 (2013) Original Android Development] beachfl:
It does for me.
[Nexus 7 (2013) Original Android Development] ksaves2:
Hi, Anyone try the VOIP/SIP phone calling app TalkaTone on an N7 2013 Flo or LTE to work? I can only get it working with the last 6.0.1 ROM for the LTE model. After dialing the screen app screen disappears.

For folks who don't know what I'm talking about, look up TalkaTone and it will allow cell phone calls over VOIP/SIP via a data SIM using data or over WiFi. Down side is quality varies but I've found it workable.

Lineage or crDroid won't work and I think it's a handicap of the 7.1.2 ROMs with this app as well as 6.0.1. Flo can do it via fast WiFi with the last supported kernel but Lineage won't work with it either. Kurt
[Nexus 7 (2013) Original Android Development] Sindee75:
[MENTION=4501300]defim[/MENTION] or anyone who can help. I have a nexus 7 2013 with the good ol ghost touch screen issues. Various hardware fixes did not help. Anyway, I read some had this problem after 5.01 update. So, I used nexus root tool to downgrade to 4.4.4 version. Google play store and services errors. So i installed the lineage nugout rom. Now i cannot get past the boot animation. Tried wipes, no help. Can anyone advice me please? Thanks, Cindy
[Nexus 7 (2013) Original Android Development] defim:
[MENTION=7935372]Sindee75[/MENTION]: On preoblems i would start from scratch with latest official version (Android 6). I never had hardware issues with Nexus 7
[Nexus 7 (2013) Original Android Development] Sindee75:
Tried from scratch. I also get stuck at boot animation on factory image 6.0.1. Did all wipes, format, factory resets first and still get stuck at boot animation. The only nexus firmware that does not get stuck is 4.4.4 but google play services and store crash. What is causing being stuck in boot animations and how to get out of it? Thanks, Cindy
[Nexus 7 (2013) Original Android Development] Spyr0s:
You need also to update the bootloader and twrp, download the Nexus Root Toolkit and flash latest factory image before installing LOS14.1 or update bootlader via adb/toolkit.
[Nexus 7 (2013) Original Android Development] Sindee75:
Have updated all files, boot.img, system.img, cache, user data, etc. And twrp latest version 3.1.1 both ways via adb/fastboot and the toolkit. I wipe clean before each firmware stock or custom Rom. Why will the only Rom work is nexus 4.4.4, jss15r And below? But google services and apps crashes on those? Even wipe data, cache, system and data, format, factory resets before each try. Nothing works yet. Please help.. thanks...
[Nexus 7 (2013) Original Android Development] Spyr0s:
which gapps package you re using? you need nano or pico for cm13 and above, stock size gapps are not working after cm13
[Nexus 7 (2013) Original Android Development] Sindee75:
Have tried Pico, nano and mini ... ugggg!
[Nexus 7 (2013) Original Android Development] Spyr0s:
Try Nexus Root Toolkit, Flash Stock Unroot with Soft_Bricked/Bootlloop option. If this doesn't work i don't know what to say anymore, maybe it's a hardware problem.
[Nexus 7 (2013) Original Android Development] Sindee75:
I'll try toolkit flash stock unroot with softbricked dont remember seeing option. Do i install twrp first with this method? Can u give me step by step of what you mean please? Thanks
[Nexus 7 (2013) Original Android Development] Spyr0s:
This method will install stock recovery and you will need to flash twrp if you want to install LOS but your goal is to make your tablet work first and then customise it.
[Nexus 7 (2013) Original Android Development] Sindee75:
Opened toolkit and realized that I have been choosing stock unroot and softbrick/bootloop option. I've done it again to try and bring it back to android 6.0.1. Again, it is sitting at boot animation for 30 minutes. I'll wait another hour then try LOS, but if I try another Rom while this is stuck in boot animation the next Rom gets stuck in boot animation. I think we need to figure out how to get past this problem first, don't you? Thanks for your help...
[Nexus 7 (2013) Original Android Development] Sindee75:
Still stuck at 6.0.1 boot animation. Googling everything to get out of this. So far, I have tried everything I have googled thus far. I'm certain if I load lineage os or any os for that matter I will be stuck at boot animation. The only is that gets me past the animation is stock 4.4.4, but that is useless without google play and services not working. Any help out there??
[Nexus 7 (2013) Original Android Development] coremania:
What happen if you flash latest official Google factory image, flash it step by step the classic way with fastboot.

You can use latest minimal adb&fastboot for it, don't use any tools. Do you get any error messages?
[Nexus 7 (2013) Original Android Development] Sindee75:
Hello, i have used fastboot/adb and all factory images only work BELOW 5.0, why? Only stock images below 5.0 work. Can you please help? Everything above 4.4.4 gets stuck in boot animation. Can't get past it. I've done wipes, factory resets, formats, reinstalls, nothing I have tried helps. Please help. Thanks, Cindy
[Nexus 7 (2013) Original Android Development] coremania:
Yes, you wrote that before, did you use the flash all command, or did you flash commands step by step.

Kitkat is working, what happen if you just upgrade your bootloader. If you flash step by step may you be able to isolate your problem.

Edit: if it's similar to the lollipop update brick, you're could be lucky by flashing the first 6.0.0 image, like a reddit user reported that it fixes, he was using the toolkit too. If you're not lucky it's the hardware issue and you have to replace the motherboard.
[Nexus 7 (2013) Original Android Development] Sindee75:
Yes, I have flashed each file individually and the flash all command. Also sideloaded the OTA 6.0.1 and have used the toolkit. When i flash the package, it also flashes the bootloader, not sure what you mean but I have reflashed the bootloader file over the the latest bootloader for my system.

I have flashed the first 6.0.0 image, no luck. If it is a motherboard issue, why would kitkat be able to boot up okay?

This has been driving me bonkers for 2 weeks ? my problems began when downgrading to kitkat then installing a custom Rom for kitkat because google play store and services crashes on kitkat. It is almost as if the 4.4.4 is holding a setting or something. But I gave formatted the tablet and flashed bootloader so you would think that would have fixed it?

There has got to be something I am missing to fix this.

I do appreciate your help. Anything else you can think of me to do, I'll do it.
[Nexus 7 (2013) Original Android Development] coremania:
Not really, never heard before that someone has been damned to use kitkat. Shot into the blue, lock and relock the bootloader for wiping?
[Nexus 7 (2013) Original Android Development] Sindee75:
Did not want to go back to kitkat.. I had the ghost touch screen problems and new digitizer did not fix it. Read that after lollipop upgrade many had touch screen issues so I wanted to downgrade to before lollipop to see if touch screen issues would go away.

There is always a method to my madness, lol!

Shot in the blue.. Do you mean lock bootloader twice then wipe?
[Nexus 7 (2013) Original Android Development] coremania:
Locking or unlocking the bootloader will always wipe your device. By the way, if you wipe caches with the recovery do you get any errors, like not able to mount?
[Nexus 7 (2013) Original Android Development] Sindee75:
Right now bootloader Is unlocked. I have locked it and unlocked it and wiped everything at least 2 dozen times, so I have no problem wiping..

I get no errors wiping cache...
[Nexus 7 (2013) Original Android Development] Sindee75:
Question. What if I flash the old bootloader from 4.4.4 that allows boot then flash newer 6.01 system, user data, cache and recovery images?? I dont know if the system image verifies the bootloader version?

Thanks
[Nexus 7 (2013) Original Android Development] coremania:
Try it, these days I never flashed back any device back to kitkat.

Edit: best for you before you continue with endless tryouts is to do a logcat while you're in bootloop. There are several threads here on xda how to do, and experienced members can take a look, tell you your issue and help you out.
[Nexus 7 (2013) Original Android Development] ptesmoke:
Anyone manage to get Netflix working??
[Nexus 7 (2013) Original Android Development] drmarble:
Netflix 4.8.7 build 9783 is the last version that works. No download videos with this version. Find it and side load it.

The disabling drm trick (breaking google play movies) stopped working a few Netflix versions ago. Downloads didn't work with this tsrick anyway.

LineageOS developers are aware of the problem and have found no solution except blame Netflix.
[Nexus 7 (2013) Original Android Development] NamenIos:
Has anyone encountered rendering bugs like in the pictures ever? Maybe in older versions of the rom?

Disclaimer, the screenshots are from another device (fusion3) and I don't own Flo, this is just for hunting down a bug.
[Nexus 7 (2013) Original Android Development] wolfder92:
Hello everyone. Has anybody encountered the issue were the device results in nexus 7(2012)? I am running 20170911- Nightly-deb official.
[Nexus 7 (2013) Original Android Development] jhford:
I can't find the link to your builds. I have a 2013 deb running 14.1-20171002-NIGHTLY-deb, and it's horribly slow. Haven't tried Elementalx or a new nightly. I was thinking about going back to stock, but just read your thread. I await your advise.

Thanks
[Nexus 7 (2013) Original Android Development] jhford:
Slow

My deb was so slow, I upgraded to the latest nightly. After flashing it was fast and perfect. But it slowed to a crawl after about an hour. Why? What can I do? Do I have to go back to stock?
[Nexus 7 (2013) Original Android Development] k_illen_:
I have just updated both my phone Moto G LTE (Peregrine) and my Nexus 7 (Flo) with one of the latest LineageOS nightlies

Peregrine is running lineage-14.1-20171124-nightly-peregrine-signed.zip

Flo is running lineage-14.1-20171121-nightly-flo-signed.zip

And now I have an issue when Im trying to connect to my own L2TP/IPSEC VPN server running libreswan,

but the issue only occurs on my Nexus 7. The VPN connection is working fine on my phone so I tried to read the logfile /var/log/auth.log on the server to see the difference between the unsuccessful connection attempt and the successful one

it seems like the handshake using

SP transform ESP_AES(256) / auth AUTH_ALGORITHM_HMAC_SHA2_512 not implemented or allowed

is not working

I have the following chippers in my /etc/ipsec.conf

ike=aes256-sha2_256,3des-sha1,aes-sha1

phase2alg=aes256-sha2_256,3des-sha1,aes-sha1

sha2-truncbug=yes

Since it working on my phone but not on my nexus7 2013 I guess its because of a bug in , I hope someone can remove the bug
[Nexus 7 (2013) Original Android Development] droiduzr2:
Great ROM.

My USB stopped working. It was fine 2 builds ago.

I plug in USB to 2 different windows 10 laptops.

I pick MTP but Windows error that it will not see the tablet.

I pick PTP mode but it will only show me the picture folder.

What's happening here?

Thanks!