yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] autobulb:
With the correct partition size, and full wipes, 10/11 would not boot for me and go to recovery after a long delay which sounds like what is happening to you guys. Tried 10/05 since other people mentioned they had success with that one, and it installed without a hitch. I would recommend trying known good versions.
[Nexus 7 (2013) Android Development] Droidoidz:
Well that didn't work for me either. Had the same result. Which gapps package (date/(size) and magisk version did you use?
[Nexus 7 (2013) Android Development] jsschmid:
Thanks, I'll try that out today and report if it worked.
[Nexus 7 (2013) Android Development] DerGuteWolf:
pitrus-'s builds: download verification

Does anybody have an idea what caused this?

---------- Post added at 11:57 AM ---------- Previous post was at 11:20 AM ----------

Really?

https://xdaforums.com/nexus-7-2013/orig-development/repartition-nexus-7-2013-repartition-t3844386 refers to twrp-3.3.1-1_UA, https://twrp.me/ has 3.3.1-0 and I found no hint regarding partition sizes in the release notes...
[Nexus 7 (2013) Android Development] dealpapa1:
oh yeah android 10 is coming
[Nexus 7 (2013) Android Development] slinson:
what/where?
[Nexus 7 (2013) Android Development] juliatan:
Is restoring user apps (not system things!) with Titanium Backup not working normal in LOS 16.0? Some apps+appdata restore fine, but with most Titanium hangs. No matter what setting. No matter doing single or batch restore. So I was wondering if this is a normal LOS 16, Android 9 or Magisk 20.0 issue.
[Nexus 7 (2013) Android Development] Nexus7_2013_Flo:
Our device is far from new, so I guess the only security updates we get, are the ones we get through Lineage. No more device dependent security updates. I am doing the same as you, update around the time where the monthly security patches are implemented. I love the ROM, but do not have the time to flash every day. So about once a month suits me well. What I do is just taking a look at the general Lineage OS change log, and look for the entry: "Bump Security String to ...." (Browser search) If you do that you will see that last night there was an entry "Bump Security String to 2019-10-05". It means that this months patches has been implemented in the official Lineage OS 16.0. I assume that this ROM is pulling from official Lineage. So this should be a good indication. I would however wait a day or two with updating, after seeing the entry. To ensure that this included in the ROM. Hope that helps.
[Nexus 7 (2013) Android Development] dealpapa1:
Android 10 is here

AospExtended-v7.0-flo-20191012-2213-ALPHA.zip

AospExtended-v7.0-deb-20191013-0953-ALPHA.zip

lineage-17.0-20191011-UNOFFICIAL-flo.zip

lineage-17.0-20191011-UNOFFICIAL-deb.zip

There will be no pure "classic" AOSP version this time !

Working:

- Video

- Audio

- Wifi

- Bluetooth

- GPS

- Camera (needs more testing)

- Sensors

- DRM

- RIL (DEB device)

- etc.

Known issues:

- NFC has been taken out - maybe next build.

- Video: Some graphics glitches when you start to watch movies. (Skip/Stop video and play again a few seconds later)

- Sensors: Compass not working correctly (same problem on Pie CAF version)

- Maybe more ..
[Nexus 7 (2013) Android Development] Ranbato:
Do you know if HDMI out is working?
[Nexus 7 (2013) Android Development] manishhisnam89:
Super user does not work

Works well but have troubles with Superuser. Does not work after flashing the Rom. Also tried removing and installing Magisk. Both dont work. Any suggestions ?
[Nexus 7 (2013) Android Development] MartinX3:
I got a signature verification error with the build from 20.10.2019

Can someone reproduce it?

Edit: same issue with 19.10.2019

Edit0: Ah, it is a known issue happening by switching between pitrus and ripee's builds.

Seems I did install the other one last time.

Build flashed successful with deactivated verification and the tablet boots fine into android.
[Nexus 7 (2013) Android Development] dealpapa1:
is 16 dead? the god has discontinued the 16
[Nexus 7 (2013) Android Development] M4DNESSS:
Notification LED

Hello. Just installed LOS 16 on my Nexus 7 (2013) flo device.

Problem is: my notification LED does not light up when any notification actually arrives (facebook, viber, battery charging, etc.)

In the settings, however, notification LED flashing when I choose how it should light up (fast, slow, etc.).

Do I miss something? Is there a way to fix this?

Could not find anything helpful on the forum regarding this matter.

Thank you.

..And found one more issue. In Aliexpress app, when trying to "Search by photo", exactly when photo was just made, tablet gets stuck and after 10-20 seconds reboots itself every time I try to use this function. Checked if it was camera issue - camera app works fine, I can take pictures normally.

