yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] MarviXDA:
I think, every Android 10 device. IMHO.

---------- Post added at 09:29 PM ---------- Previous post was at 09:22 PM ----------

Now I am sure. This is contens of script:

ui_print("");

ui_print("TWRP flashable pattern/pin remover");

ui_print("");

ui_print("");

ui_print("");

delete("/data/system/password.key");

delete("/data/system/pattern.key");

delete("/data/system/gatekeeper.password.key");

delete("/data/system/gatekeeper.pattern.key");

delete("/data/system/locksettings.db-wal");

delete("/data/system/locksettings.db-shm");

delete("/data/system/locksettings.db");

ui_print("");

ui_print("Files removed - please reboot!");

ui_print("");

ui_print("OK Done");
[Nexus 7 (2013) Android Development] matt.weatherford:
Hi,

Thank you very much for this work on the 2013 Nexus 7 variants!

It is amazing to be able to run Android 10 pie on these great devices.

I was a little confused by this thread from like 2007 initially (posts on page 1) might be worth starting a new thread, but just a tiny suggestion. ;)

I just followed the top post directions and installed the FLO build

It is working great (AospExtended-v7.0-flo-20200122-1535-UNOFFICIAL.zip)

Here are a few links I hope will help assist the next person - feel free to add to top post if you think it worthy:

TWRP builds for DEB and FLO Nexus 7 tablets:

ttps://dl.twrp.me/flo/

ttps://dl.twrp.me/deb/

Open GAPPS for Android 10 for Flo/Deb:

ttps://opengapps.org/#downloadsection

** Choose ARM / 10 / Pico and click download arrow

Look forward to more of these builds - keep up the great work!

-Matt in Seattle, WA
[Nexus 7 (2013) Android Development] stunned:
Early usage suggests that AEX 7.0 version is working great :) , Pie version was getting pretty unusable.

I do get settings crash if I try to change or access Lockscreen UI in extensions. Is that normal (bug)? I'm using one step bigger display size than default, otherwise all is default, no root etc.
[Nexus 7 (2013) Android Development] MarviXDA:
On my (rooted) devices lockscreen ui settings are working with no crashes.

What display do you use? Can you give devchek results, please?
[Nexus 7 (2013) Android Development] stunned:
I mean i just changed dpi with built in slider, no external display. Change is just somewhat big because many apps change to phone ui from tablet ui
[Nexus 7 (2013) Android Development] MarviXDA:
Ou!

It works without any crashes.
[Nexus 7 (2013) Android Development] matt.weatherford:
I picked up a "new" stock nexus 7 2013 (flo) today for $25 from craigslist...

I got twrp flashed then tried to use the script in post #1 to redo the partitions (sysrepart_1280_120.zip) , but it threw a bunch of errors and

now I have trashed partitions on the Nexus 7 and cant even flash the TWRP recovery. I can 'fastboot flash boot boot.img' but not recovery.

I can boot in to the bootloaded. I can run fastboot commands over USB from a pc/mac/linux.

I can even boot in to TWRP3.3.1-1UA.-flo.img over USB cable from a linux box using a sorta sideloaded Recovery like this:

fastboot boot twrp-3.3.1-1_UA-flo.img

Which is pretty cool, but I still am not sure how to get a good partition map back on this Nexus 7 2013 wifi (flo)

But TWRP still complains that there is no /system, /vendor, or /data partition.

I tried re-running the partition script at the beginning of this thread

Would some kind soul please point me in the right direction?

Thanks in advance,

Matt
[Nexus 7 (2013) Android Development] n3kf:
When I have gotten into this situations, I have found the only way to fix it was to do a complete factory restore to whatever the last supported level was.

https://www.androidpolice.com/2013/...stock-using-a-full-factory-image-and-root-it/
[Nexus 7 (2013) Android Development] ipdev:
Hi.

I am a little confused with the errors you are describing.

What and When are these errors happening?

