yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] 0E800:
Thank you [MENTION=5480152]followmsi[/MENTION] for your contributions to the internet.

Playing it forward:

I modified the kernel to support HID Keyboard gadget and patched kernel for Wifi Injection

Resurrection Remix / Android 9 (Pie) + Nethunter for Nexus 7 2013 (Flo)

https://github.com/0E800/Nexus-7-2013-Flo-Experimental/releases/tag/RR_PIE_Flo_Kali

---------- Post added at 03:17 AM ---------- Previous post was at 02:54 AM ----------

Use NRT - its outdated but still works.

Ultimately the more you flash and modify build.prop you closer you get to not being able to verify if issue are from the Rom build or your jacked up device that wont let go of old configs.

I provided links to download the needed files.

https://drive.google.com/open?id=1hRx5VLwh-nqRhCjcWLFg7EpI7QR_nWoP

Download NRT.

Follow instructions for verifying USB drivers.

Download both TWRP files

NRT will want to you to point to the old one, but then you can install the newer one.

Install TWRP

Download razor-lmy48t-factory-0db13100.zip

Chose option to Reset to Factory and select the Android 5.1.1-lmy48t

Show NRT that you already have it downloaded

Factory reset your N7 to razor-lmy48t-factory-0db13100.zip

When finished and your N7 reboots, you will need to go through the setup process on the N7

Once done,

Goto Settings

About Tablet

Click on Build Number 5x to enable Dev Options

Goto Developement Options and enable USB debuging

Plug N7 into computer via USB and alow the computer on your device

Boot into TWRP recovery

In TWRP your computer will be able to copy files to your device after you factory reset.

Wipe your device,

Go back and install your Rom.

Hope this helps, should be enough to get you where you need to go
[Nexus 7 (2013) Android Development] followmsi:
Nice .. thank you !

Did you publish your patched/modifd kernel sources somewhere ? .. just to see what you have patched.

Maybe we can implement it permanently into our kernel.

Cheers
[Nexus 7 (2013) Android Development] tsiftsism:
I thank to both of you for replying, vagelis74 and 0E800.

I'll try to flash the Pie rom as soon as i return back to home from my business trip.
[Nexus 7 (2013) Android Development] tsiftsism:
Can you please help me one more?

- I unlocked bootloader, flashed twrp-3.0.2-0 and after that twrp-3.2.3-0.

- Then i copied flo-deb_clamor_repartition.zip, PixelExperience_flo-9.0-20190325-0235-UNOFFICIAL.zip, open_gapps-arm-9.0-stock-20190324.zip and Magisk-v18.1.zip into a flash drive and i connected it to the device via an otg cable.

- Now while on twrp i select to flash the rom.zip file and i get an ERROR: 7 message which means from what i have read that the rom can't be flashed into /system due to a bigger size file.

- So, i select to flash the reparition.zip, but it also can't be flashed.

Any idea what i have to do?

Thanks in advance for your answer.
[Nexus 7 (2013) Android Development] prsa01:
So even waking from deep sleep your wifi is immediately responsive.?
[Nexus 7 (2013) Android Development] brewer75:
I was having a lagging problem but I recently resized my partitions and did a clean install, now all is good.
[Nexus 7 (2013) Android Development] v12xke:
Yes. Please read the OP? (or re-read again), particularly the section regarding the ERROR: 70 message! Try using the recommended sysrepart_1280_120.zip before doing any thing else. Flash the ROM and then follow directly with the -NANO- Android 9.0 version of OpenGAPPS. Do those together. Then root and kernel. I usually queue up in TWRP - ROM, GAPPS, Magisk, Kernel and flash all 4 together in that order. Try this and report back. :good:
[Nexus 7 (2013) Android Development] brewer75:
Yes
[Nexus 7 (2013) Android Development] ipdev:
ERROR: 70 is lack of space to install.

ERROR: 7 Is a compatibility error.

Wrong version of a file.

Device is detected improperly.

(Quite a few other things depending on what is being checked.)

- The twrp recovery.log should show what triggered the incompatibility error. -

Sometimes just wiping caches and system then rebooting into twrp will work.

(Sometimes wipe or format data may be required.)
[Nexus 7 (2013) Android Development] sir_bazz:
And in addition to the good info in the previous replies, don't bother with opengapps.

Just skip that step as gapps is already included within the PixelExperience rom and gets installed automagically.
[Nexus 7 (2013) Android Development] 0E800:
My apologies... I am not proficient with Github. May you suggest some commands I can run from the kernel dir to push it so that the changes will be available?