Same issue happens in Viber and Telegram if I try to send a photo (not from gallery, but straight from camera).

So basically I cannot upload a photo straight from camera to any service.
[Nexus 7 (2013) Android Development] Goon818:
No. It's alive. You get the updates over OTA.
[Nexus 7 (2013) Android Development] efenlay:
link: xdaforums.com/devdb/project/dl/?id=30499

Mine screen -> Advanced -> Terminal -> tape "modify" (several errors will appear and rebooting recovery mode will take ~ 10 min)

Wipe -> Advanced Wipe -> System ->Change File System -> EXT4 then system size will be 1497MB or so.

Then you can install whatever you like.

Thanks real_klaerbaer.
[Nexus 7 (2013) Android Development] kabigo:
Hi,

after running the flo-deb_clamor_repartition.zip and installation of twrp-3.3.1-1_UA-deb.img my deb now always end up in a boot loop (lineage boot logo and then TWRP) after installing LineageOS.

I tried installing lineage-16.0-20191025-UNOFFICIAL-deb and lineage-16.0-20191026-UNOFFICIAL-deb after running the repartition tool and TWRP ua. I also installed again the normal current TWRP before flashing Lineageos without change of the effects. I didn't install any additonal packages (like gapps or su, gapps I tried during my first installation, but I thought just go step by step and install LinageOS first...). BTW I can mount and see a vendor partition and the partition script also didn't complain (typed the modify, rebooted installed TWRP UA, run wipes, installing Lineage).

Allpartitions are ext4 and I was always running wipes (so many wipes ;) ).

Any idea / proposal?

If that doen't work I think I need to look for another smallsized tablet...

Thanks kabigo
[Nexus 7 (2013) Android Development] M4DNESSS:
I had the same problem. I simply followed installation guide step by step again and it worked out for me.

Take care of this step:

4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache.

It does not say to tick Vendor, so do not tick it, just follow step by step, taking this in concideration.

Hope this will help.
[Nexus 7 (2013) Android Development] jhford:
How do I implement OTA? Thanks
[Nexus 7 (2013) Android Development] rho-bot:
OTA is already Built-In:

Settings - System - Extended - Updater
[Nexus 7 (2013) Android Development] M4DNESSS:
Just want to add that notification LED started to work by itself in all applications (Viber, Telegram, Facebook, etc.), but still not when tablet is charging (don't care much about this actually).

But problem with sending photos by apps (Viber, Telegram, Aliexpress, etc.) is still not working. Tablet is sill rebooting every time I attempt to send photo. Any ideas of problem source? Couldn't find something helpful for now.
[Nexus 7 (2013) Android Development] jhford:
Thanks. Do you think 17 will be available in the somewhat near future? BTW, the updater is very cool, but I didn't notice that it wiped dalvik and cache at the end. I don't know why I never noticed the updater mentioned here before.
[Nexus 7 (2013) Android Development] rho-bot:
Early Beta available here: https://xdaforums.com/nexus-7-2013/development/rom-t3569067
[Nexus 7 (2013) Android Development] jhford:
Have you or any of your friends tried it yet? Thoughts? Issues? Thanks
[Nexus 7 (2013) Android Development] ipdev:
While the latest builds are working very good, both Lineage 17 and AEX 7 are still testing (Beta/Alpha) builds.

The Lineage and AospEXtended teams are working on bringing their base up to stable/official status.

Some of the device specific issues may never be solved.

Read the OP [[ROM][flo|deb][UNOFFICIAL][AospExtended-v7.0][Lineage-17.0] - Link and then start at xdaPost 2741 - Link and read (skim) the rest of the thread.

I haven't been posting much in that thread but, I've been testing the builds since the beginning. Give it a try and see for yourself, you might like it. ;)

If you use Gapps, make sure to use a package that doesn't remove Provision.

None of the SetupWizards seem to be working currently on deb/flo. Removing Provision without having a working SetupWizard breaks the UI.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] jhford:
Surely I alone have had this problem.

I use Nova Launcher and a few widgets, including Gmail, Google News, and Google Voice, on my Nexus 7 (2013) debs, but they contain no date on boot. To populate them with date, I have to launch each app from the app drawer. It's a minor PITA, but I'd like to fix it.

Thanks
[Nexus 7 (2013) Android Development] Im ikki:
Bug report

I have faced the touch issue that i cant hold move any app on launcher after enble gesture mode
[Nexus 7 (2013) Android Development] gogol:
I was trying to install this on my Nexus 7 2013 (stock ROM). And I tried to install twrp-3.3.1-1_UA-flo.img from this link:

https://xdaforums.com/nexus-7-2013/orig-development/repartition-nexus-7-2013-repartition-t3844386

Reason because, from what I read, I need to do re-partition first.

But, this TWRP cannot be installed, error "size too large" (see below). Any idea?

C:\Nexus7>fastboot flash recovery twrp-3.3.1-1_UA-flo.img

sending 'recovery' (10498 KB)...

OKAY [ 0.383s]

writing 'recovery'...

FAILED (remote: size too large)

finished. total time: 0.390s
[Nexus 7 (2013) Android Development] dealpapa1:
when will we upgrade to lineage-17.0-20191107-UNOFFICIAL-flo.zip

I really like the ota feature from you
[Nexus 7 (2013) Android Development] pitrus-:
I'm awaiting HDD hotswap cases and some extra SSD:s before I will be migrating the compiler server från Fujitsu hardware to Dell PowerEdge. When I've done this I should have some space available for the 200GB of source code for LineageOS 10 base. Then I can start compiling that too. [emoji4]

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] dealpapa1:
oh yeah:cowboy:
[Nexus 7 (2013) Android Development] schnee1:
This build us getting better with every iteration! Thanks for the work!

I have only 1 issue: Netflix does not work properly....

The app itself loads, I can see the tittles etc. However when I try to play any of the tittle the playback crashes after -30 seconds. Playback in the does not work till the next restart of the device, when it works for another 30 sec....

Earlier in this thread I uploaded some debug output which show some kind of codec crash. Other applications (example Amazon Prime video) works fine
[Nexus 7 (2013) Android Development] riskseeker:
I just wanted to let you know how much i appreciate all your efforts for or beloved nexus 7. LineageOS 16 really made this tablet fast and usable. Never dreamed of getting android 9, let some 10!

Thank you!
[Nexus 7 (2013) Android Development] pitrus-:
Well, I'm just lending out my hardware for free. But we should be thankful for the devs doing the heave software lifting piece which is what really makes this possible. [emoji4]

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] M4DNESSS:
On previous page I already mentioned, that I have an issue with sending a picture straight from camera on any app with this function (Viber, Telegram, etc etc). Tablet gets rebooted every time when I attempt to send a picture with no errors or whatsoever. At first the app is getting stuck for 5-10 seconds, then the reboot follows.

As I see nobody can help me with this issue here, so could someone please tell me if that is only my problem and where I can report this problem so I can get any help with this.

Thank you.
[Nexus 7 (2013) Android Development] riskseeker:
Sorry to day but works fine for me. Upgraded on September 26, last updated to November 6 version.
[Nexus 7 (2013) Android Development] Fuzi0719:
As an aside, any idea why I can never get the OTA to work? It always fails in the download (error message that download failed to verify). I've tried multiple times, but it always fails. I have to download the update to my desktop computer, connect via USB and sideload it.
[Nexus 7 (2013) Android Development] riskseeker:
I had the same issue, maybe still have. Updated to current version so can't try right now.

You can however download on the tablet and update from the internal memory. No need to use laptop for this. BTDT.
[Nexus 7 (2013) Android Development] Fuzi0719:
I think the issue for me was the switch from ripee to pitrus. After asking the question, I read further back and saw someone mention that could cause OTA updating issues from one to the other.
[Nexus 7 (2013) Android Development] kudep:
Can you please spend some words on the install process by using the repartition script?

I feel that I'm doing something wrong when following both instructions (especially when to use which TWRP version), my nexus deb lineage (didn't add any extras like gapps) installation re-boots all the time...

Thanks
[Nexus 7 (2013) Android Development] Ally L.:
how to "recover" from encryption

I encrypted my N7 before I saw the warnings not to encrypt while running this ROM... :D The tablet has been running the 9-27-2019 build ever since, but has not been able to boot into TWRP recovery. I would like to re-do a clean install, but I am a little unsure about the procedure. Do I need to start with a factory reset? Will I need to go through re-partitioning again? Would appreciate pointers on how to proceed. Thanks!!

Edited to add: I did end up doing a factory reset (wiped Data, Cache, and Dalvik in TWRP), followed by formatting the /system partition before installing the ROM. I did not have to re-partition again. After some trial and error, my N7 is now happily running LineageOS 17. :)
[Nexus 7 (2013) Android Development] MorpheusUK:
Have the 16.0 builds stopped now last one I see and was available OTA was the 06/11/2019?

Thanks

---------- Post added at 06:37 PM ---------- Previous post was at 06:37 PM ----------

Have the 16.0 builds stopped now last one I see and was available OTA was the 06/11/2019?