1. Why are you using the UA version of TWRP?

2. Did you boot the device first to make sure it worked when you got it?

3. Did you update it to the latest Google factory-image?

-- Updating the firmware can be handled later if it needs to be updated. --

4. Do you get the same errors/results using the last official TWRP?

TWRP

Nexus 7 (2013) WiFi (flo) twrp.me - Link

Nexus 7 (2013) LTE (deb) twrp.me - Link

Note:

There is no Vendor partition originally on this device.

Vendor is created if you use Clamor's xda-thread - Link repartitioning script.

It also increases the size of the recovery partition, UA version of TWRP is a little bigger so it will not fit on the stock recovery sized partition.

- The reason you can fastboot boot it but, not flash it?

- I'm guessing the vendor error is also in UA-TWRP.. ?

I'm guessing the partitions were changed and you just need to format them.

I do not want to guide you down the wrong path.

Download and try using the regular (official) TWRP and see if the same errors happen.

[You may have to fastboot erase recovery then fastboot flash recovery

twrp-3.3.1-0-flo.img]

Note 2:

Clamor's repartitioning scripts work fine. A little heavy handed but, work great.

I used his repartition scripts on my Nexus 4 and 5.

Reverted my Nexus 7 (flo) and tested his repartitioning. Worked great, only problem was reverting back to stock (at least on flo) partitions were off. (Sectors did not match factory partitions.)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] matt.weatherford:
N3kf and ipdev,

First ,thank you both for your replies - I really appreciate that!

I am now back in business. I used the fastboot recovery boot-over-usb of the UA version of twrp (what is this UA version and how is it different the the latest UA?) Once booted, I used the Clamor repartitioning tool (last time I tried I think I forgot to actually log in with adb shell and run by hand the shell script/command that *really* does the work because that message scrolled up off the TWRP screen after I flashed it) Clamor repartition succeeded. Then I was able to format /system, flash a rom, latest twrp, etc. After I verified that worked, I ran the repartition script at the start of this thread, and everything seems happy again.

Last Question, not urgent, the Clamor repartition process works but specifies the TWRP-UA version 3.3.1-UA

Is that newer or older than 3.3.1 here: ttps://dl.twrp.me/flo/ ?

Should I be using the plain old 3.3.1 ?

thanks again, Another resurrected nexus 7 kept in service and out of the landfill - great work folks ! :)

Matt
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.0 - February 2020

AEX Team merged security patches quickly this month ..

As well I have patched framework/base to support microG.

AospExtended-v7.0-flo-20200207-1513-UNOFFICIAL.zip

AospExtended-v7.0-deb-20200207-1719-UNOFFICIAL.zip

Changes:

- Google security updates -> February 2020 (android-10.0.0_r28)

- Patched framework/base to support microG

- Latest AospExtended changes for Android 10

Pls check first page for installation instruction !

The ROM installer will backup existing opengapps and magisk installation.

Enjoy Android 10 :p
[Nexus 7 (2013) Android Development] JT1510365:
Great job and work as always buddy:)
[Nexus 7 (2013) Android Development] m00head:
https://xdaforums.com/showpost.php?p=71737710&postcount=225

This issue has also been mentioned previously in this thread here and here.
[Nexus 7 (2013) Android Development] followmsi:
The first "unofficial" versions are coming for the gapps issues on 7.1.2 ..

https://xdaforums.com/showpost.php?p=71802639&postcount=4151
[Nexus 7 (2013) Android Development] vkk178:
Wiping system from Devswifts ROM and installing this ROM worked fine for me so far.Thx [MENTION=5480152]followmsi[/MENTION].I downloaded gapps mini and installed it with this custom gapps-config.txt script

MicroGApps

googlenow

Can system partition be formatted to f2fs ? Is it worth it ?
[Nexus 7 (2013) Android Development] followmsi:
No .. not system partition .. just /data and /cache partitions are ready for F2FS. (fstab)