I tried removing the .git dir and pushing as new repo but got errors regarding failure to push references.

So then I restored original .git/ folder and tried pushing and got errors.

```

root@keys-daggers:~/rerpie/kernel/google/msm# git remote -v
github [url]https://github.com/followmsi/android_kernel_google_msm[/url] (fetch)
github [url]https://github.com/followmsi/android_kernel_google_msm[/url] (push)
nh_pie [url]https://github.com/0E800/kernel_flo_pie_nh.git[/url] (fetch)
nh_pie [url]https://github.com/0E800/kernel_flo_pie_nh.git[/url] (push)

```

Any help would be greatly appreciated. Mostly I just git clone.
[Nexus 7 (2013) Android Development] followmsi:
grab all code from all repos ..

git fetch --all

checkout my branch onto your machine.

git checkout github/followmsi-pie -b yournewbranchname

Now do all the changes for Nethunter you did before .. and commit them.

git commit -a

Check the git log for your last commit ..

git log

Push the complete branch onto your github

git push nh_pie yournewbranchname

Done.

Check https://github.com/0E800/kernel_flo_pie_nh

Now you should have a new branch called "yournewbranchname" - including the Nethunter modifications.

Cheers
[Nexus 7 (2013) Android Development] 0E800:
Thank you kindly sir.

https://github.com/0E800/kernel_flo_pie_nh/tree/nh_flo_pie

It seemed as though I did not have to re-do my edits as `git commit -a` showed me the list of files that I had altered.

I am confident I will be returning to this post in the future to review the instructions you provided.

Much appreciated, be well.
[Nexus 7 (2013) Android Development] tsiftsism:
Thanks a lot to all of you guys for helping me on how to flash the Pie rom.

Android 9 is up and running on my Nexus 7.

Appreciate it.
[Nexus 7 (2013) Android Development] MikiGry:
Is there any way to reset the device theme to default one without going inside setting ? I think i broke settings by setting AEX theme :/ (they crash every time I try to open them)
[Nexus 7 (2013) Android Development] JT1510365:
No the settings crash is because there is two of the same turbo apps in the ROM you need to boot into twrp mount system go to file manager and delete the folder in system/priv-app called turbo prebuilt and make sure to not delete the one just called turbo. Then factory reset in twrp so you don't have any issues. I wrote about this issue in a previous post. This only happens with all AEX 6.4 ROMs for all devices

BTW I am making my own ROM called lineage extended ROM for flo so stay tuned for that i t will be aosp extended based but will have lineage apps instead of the aosp ones as well as fixes and optimizations as well as a ton of more apps:)
[Nexus 7 (2013) Android Development] MikiGry:
Forgot about that. However I noticed something else. After installing the rom together with Magisk, Magisk does not install (no errors is TWRP). I have to reflash it. And settings start to crash after doing that step. Or after installing YT Vanced Magisk version
[Nexus 7 (2013) Android Development] followmsi:
Just checked your commit .. we missed one command in between :)

Before "git commit -a" we need to use "git add -A" to track all new files.

Like flo_nethuntrer_defconfig and other files.

Cheers
[Nexus 7 (2013) Android Development] JT1510365:
i told you how to fix it and magisk does install and you dont need to reflash it will say installed once you setup the device and reboot i experience no settings crash because i used the way i told you to fix it. I will not help you further and dont expect anyone else to help you either if you dont provide logs or if you included addon mods
[Nexus 7 (2013) Android Development] MikiGry:
Deleting that folder in TWRP does fix the problem (as You told in posts above)

I"m just writing what I faced during instalation process. I know about logs and addons. I"m not a newbie in custom roms world :)
[Nexus 7 (2013) Android Development] JT1510365:
yeah but followmsi already knows about the problem and its something that has to fixed by the AEX team not followmsi he will add the new upstream changes in a new build and hopefully it will bring a fix
[Nexus 7 (2013) Android Development] ipdev:
I thought the extra turbo directory was a problem with the gapps installer script?

I never had that problem, I looked at mine when you made note of the extra turbo directory, mine only has priv-app/TurboPrebuilt

Made sense it was due to gapps install, I use/install delta gapps-base and gapps-keyboard. I assume most are using OpenGApps.
[Nexus 7 (2013) Android Development] JT1510365:
yeah if you use opengapps it will add an extra system folder and app and its just called turbo. The one that comes with the rom is turbo prebuilt but both of them are the same app and if you have both of them in the system then you get settings crash. So its best to just delete turbo prebuilt and use opengapps nano hopefully the aex team fixes this issue:)
[Nexus 7 (2013) Android Development] MikiGry:
Tried to change default CPU grov from ondemand to interactive and I managed to break MP-decisions by doing that