Thanks
[Nexus 7 (2013) Android Development] pitrus-:
Haven't had time to fix the build bot after server change. Will do when I find the time.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] MorpheusUK:
Thanks for the update and your efforts Pitrus.
[Nexus 7 (2013) Android Development] drinkypoo:
Anyone have any tips for extending battery life? Things are working well for me in general but charging is slow and battery runs down more quickly than with stock updated rom.

edit: I used a kernel control app to set the governor to interactive instead of performance, and also enabled fast charge. Now it will actually charge when I'm doing things. It's still not a very good governor, though, at least with default settings. More tuning is needed. Or preferably, a better governor.
[Nexus 7 (2013) Android Development] kozmo2k4:
Thank you [MENTION=4244522]pitrus-[/MENTION], for the new builds.

Updated to Dec 3rd build from Nov 11 (flo), and everything is running smoothly..

:good::good::good:
[Nexus 7 (2013) Android Development] jhford:
Ditto. [MENTION=603202]pitrus[/MENTION].
[Nexus 7 (2013) Android Development] GemWarrioR:
thanks my nexus is alive and well in these rom
[Nexus 7 (2013) Android Development] simo6:
hello, i'm not able to flash latest twrp. i always get this error:

fastboot flash recovery twrp-3.3.1-1_UA-flo.img

target didn't report max-download-size

sending 'recovery' (10498 KB)...

OKAY [ 0.343s]

writing 'recovery'...

FAILED (remote: size too large)

finished. total time: 0.353s

anyone could help pls?
[Nexus 7 (2013) Android Development] simo6:
sorry figured out myself.