Would not recommend to change system to f2fs.

Next to some other problems .. F2FS is speeding up the write process - which we don't need on READ-ONLY partition. :)

Hope this helps ..
[Nexus 7 (2013) Android Development] vkk178:
Thx I have only formatted cache to f2fs .I guess formatting data also wipes out the internal storage , so will keep it as is for a while
[Nexus 7 (2013) Android Development] followmsi:
Yep, internal storage will get lost if you change to F2FS.

Like you assume .. it's a part of the data partition.
[Nexus 7 (2013) Android Development] dealpapa1:
can we just remove the music app? the patch is still not working for me.
[Nexus 7 (2013) Android Development] followmsi:
Did you grant access to storage for the music app ?

Manually ?

Then it should work .. ;)

You can mount the system RM and just delete Music folder in /system/priv-app.
[Nexus 7 (2013) Android Development] m00head:
Is 5GHz WiFi working on this ROM?

Using the WiFi Analyzer app, I can see lots of WiFi networks in the 2.4GHz range, but non when I switch into 5GHz mode.

Also, I remember that the stock ROM had these options, which are missing from this ROM:

Settings -> Wi-Fi -> Advanced -> Wi-Fi Frequency band -> [Auto | 5 GHz only | 2.4 GHz only]
[Nexus 7 (2013) Android Development] followmsi:
Don't know the switch in menu.

But 5ghz wifi works as expected, at least for me.
[Nexus 7 (2013) Android Development] mrbtree98:
I think it's a thing with nougat in general. It's the same on purenexus, Los on my Oppo R7 Plus and my HTC One m9 on stock 7.0 so it's probably the way it should be.
[Nexus 7 (2013) Android Development] followmsi:
Yep, seems to be removed ..

https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
[Nexus 7 (2013) Android Development] jaibar:
It looks really cool- the line can also be added to build.prop using root explorer (and any similar root file viewer with text editor, for that matter).

Only drawback is when using split/multi window, the recents become quite small- kind of looks awkward..
[Nexus 7 (2013) Android Development] dealpapa1:
you are the best dev in the xda I ever met. Thank you so much for your hard work and help.

http://www.droidviews.com/twrp-recovery-explored-and-explained/

do you mean to mount from twrp? :D
[Nexus 7 (2013) Android Development] followmsi:
Thanks ..

This can be done in system too .. "mount -o rw,remount /system" in terminal app as root.
[Nexus 7 (2013) Android Development] rajsris:
Overall I like grid multitasking. Just takes some getting used to because you can't swipe to quit apps like regular multitasking.
[Nexus 7 (2013) Android Development] followmsi:
Yes .. you need to get used to it :)

Will activate this view per default in next relase .. you can always disable via build.prop.
[Nexus 7 (2013) Android Development] followmsi:
The new setupwizards did arrive on github :)

https://github.com/opengapps/all/commit/36165c50e438f3e5193b07076b213d5bf19f1f9c
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Hm... I don't liked "grid" mode, very small windows, when a lot of task has been opened... The regular much better.
[Nexus 7 (2013) Android Development] miki67:
I agree with you... "Old" mode is much better, swipe to close many open tabs is easier, faster and comfortable... [emoji6]

Inviato dal mio Asus Zenfone 2 (ze551ml) con Tapatalk 6
[Nexus 7 (2013) Android Development] MarviXDA:
Wonderful!
[Nexus 7 (2013) Android Development] reignydeyz:
Lock screen takes a while to authenticate

Just wondering... I noticed almost all Android Q builds are taking so much time to authenticate on the lock screen - especially when the device has just booted up.

I usually got caught by 2 to 3 timeouts before having a successful login. I have to press the power button again and again...
[Nexus 7 (2013) Android Development] nicky-xda:
w

ake on plug: cannot be switched off?

On my device the display turns alway on when i connect/disconnect it by usb.