I can confim WI-FI issues. It doesn"t work after some time in deepsleep (it stays connected but nothing loads) (will try to see if logs show anything)

Lockscreen charging indicator (at the bottom) is broken. Shows 0mA of current during charging (voltage seems to be correct though)
[Nexus 7 (2013) Android Development] Ruzar:
Hi and thank you for the great Android P ROM. However I'm stuck with a screen rotation issue.

Problem:

Just after installing the ROM, the rotation worked great, it was fine for a couple of days. After that it stuck, no screen rotation since then :(

What I have tried:

Checking if it's a HW issue. Acccelerometer sensor seems to be fine. (checked with "Sensors Multitool" app)

Cleaning ribbon cable joins

Turning on "parrotmod" from EX manager

Flashing "ElementalX-N7-7.02-Pie-20190319" kernel

Current setup

I followed the installation steps from the first post (magisk and gapps included) and flashed the "flo-deb-followmsi-kernel-pie-20190319" kernel.

How can I make sure that this is a HW issue or not? What can I do to make screen rotation work again?
[Nexus 7 (2013) Android Development] andrei15:
I had a problem with the screen rotation in the very first version this ROM. It was corrected by turning off the screen rotation in the settings and completely turning off the tablet. After turning on the tablet and turning on the rotation in the settings, it began to working.

After the last two ROM updates, this problem is almost gone. (it was only once and was fixed by normal reboot)
[Nexus 7 (2013) Android Development] followmsi:
Thanks for letting me know ..

Need to check mpdecision service .. service restart seems to be required after changing governor.

Remember same/similar problem back on Oreo/Nougat.

Charging indicator needs to be checked too.

For me wifi works fine after deep sleep.
[Nexus 7 (2013) Android Development] followmsi:
Sounds like software issue .. "After that" .. what has happend in between ?

Pls start from scratch .. do factory reset via TWRP.

May take /data backup first.

Good luck !
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.4 - April 2019

AEX Team has merged the April security updates from Google ..

AospExtended-v6.4-flo-20190402-1617-UNOFFICIAL.zip

AospExtended-v6.4-deb-20190402-1741-UNOFFICIAL.zip

Changes:

- Google security updates -> April 2019

- Latest AEX changes for Android Pie

Tested flo version with Magisk 18.1 !

Enjoy :p
[Nexus 7 (2013) Android Development] Booroner:
Going down, to see if I solve the battery drain at rest.

Thanks again for your great work
[Nexus 7 (2013) Android Development] lollyjay:
Thanks so much for all of your hard work
[Nexus 7 (2013) Android Development] JT1510365:
Working great on my flo keep up the great work we appreciate you so much and thank you for bringing us constant security updates:)
[Nexus 7 (2013) Android Development] cpsycrow:
[MENTION=5480152]followmsi[/MENTION]

Furthering my post from a while back about the hardware video+audio decoding. Here are the list of codecs present in nougat. If i am not mistaken it seems to be more than just ffmpeg that was dropped? I assume what we have in pie is correct, and this is just the way it is going forward?

https://imgur.com/a/PwifJkF

EDIT: Here are the codecs listed in a clean install of the latest AEX PIE

https://imgur.com/a/oyJ9tip

Aside from the dropping of ffmpeg it looks like the qcom codecs are missing too?

Thoughts?
[Nexus 7 (2013) Android Development] anivegmin:
I've just installed this ROM to replace my now out of date LineageOS 14.1 and noticed that SELinux is set to permissive.

How compromised am I with this setting? I know it means that I am now more vulnerable, but how vulnerable? For a savvy user who doesn't do anything stupid is it ok for everyday use?
[Nexus 7 (2013) Android Development] reignydeyz:
Slow charging

Has anyone experience slow charging?
[Nexus 7 (2013) Android Development] cpsycrow:
Looks like fast charging isnt enabled by default. install a Kernel tweaker tool like smartpack or kernel auiditor and enable fast charging.
[Nexus 7 (2013) Android Development] anivegmin:
PS. Apart from SELinux being set to permissive the only other thing is the compass not working. Otherwise everything seems fine, maybe not quite as fast as Lineageos 14.1, but more than acceptable.
[Nexus 7 (2013) Android Development] followmsi:
Thanks for reporting ..

Yes .. have realized the missing qcom codecs too.