but after flashing latest rom then reboots into system i see the lineageos logo for several minutes then it reboots into recovery.. :( (repartition script finished smoothly without any errors)

any ideas?
[Nexus 7 (2013) Android Development] simo6:
looks like gapps package breaking up everything. if i install only the rom it boots up

which opengapps should i use?
[Nexus 7 (2013) Android Development] DerGuteWolf:
I have the same problem (several minutes boot animation, then reboot to recovery), so far tried lineage-16.0-20191205-UNOFFICIAL-flo with open_gapps-arm-9.0-mini-20191204, open_gapps-arm-9.0-micro-20191204 and open_gapps-arm-9.0-mini-20190911 (last one used to work with at least lineage-16.0-20190910-UNOFFICIAL-flo).

Has anybody a current working combination?
[Nexus 7 (2013) Android Development] drinkypoo:
I am using open_gapps-arm-9.0-nano-20191127. I installed lineage, booted up and went through setup, then installed gapps.

I do have a problem, though. I am currently running the build from Dec. 2. Today it killed the battery while on the charger. I was not having problems with battery on the stock (updated) rom. (I have replaced the battery, and it's pretty new.)

What caused me to see your symptoms was to permit TWRP to install the TWRP app as a system app. If I don't let it install as a system app, it just doesn't install. I installed the TWRP app from the play store and that works fine.

---------- Post added at 09:26 PM ---------- Previous post was at 09:21 PM ----------

Sounds like resize didn't work.
[Nexus 7 (2013) Android Development] DerGuteWolf:
Is this the recommend approach? I was always installing both zips at once...

I went now back to open_gapps-arm-9.0-mini-20190911 with lineage-16.0-20190910-UNOFFICIAL-flo, which worked straight away with both zips at once, all other combinations of recent versions including lineage-16.0-20191203-UNOFFICIAL-flo and lineage-16.0-20191205-UNOFFICIAL-flo and open_gapps-arm-9.0-micro-20191204, open_gapps-arm-9.0-mini-20191204 and open_gapps-arm-9.0-mini-20190911 and with/without twrp app did not work.
[Nexus 7 (2013) Android Development] pitrus-:
The recommended way is to flash both ROM and gapps at the same time, as the gapps package removes and/or replaces some of the apps included with the ROM depending on which gapps package you choose. However the officially supported gapps by LineageOS is the nano package.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] simo6:
i've tried to flash only lineage. it boots up. then went back to twrp to flash gapps and it still stuck at lineage logo then reboots to recovery.

formatted data, reflashed only lineage and didnt boot up again.

at last i tried to flash another rom supporting android 9 (aosp) with micro gapps and worked flawlessly. i guess something wrong with the latest lineage package
[Nexus 7 (2013) Android Development] Jean_C:
Unable to install gapps

I managed to install lineage-os and lineage-16.0-20191206-UNOFFICIAL-flo and twrp-3.3.1-1_UA-flo.img

I tried to install open_gapps-arm-9.0-pico-20191127 too but twrp complained about not enough diskspace, error 70.

Tried open_gapps-arm-9.0-pico-20191126 too .

What can i do to install some gapps please?
[Nexus 7 (2013) Android Development] ripee:
No need to use the UA twrp anymore, as Clamor has updated the repartition tool to work with the official twrp. So just flash official twrp 3.3.1-0, reboot recovery, wipe system cache dalvik, flash the rom, gapps, magisk if you want, wipe cache and dalvik again, then reboot system.
[Nexus 7 (2013) Android Development] DerGuteWolf:
Apparently open_gapps has pulled anything newer that 20191127 .

Has somebody a suggestion which lineage-16.0-*-UNOFFICIAL-flo build I should try?

---------- Post added at 03:38 PM ---------- Previous post was at 03:28 PM ----------

But why says https://xdaforums.com/nexus-7-2013/orig-development/repartition-nexus-7-2013-repartition-t3844386 still to use the UA twrp? Is the repartition tool available there the one which will work with the standard twrp or is this version available somwhere else?
[Nexus 7 (2013) Android Development] simo6:
it looks like it was a twrp problem. with the UA lineage didnt boot up. I tried to flash the standard twrp, then flashe lineage added gapps and now it's working
[Nexus 7 (2013) Android Development] DerGuteWolf:
I was now successful with lineage-16.0-20191206-UNOFFICIAL-flo and open_gapps-arm-9.0-nano-20191127 (with UA TWRP)!
[Nexus 7 (2013) Android Development] Jean_C:
damn gapps

Hello, i'm still trying to get gapps on my flo.

When i go into twrp and do Wipe=>Advanced wipe=>select System=>click on Repair/Change File system, i get "Invalid partition".

Seems i'm stuck, help appriciated.

ps, may someone has a command line for me to resize stuff in the terminal?
[Nexus 7 (2013) Android Development] ripee:
Because that thread hasn't been updated in a while.

Flash official twrp, run Clamor's repartitioning zip, reboot back into twrp, go to advanced wipe and wipe everything. Format data then format the other partitions. Now proceed with flashing the rom, gapps, etc.
[Nexus 7 (2013) Android Development] dealpapa1:
the ota server is really slow:rolleyes:
[Nexus 7 (2013) Android Development] brolic925t:
Quick question before I go and buy a battery, screen, and back cover. Is this worth reviving a Nexus 7 for? Is it smooth? Any videos ?
[Nexus 7 (2013) Android Development] kozmo2k4:
Don't have a video of it, but it's my daily driver.
[Nexus 7 (2013) Android Development] pitrus-:
It could be that I'm downloading a lot of torrents at the moment, or that there's a bottleneck somewhere down the road.

The OTA server itself has 12 pieces of Xeon 2.93GHz Westmere cores, 224GB RAM and an 1000/1000 A3 fiber connection here in Sweden [emoji1236] which benches around 600-700Mbps both ways daytime. [emoji2957]

You can test what speeds you get to my OTA server here - > https://speedtest.wickenberg.nu

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] dealpapa1:
i see
[Nexus 7 (2013) Android Development] olliebean:
That page tells me I'm getting an upload speed of 33.4 Mbps, which is impossible as my connection only supports a maximum upload of around 1.2 Mbps.
[Nexus 7 (2013) Android Development] pitrus-:
Interesting, must be a bug in LibreSpeed or in your browser. Could it be that you're running it in Firefox? i saw they fixed a bug with multistream for Firefox users in latest source change.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] olliebean:
In Chrome, on Android. In Firefox, on my PC, it gives a more realistic result.
[Nexus 7 (2013) Android Development] pbrown77:
So I've followed the instructions accurately... Well I has thought so. I already had twrp 2.8.# so installed 3.3.1. Used the repartition tool. Wiped all that was described. Install both the latest rom and google apps and the wiped davic. But it never gets past the blue dot going in an arc (lineage animation I believe) from right to left but it never gets any further. Eventually it reboots back into twrp after a long period.

I have since flashed back to the stock rom and that eventually installs fine. Then tried all this again but it ends the same. Previously I had lineage 14.1 no problems (although I had some problems with some apps so hoped this would fix those problems.)

Any advice?
[Nexus 7 (2013) Android Development] why_So_serious:
I can't seem to get Magisk working. I've tried installing it through the app but it didn't work (fail unknown image). Then i realized that i didnt have root on my device. So i flashed it with TRWP. Everything went fine, but it still fails the basicIntegrity check :/ does anyone haven an idea? Tried the core mode, same result

I think that root is my main issue here. Trust shows that SELinux is deactivated and Root-Access is "ADB-Only".