When i de-activate the "settings/display/wake on plug" it always gets reset to activated as soon as i go out of the settings and open them again.
[Nexus 7 (2013) Android Development] BigB451:
I tried to reboot and now my screen is always black. If I plug it into my computer, I can hear the ding when I hold down the power button. Is there some way that I can save the tablet? Thank you!
[Nexus 7 (2013) Android Development] MarviXDA:
It's hardware issue, in my opinion. Disassemble your device and check screen cable.
[Nexus 7 (2013) Android Development] AlmostIdiot:
It's a great rom, but despite all the great things, I have a problem with ram management. How to avoid apps getting killed after locking screen?
[Nexus 7 (2013) Android Development] vagelis74:
Dirty Flash the latest rom aex and I have problem with play store and Google,I can't download anything, I try open gaps but the file it's bin and not zip. Any solution?
[Nexus 7 (2013) Android Development] MarviXDA:
Use another browser for downloading.

Google Chrome for example.

I have the same trouble with Via browser.
[Nexus 7 (2013) Android Development] moviefirst:
Flashed aex for the first time comming from lineage 17.1 ( clean flahs ) and everything is working great.

Thanks Dev! Great job.
[Nexus 7 (2013) Android Development] vagelis74:
Thanks
[Nexus 7 (2013) Android Development] AlmostIdiot:
Is elementalx kernel integrated into the latest version of AEX?
[Nexus 7 (2013) Android Development] BigB451:
That would've been my first thought, but it happened on a restart. Also, a few posts in this thread speak of a black screen.
[Nexus 7 (2013) Android Development] MarviXDA:
If you can not boot even into recovery and into bootloader, this is not problem of the rom. It's hardware issue.
[Nexus 7 (2013) Android Development] andythegreat:
Keep on getting error 7
[Nexus 7 (2013) Android Development] MarviXDA:
Solution is similar to that of error 70. Read 1-st post.
[Nexus 7 (2013) Android Development] BigB451:
I would've thought that, but it happened on a restart. Hardware problem nevertheless, you think?
[Nexus 7 (2013) Android Development] MarviXDA:
Yes. firmware in terms of boot is the next step after working out the primary bootloader. Firmware can be very different with the same bootloader. these are different things. In addition, the bootloader itself is not affected in any way during the firmware process. your bootloader seems to be damaged. the reason is not yet clear, but the reason is definitely not rom.
[Nexus 7 (2013) Android Development] BigB451:
Got it. Thanks very much. What, if anything, can I try at this point to salvage the tablet?
[Nexus 7 (2013) Android Development] Tommy Jordan:
Where is APN settings?

I could install deb version successfully.

But I can't find APN settings page and connect with mobile network.

Where is APN settings page?
[Nexus 7 (2013) Android Development] MarviXDA:
https://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/fix-nexus-7-2013-bricked-stuck-t3310608/page1

---------- Post added at 05:51 AM ---------- Previous post was at 05:49 AM ----------

What is your mobile provider?

UPD. You are right. There is no APN section in settings.

As for me, mobile network just works.
[Nexus 7 (2013) Android Development] m00nlighter:
Guys, is there any kernel for this ROM that supports both overclocking and undervolting?
[Nexus 7 (2013) Android Development] Tommy Jordan:
My provider is LINE mobile in Japan.

Why is there no APN section in android 10 settings?
[Nexus 7 (2013) Android Development] Ler0y:
Hello friends, i have some funny issue.

My device is Nexus 7 32 Gb Wi-Fi (flo)

on stock system (android 6) all works great.

When i install AospExtended-v7.0 2020-02-07, screen rotation don't work after install 0.o

I tried to check and clean (with isopropanol) internal flex cable - it won't help (hmm, when i use stock fw- all work great).

In AIDA64 i don't see any working sensors =(

If you can guys - pls help.
[Nexus 7 (2013) Android Development] MarviXDA:
You can try this recipe
[Nexus 7 (2013) Android Development] 2kpilgrim:
After short test - kudos an dev! Working better than expected.