The OMX.qcom.decoder.avc seems to have an issue .. produces crash on startup.

I have taken it out for testing .. the other codecs are still not "visible".

Not sure about the root problem here ..

All takes time .. I have not much time anymore.

There are still a few issues left on Pie .. but for now it's quite usable.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Of course "enforcing" selinux is "more" secure as permissive selinux .. in general !

Yes - mid/long term it's planned to switch to enforcing mode.

But if I have time left for flo I would like to work on other problems .. selinux has lower priority.

Lineage did disable NEVERALLOWS a few weeks ago .. a first step into "more" security.

Some devices have overwritten this setting to "relax" sepolicies again - we have kept them on !

A little piece of more security .. the rest will come later .. at some point.

Hope you have a better understanding ..
[Nexus 7 (2013) Android Development] AndyCosmos:
Thank you for this amazing room , thanks for your work , I have a small bug with this room , some language don't display and even Gboard and aosp can not show such as some Asian language like Lao , if you have time please have a look into this , anyway very smooth and features pack rom.
[Nexus 7 (2013) Android Development] sam298:
Yes. Battery life is great. Unicode fonts won't work in apps or browser on pie. It was working fine on oreo builds.
[Nexus 7 (2013) Android Development] pss34:
I can not connect my bt keyboard to my flo :( Is it known issue?
[Nexus 7 (2013) Android Development] Booroner:
The last compilation for Deb works great, loads faster, solved the battery drain at rest, at the moment the best compilation for me to date, totally stable and functional, great @ followmsi, thank you very much !!!!
[Nexus 7 (2013) Android Development] prsa01:
I've been able to connect my No-name bt keyboard with all of the versions. I don't use it very much so can't say how solid the connection is but it works fine for the little I use it.
[Nexus 7 (2013) Android Development] pss34:
I've tried rr-0320, all is OK with bt keyboard.
[Nexus 7 (2013) Android Development] v12xke:
[MENTION=5480152]followmsi[/MENTION] If it's not too much trouble could you please whip up another ElementalX based pie kernel? I use the EX kernel manager to enable fast charging and the gestures I have become dependent on. In the meantime your March version is working ok with this AEX April build. Appreciate your work. Thanks. :good:
[Nexus 7 (2013) Android Development] JT1510365:
I don't understand why you think followmsi should update his elementalx kernel to an april version his march version is working perfectly fine. Could you help and explain to me why he should otherwise. I am curious and would like to know:)

Anyways followmsi your pie april aex build is working perfectly fine and i love it and the only bugs are nfc and compass but everything else works just flawlessly:)

Keep up the good work buddy:)
[Nexus 7 (2013) Android Development] v12xke:
I never said "hey you should". It was only a request. And I also said in my post the March kernel is working well with the April build. If you follow flar2 and use his kernels on multiple devices like I do, you understand there are improvements made every month. [MENTION=5480152]followmsi[/MENTION] made it the first time based requests from several users, and he recognized there were advantages. You don't just keep using the same kernel month after month when the kernel dev is very active in making improvements. Sure this is a legacy device, and it was a valuable gift I never expected to see, BUT hey if he's going to keep rolling out AEX builds that have limitations due to our specific N7 hardware and can be overcome with the EX custom kernel, I can ask! It never hurts to ask. At least he knows there is an interest and a following. Peace.
[Nexus 7 (2013) Android Development] followmsi:
Make peace not war !

Of course .. asking questions is still allowed :p

Indeed - there is not much stuff to add into new EX kernel .. actually nothing to add.

The same situation for "my" kernel too.

We use latest 3.4.113 kernel .. the 3.4 kernel is EndOfLife (EOL) - there is no more upstream !

Unlike to 3.18 kernel which still get upstream updates .. e.g. 3.18.138 from last week.

But not for flo/deb devices anymore.

Flar2, Franco and the other kernel guys are taking upstream from kernel.org and from CAF sources.

Tweak the stuff and add features .. etc.

In current flo/deb EX kernel for Pie are all the "features" included.

For this reason it makes no sense to build a new kernel .. the kernel will have new timestamp only - nothing more.

Of course you can always play and do minor changes .. or backport stuff from newer kernels.

But for this work I do not have the time anymore.

Thanks for understanding !
[Nexus 7 (2013) Android Development] cpsycrow:
ex clock

I was wondering.. is it at all possible to have all the CPU/GPU clock speed options unlocked or is there something preventing this?