I have a question about repartitioning:

Have second flo with Rom PIE PE from followmsi cca from Jan 2019. New AOSP should be installed too.

This device was repartitioned with clamor script and twrp_UA installed - vendor partition is there too.

1. AOSP from 07.02.2020 dont need vendor part. Are there new ROMs which needs this

kind of repartition with vendor partition?

2.Is it posible to change this partitioning with k23m sysrepart? Maybe first change to stock partit. and

second step repart with k23m. And install stock Twrp 3.3.1

[MENTION=7280276]ipdev[/MENTION] thanks for post #2979
[Nexus 7 (2013) Android Development] Ler0y:
Hello, i don't know why, but i reinstall AE another time and... - All work fine o.0
[Nexus 7 (2013) Android Development] n3kf:
I had been running the Lineage 17.1 ROM and decided to try this one. Seems to run well. Thanks to all the developers. This seems to share a similar issue to the Lineage ROM. After some period of time with opening apps, the ROM starts getting a bit sluggish and laggy. Watching memory, it appears available memory seems to decline over time, even though apps are closed out. Maybe a slight memory leak? This device seems to share a problem that was seen in the original Nexus 7. Once available memory gets below 150mb or so, the sluggishness and lag starts. As time goes on this can get worse. Has anybody experimented with low memory killer to see if this can be helped a little? Doesn't seem to make a difference what CPU or IO governor's are used, which would make sense. Yes I know this is an older tablet! It's probably related to the 2gb of ram. Of course a reboot solves it for a while.

Is the kernel that is used in this ROM the same that is in the Lineage 17.1 ROM? How difficult would it be to compile an elementalX ROM for this? I'm a long time programmer, but not in the Android environment. Thanks.
[Nexus 7 (2013) Android Development] vkk178:
I recently resurrected my Nexus 7 2013 after more than a year & boy [MENTION=5480152]followmsi[/MENTION] doesn't stop to amaze me . I had one off his initial ROMs 2 years back & this one has gone beyond that . Thanks again [MENTION=5480152]followmsi[/MENTION] & all the developers who put in their effort.

Just one concern like the previous post . App switching is virtually not possible . Not more than one or 2 apps [emoji853] . Are there any tweaks for a better app switching experience? Atleast 4-5 apps . I recall it was better on stock ROM . I have this ROM with micro gapps . Just to try, can I flash back stock ROM with modified partition layout .?

Cheers.

Sent using Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
STANDALONE KERNEL

Last year in March I have made ElementalX kernel for Android Pie.

One year later we use the same sources and original EX config for TEN.

I have added minor patches only (hidden wifi network)

ElementalX-N7-7.02-TEN-20200301.zip (inside KERNEL subfolder)

Sources:

https://github.com/followmsi/flo_elementalx/tree/ElementalX-7.02-TEN

End of last year I have added some patches for ashem and lowmemorykiller into "my" kernel sources.

The patches may have "negative" impact on performance -> needs testing.

For this reason I did remove the related patches from kernel sources now.

This kernel will be used for the next AEX builds ..

flo-deb-followmsi-kernel-ten-20200301.zip (inside KERNEL subfolder)

Sources:

https://github.com/followmsi/android_kernel_google_msm/commits/followmsi-10

As said above .. needs testing - not sure if the reverts will improve peformance .. maybe not.

Pls use TWRP to install the .zip files !

Reboot afterwards .. no need to wipe anything.

Both kernel should run on ALL Android 9 AND 10 ROM for flo/deb devices !