e.g we cannot set the CPU clock higher than 1512 and the GPU cant be set to 400 or 128 etc
[Nexus 7 (2013) Android Development] tinyturtles:
Hello! I have installed this ROM for the first time a few days ago. I am having an issue where the battery drain is very high (7-10% per hour) both on stock kernel and Elemental. GSam and BBS are reporting the phone is always awake from android system or kernel? I noticed that double tap to wake was working, so I have used kernel adiutor to turn off tap to wake.... Another suggestion in this thread was to turn off Ambient Display, but I do not have an option to do this. Is anyone else having this awake issue? Am I missing something that will fix the problem? Thank you :)
[Nexus 7 (2013) Android Development] followmsi:
Sorry, no idea .. and no time to check.

I see .. we need a dedicated kernel guy for flo/deb .. any volunteers ? :)
[Nexus 7 (2013) Android Development] v12xke:
I did not know this. Thank you for taking the time to explain.
[Nexus 7 (2013) Android Development] dealpapa1:
Apr 15, 2019

TWRP 3.3.0-0 Released

TWRP for flo

Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.

We recommend downloading the latest version of TWRP for your device.

Sometimes, firmware updates for a device break compatibility. If you have not updated the firmware on your device and the latest version of TWRP is not working for you, you may want to try an older version.

Downloading an image for a different device, no matter how similar, usually does not work.

Thank you for choosing TWRP.

TeamWin PGP Public Key

twrp-3.3.0-0-flo.img	8.8M	2019-04-10 14:00:18 EDT
[Nexus 7 (2013) Android Development] sidamos77:
I have the same problem with deep sleep on my deb running LOS 16.0. I thought I'd try AEX but sad to read that you have the same problem. Which ROM are you running now?
[Nexus 7 (2013) Android Development] brewer75:
I have a flo so you may have a different experience than I've had. This ROM is great in all other ways so I'd encourage you to give it a try. Due to the battery drain I've had, I switched to [ROM][AOSP][7.1/8.1/9.0 EXP][flo/deb] Unlegacy Android Project and it has been much better battery-wise. If you decide to try the Unlegacy ROM you may have to search a bit through the last several posts for the download link because it is experimental at this time and wasn't listed in the OP download area the last time I looked.
[Nexus 7 (2013) Android Development] sidamos77:
Thanks! I installed Unlegacy today. Although it does deep sleep well, I still have 1%/hour battery drain. That is less then with LOS 16.0, but I had only 0.25%/hour with LOS 14.1. Maybe it gets better after one day or so.
[Nexus 7 (2013) Android Development] followmsi:
Classic_04-2019_AOSP_9.0.0_r35 -> Easter Edition

One more "classic" version ..

For this ROM I did use "normal" AOSP sources and no CAF sources .. I like it !

Need to check AEX, LOS, RROS and PE sources .. we may switch them all.

But this will take more time ..

flo-Classic_04-2019_AOSP_9.0.0_r35_followmsi.zip

deb-Classic_04-2019_AOSP_9.0.0_r35_followmsi.zip

Changes:

- HW decoding

- Compass

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Happy Easter :p
[Nexus 7 (2013) Android Development] JT1510365:
Why are you so awesome and why do you bring so many cool gifts and roms and such? I know because you just are awesome! You keep amazing us every day so hats off to you buddy:) I can't believe that this tablet still get's development its amazing:)
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.4 - Easter Edition

We have switched to "my" old ASOP sources and blobs now.

Still some changes required .. no more prebuilt kernel .. etc.

The sources have been pushed to Github. ( For the moment AEX only )

The manifest for AEX and for the other ROM has not been updated yet.

I want to make Lineage test build first .. adjusting the other ROM sources in the next time.

AospExtended-v6.4-flo-20190420-1407-UNOFFICIAL.zip

AospExtended-v6.4-deb-20190420-1605-UNOFFICIAL.zip

Changes:

- Switch to AOSP sources

- HW decoding

- Compass

Tested flo version with Magisk 19.0 !

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Happy Easter :p
[Nexus 7 (2013) Android Development] followmsi:
Happy Easter ! :D
[Nexus 7 (2013) Android Development] dealpapa1:
you are beyond god now.
[Nexus 7 (2013) Android Development] dealpapa1:
who is maintaining this PixelExperience_flo-9.0-20190206-0806-UNOFFICIAL.zip 531.6MB?
[Nexus 7 (2013) Android Development] JT1510365:
That build is made by followmsi
[Nexus 7 (2013) Android Development] lollyjay:
Well I'll be damned. Compass is calibrated. :laugh:
[Nexus 7 (2013) Android Development] dealpapa1:
excellent rom