I would love to have more time for Android and this kind of stuff .. but 2020 does not look good .. at least for Android.. :(

Cheers
[Nexus 7 (2013) Android Development] n3kf:
Thanks [MENTION=5480152]followmsi[/MENTION]. Should have figured you were on it. I'll test the kernel with the removed patches and comment on it.
[Nexus 7 (2013) Android Development] n3kf:
Out of the gate, this kernel seems much snapier. But, that's subjective. Give me a day to see if the laggy stuff creeps back in. Thanks again your work is much appreciated!
[Nexus 7 (2013) Android Development] followmsi:
Keep on testing !

A lot of devices are moving from kernel lowmemorykiller towards android user space lowmemorykiller.

We still use "old" 3.4 kernel and need quite some changes to make this working .. made test kernel which is crashing on boot.

As mentioned before .. no more time for all this stuff. :(
[Nexus 7 (2013) Android Development] n3kf:
So far, it certainly seems better then the previous kernel. Yes I understand that you got to use the old kernel and try to cherry pick changes. I'll try loading it up more. Maybe if I can get my "feet wet" for a while, I can help you out some down the road. But not really ready for that yet!!!
[Nexus 7 (2013) Android Development] fatsix:
The system repartition link isn't working. Anybody ale to help?
[Nexus 7 (2013) Android Development] Ch3vr0n:
Which gapps are recommended?
[Nexus 7 (2013) Android Development] 2kpilgrim:
Personaly use nano gapps without problems.

As on followmsi post #2981: "- Patched framework/base to support microG"

But on opengapps.org only pico and nano gapps for ARM and Android 10 present.

[MENTION=5480152]followmsi[/MENTION]: Stable daily driver. Thanks on you and all developers!
[Nexus 7 (2013) Android Development] n3kf:
[MENTION=5480152]followmsi[/MENTION]

So all in all this is running pretty good. If I load up apps (maybe open 7 or 8) and see free memory gets below 200 -250mb, things start getting laggy, but it still runs. If I push on the task button (right one) and swipe away some apps, things improve. If I swipe all the apps away it runs pretty good for a while. So all in all a good improvement on this kernel. And for the age of the device, have to be happy that I'm actually on 10!

I'll try experimenting with some settings, but overall, think people should be happy.
[Nexus 7 (2013) Android Development] n3kf:
So one more comment. I decided to test the EX Kernel that [MENTION=5480152]followmsi[/MENTION] built. I figured there would not be any difference. But this kernel seems to handle the low memory conditions better. And seems to return the memory faster to the free pool when I swipe the app away. It runs well. Would be interesting for someone else to give it a try and see how it works for them. For now, I am stayng with the EX kernel.
[Nexus 7 (2013) Android Development] 2kpilgrim:
I installed flo-deb-followmsi-kernel-ten-20200301 2 days ago. For GPS in my car, works without glitches. Low memory appearance has not been tested now.

@ n3kf Are there some functional differences between EX and followmsi kernels?
[Nexus 7 (2013) Android Development] n3kf:
Don't really know what the functional differences are. EX is usually pretty customizable. It is known for pretty decent battery life. It appears that it is doing pretty good with battery life. Also it has a couple more CPU and IO governor's. Other then that, I am happy with it. Just for grins, I have another Nexus 7 running Lineage 17.1. put the kernel there and it's running pretty good also. But haven't played a lot with it.
[Nexus 7 (2013) Android Development] 2kpilgrim:
There are several kernel managers in the Play Store. Is there a preferred one to play with? To "doubletape2wake", I use the kernel adiutor.
[Nexus 7 (2013) Android Development] ipdev:
None at the moment. ;)

They all seem to have some fault.

OpenGapps pico/nano are probably the safest for now.

They all work just fine.

fk and ex are both paid apps. Nothing wrong with that, I bought/donated to both.

(fk was just on sale again, not sure if it still is.)

Both fk and ex require you to be logged into PlayStore to check for license.

Kernel Adiutor on the other hand, doesn't.

fk is likely the most updated. (Plus it has some extra features.)

ex is still a solid manager.

KernelAdiutor still works fine.

All depends on you preference.

I use KernelAdiutor quite a lot when testing and not logged into PlayStore.

I still use all three of them. :)

Cheers. :cowboy: