yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Byooxyde:
This rom is perfect, it there are no problems, for Google play games install this: http://www.apkmirror.com/apk/google...ames-3-7-24-3051774-036-android-apk-download/

And do not forget to accept the permissions for Google apps in the settings or it may be some crashes

I searched and for now I have not found problems

Very good job ;) :)
[Nexus 7 (2013) Android Development] nbehary:
I could probably do it as a separate zip. Actually I'm sure I could. I'm playing with the Kernel right now trying to piece together patches for CVE's. After that 8.1 will be an update with just that. I'll build one with that then.
[Nexus 7 (2013) Android Development] ryanexec:
Awesome, thank you; I'll wait to upgrade from 6 to 8 then, and test 8.1 with MultiRom then.
[Nexus 7 (2013) Android Development] yukkio:
Hi all, what kernel do you recommend? Using glitch i feel my nexus a bit slow. Tested intellidemand and intelliactive.

Thanx

Br

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Android Development] ryanexec:
If added as a supplemental download, then you'll need to update it continuously, correct? What issues would there be with having it merged into the embedded kernel?
[Nexus 7 (2013) Android Development] nbehary:
Not continuously. The kernel doesn't change much really. 0.8 is using the exact same kernel I built for version 0.6 of my previous fork over a month ago. (It really should have been updated since then, which is what I am working on now)

As to why not, what that does seems dangerous to include unless really necessary. (Not sure on that completely)
[Nexus 7 (2013) Android Development] ATSPerson:
I have an odd 'bug'. Even though I've disabled screen touch sounds I a still getting them as I type this out. Only turning the sound fully down stops the noise.

Just me?

Details: FLO_AOSP_7.1.0_r4_v.8.0, Micro gapps, rooted.
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
Sadly can't use the new emoji since the new Google Keyboard is only arm 64 until it hits the play store.

Edit: Had anyone been able to get the OK Google training on Google Assistant to stay trained? It you go into the normal settings it just force closes ?
[Nexus 7 (2013) Android Development] nbehary:
I have yet to get it to stay trained. It'll always ask everytime, on both my phone and the N7. (I've read about ways to fix, but never gotten them to work)

I'm also fairly sure that G is trying to stop people using it. The latest Google Search update on my phone killed Assistant entirely and went back to Now. (The N7 hasn't gotten that yet. EDIT: spoke to soon, it did 8m ago, and yep, killed Assistant.)
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
I'm hopeful Google will just let us have it on other devices it a better hack comes along.
[Nexus 7 (2013) Android Development] atifsh:
my device is still trained

no fc's

and as I've already told Google now already working as conversation without any modding.
[Nexus 7 (2013) Android Development] nbehary:
Yay, testing!

I've added two CVE fixes to the kernel, one of them big. Pretty sure there are more that apply, so not ready to release a new build, but for the adventurous, here's a boot.img of the wip.....

This is from a flo build. I know the kernel itself applies to both devices, but not sure about boot.img. It may or may not work on deb.

build.img

It should fix the following:

CVE-2016-5195 - Dirty Cow. (Big one, not in an official security update yet.)

CVE-2016-5340 - Elevation of privilege vulnerability in kernel shared memory driver. (From the October Security update.)

Haven't tested if it does for either yet. I'm only a little dubious about the first.

EDIT: Since it changed, the kernel sources linked on the main page are ahead of this. (and are probably all that goes in 8.1)

After flashing, in About the kernel build date should be today (Oct 27) rather than Sept something, and the user should be nate@clara rather than nate@ace.
[Nexus 7 (2013) Android Development] gangrenius:
Do you have a copy of the 4.08 bootloader somehow I am still on 4.07 someone gave it to me a while back but I accidentally wiped internal storage not long ago.
[Nexus 7 (2013) Android Development] nbehary:
I don't, it doesn't build except when you do a factory image, which I have no reason to be doing. You can just grab the image from the last factory image and flash that:

https://dl.google.com/dl/android/aosp/razor-mob30x-factory-52684dff.zip

If you don't know how, it is just the line in flash-all.(sh|bat) that is using fastboot to flash the bootloader.
[Nexus 7 (2013) Android Development] klaust58:
[MENTION=7298419]gangrenius[/MENTION]: download the last factory image from google and extract the bootloader.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] TheC92:
https://drive.google.com/folderview?id=0ByFQfs_r_dQiXzRscWs2R0tzVFk

04.05 ~ 04.08 flashble zip
[Nexus 7 (2013) Android Development] Startrek852:
Here's a link to the flo 4.08 bootloader: https://www.androidfilehost.com/?fid=457095661767102991 and here's a link to the deb 4.08 bootloader: https://www.androidfilehost.com/?fid=457095661767102992
[Nexus 7 (2013) Android Development] Wannabedeveloper:
after flashing, I'm stuck in Google :( always restarting

How to fix it? I can't go to recovery...
[Nexus 7 (2013) Android Development] gangrenius:
Be more specific after flashing what

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

Recovery is power plus volume down at same time
[Nexus 7 (2013) Android Development] manfio:
Guys anyone know why this happen?

My app shortcuts dont work, open a white shortcut.

Im using last build and opengapps nano pack
[Nexus 7 (2013) Android Development] ranaxda200:
Clean Flash and set Google now launcher as the default.
[Nexus 7 (2013) Android Development] nbehary:
v0.8.1, "boring", but critical security updates.

Flo

Deb

Just a kernel update to include fixes for the applicable patches from the October Security Update (which I really should have done in 0.7) plus Dirty Cow. Specifically, these 5 CVE's: 2016-5195, 2016-5340, 2016-7117, 2016-3903, 2016-3934.

Since it may be confusing, this is just a kernel update, so the build signature didn't change. It'll still show being built on 10-25/26. The kernel build date should be "Fri Oct 28 01:46:00 CDT 2016" (not sure if that gets localized)

I have only actually tested Dirty Cow, mostly because that one needed the most hand adjustments to get in, and there's an easy example exploit due to the coverage it is getting. The rest should really be fine.
[Nexus 7 (2013) Android Development] htb2050:
Thanks man for supporting DEB together with flo. If you take a look at AFH then there are a number of custom roms available for flo updated daily but apparently no deb. I was of the view that a lot of people would have bought deb because of its cellular connectivity but apparently not.
[Nexus 7 (2013) Android Development] nbehary:
No problem. It really isn't difficult to do. At least until something comes along that breaks in Deb but not Flo.
[Nexus 7 (2013) Android Development] bd177:
This fixed Bluetooth Share FC'g. :good:
[Nexus 7 (2013) Android Development] nbehary:
I don't really want to mess with MultiRom to fully test this, so if you (or anyone) could and let me know if it works, that would be awesome. (it flashes and boots correctly and the patch applied cleanly so it should be fine.)

kexec-hardboot.zip

The kernel build date is "Fri October 28 13:45:32 CDT 2016" and it is except for the patch identical to what is in v0.8.1. (It also should work on any build of this, including v0.6 if you want to test with that before flashing the new one.)

Thanks to [MENTION=4544860]osm0sis[/MENTION] for Anykernel2.
[Nexus 7 (2013) Android Development] nbehary:
That's strange. I have no idea why it should. There was nothing near BT stuff patched. But, cool!
[Nexus 7 (2013) Android Development] drewski_1:
not localized for me . . . i think it's just a text string.
[Nexus 7 (2013) Android Development] nuumuun:
[MENTION=3286382]nbehary[/MENTION] can't thank you enough for the continued deb support!

thanks!

it's great how snappy nougat is on such an aged device ?
[Nexus 7 (2013) Android Development] ryanexec:
Awesome, thank you. I'll update and flash when possible, just to test the current the main path most people should be on.
[Nexus 7 (2013) Android Development] SHABBYLEA:
I don't use multirom, so is there any advantage in flashing this for flo?

Many thanks...?
[Nexus 7 (2013) Android Development] nbehary:
No. You probably shouldn't.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Right, just wondered...

Thanks.
[Nexus 7 (2013) Android Development] hheegg:
Happy with this ROM. Only problem, frequently wifi connection gets lost. Dont know the reason. Anybody has an idea how to fix this problem?

And an other thing, got a lot of battery usage from telephone (no need for this) I deleted SYSTEM / PRIV-APP / TELECOM the Telecom.apk and in TELEPHONEY-PROVIDER the TelephonyProvider.apk. That saves a lot of battery life.
[Nexus 7 (2013) Android Development] muschiu35bv:
Hello Guys!I tried to install the rom latest FLO_AOSP_7.1.0_r4-v0.8.1.zip using multirom but i get failed.Before installing do i need to modify updater script?Or how to be able to install with multirom as secondary rom?Thank You!
[Nexus 7 (2013) Android Development] Mysterion1:
How did you get the new navbar?
[Nexus 7 (2013) Android Development] Byooxyde:
Waths is "miscellaneous"? Maybe wifi and?

https://goo.gl/photos/JYmBEjcqg4wdR7Q29
[Nexus 7 (2013) Android Development] Ja_som:
With root:

substratum and N Navbar

W/o root:

Navbar apps

;)
[Nexus 7 (2013) Android Development] Mysterion1:
I have tried this method, but as soon as I apply the navbar in substratum and press the back button the checkbox is gone. After a reboot the navbar still isn't changed. What am I doing wrong? ? Sry but I'm new to substratum...
[Nexus 7 (2013) Android Development] Ja_som:
When you choose which nav bar theme you want, check the checkbox, then scroll down, tap on FAB and Install selected, after a while it asks for reboot, tap on OK ;)
[Nexus 7 (2013) Android Development] Mysterion1:
Thank you very much, I'll try when I'm back home :)
[Nexus 7 (2013) Android Development] nbehary:
It is "Over-counted" which is the system comparing the actual battery use with what it thinks has been. Or trying to. I'm fairly sure it is wrong based on the numbers it is reporting on my device. Not positive though.
[Nexus 7 (2013) Android Development] Byooxyde:
Okey thank
[Nexus 7 (2013) Android Development] Startrek852:
You need to flash this: https://basketbuild.com/filedl/devs...ROM/TWRP_3.0.2-0_multirom_flo_20161018-01.img and this: https://basketbuild.com/filedl/devs...ROM/multirom-20161018-v33b-UNOFFICIAL-flo.zip first.
[Nexus 7 (2013) Android Development] drewski_1:
Have you flashed the kexec patch?

Probably better q for Multirom thread
[Nexus 7 (2013) Android Development] Startrek852:
Dude, flashing the kexec patch will NOT affect flashing whatsoever.
[Nexus 7 (2013) Android Development] Sib64:
[MENTION=3286382]nbehary[/MENTION] and before [MENTION=4318865]DevSwift1[/MENTION]

We can appreciate all the work done and time spent to maintain the Nexus 7 (Flo and Deb) at the highest level with these releases Nougat 7.0 and 7.1

Congrats and well done

All is perfect.

Flash v 0.8.1

Reboot recovery

Flash Micro Gapps

Flash SuperSu (in case you lost your rights root)

Reboot System and all is perfect.

Great stuff!!!
[Nexus 7 (2013) Android Development] atifsh:
my tablets getting hung and restarting is not stopping even on newer build, infact is getting multiple times now in a day.?

going back to 7.0 now until this gets better.
[Nexus 7 (2013) Android Development] menaceinc:
Yes, I did exactly the same. Really working great.
[Nexus 7 (2013) Android Development] ryanexec:
Update:

flashing kexec loses my root, and rooting loses kexec...or multiRom isn't recognizing the kexec in the updated kernel...

device also still reports as Nexus 7 2012.

I've also been having a lot of issues with ADB & FastBoot detection via NRT since flashing .8, kexec & root; the device & drivers don't seem to be loading/displaying properly in Device Manager anymore, but I'm not sweating it yet.

Steps:

wipe > flashed .8 & gapps > reboot > flash kexec > root (NRT) > no kexec seen by multiRom > flash kexec > lost root > root (Chainfire) > no kexec seen by multiRom > flash kexec > lost root.
[Nexus 7 (2013) Android Development] Startrek852:
After you flash the kexec kernel but before you root use TWRP's file manager to check /data for a file named kinda like this: "stock_boot_12f2f4fb9d13c0d05a856db2bb5b90b8fe65caac.img.gz". Delete it, then try rooting again.
[Nexus 7 (2013) Android Development] muschiu35bv:
Hi!I have custom rom and the kernel has kexec patch.today i will try to install again after i download thenew twrp and multirom.
[Nexus 7 (2013) Android Development] ryanexec:
Thanks for the suggestion; I tried this, but multiRom still says that the kernel lacks the kexec patch. It's not a major issue, and I'm sure there are higher priority items to focus on.
[Nexus 7 (2013) Android Development] gangrenius:
If I flashed the security kernel patches he put out for the cve's in boot.img form do I need to flash 0.8.1 ? Or is .8.1 an upgrade to the rom?
[Nexus 7 (2013) Android Development] nbehary:
That was just 2 patches, not the full thing. I had actually meant to do this yesterday once I figured out making a flashable kernel zip for the kexec patch.

Here's a zip for just the kernel in 0.8.1 which is all that is updated from 0.8. You can just flash that. It is good and useful, in a security sense, for any version of this (back to [MENTION=4318865]DevSwift1[/MENTION]'s). Maybe any Nougat Flo or Deb Rom. (It is device agnostic in that way. Works for either, or should)

I'll put it on the main page in a bit too.
[Nexus 7 (2013) Android Development] nbehary:
This isn't a useful comment at all. Complaining and saying "I won't use this until my issue is fixed" does nothing when the majority of users aren't reporting the same problem. (My device has been up for a day and 9 hours since I finished playing with the kexec-hardboot patch, running the latest version.)

Useful is maybe telling a bit about what you are doing when it hangs and restarts, or anything. Not "This sucks, bye till you fix my issue that I won't tell you anything about."
[Nexus 7 (2013) Android Development] atifsh:
hold it buddy, i have said this multiple times before and because of no response was in the impression this ROM being in wip my tablet is getting this issue.

my problem is simple tablet gets non responsive for a minute and than gets rebooted, it's not a sudden random reboot it first gets unresponsive where not even hardware buttons do anything i had to press power quite long the first time, later i get to know it takes time to auto restart.

(now I'll come to your understanding of my post, I've never that rude in my comment, saying i have an issue and I'll test it again when it gets better only implies I'll check couple of builds later.)
[Nexus 7 (2013) Android Development] utfluc:
There are more implications indeed, you aren't being specific nor cooperative. Try to seize the spirit of the whole and report details about your issue, and in that way you would be helping the OP and the rest of us in achieving the objective of having a solid build.
[Nexus 7 (2013) Android Development] atifsh:
exactly! i was not being specific because i was not complaining. anyone can ask me what's going on and I'll reply as i did before.

i have told exact same problem twice before without any response though.
[Nexus 7 (2013) Android Development] htb2050:
Still not getting it or we? Please tell which app you are using when it hangs and grab a logcat.
[Nexus 7 (2013) Android Development] atifsh:
I'll do it later and try to get logcat, it's random and not specific to any application.

got same issue on Facebook, Google+, browser's, games or just browsing the home screens or settings
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
It's trained with the Google Assistant enabled? If so how?
[Nexus 7 (2013) Android Development] atifsh:
no sorry i realized that later you guys talking about assistant.

though Google now working as smart assistant as is.
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
It's not quite the same. Hopefully they find a fix for the current issue.
[Nexus 7 (2013) Android Development] utfluc:
The whole point is to be more objective and less personal when you post. And to do so with a meaningful content, whether if it is for reporting some bug or just for confirming facts. Also, don't rush into conclusions, there's not such thing as "random", try to find a pattern instead.
[Nexus 7 (2013) Android Development] nbehary:
Which, looking back, you did and it got lost. I do actually remember your first report and meaning to ask more.

The point stands though. It was, at the start one report of reboots when no one else was getting them with no other info. If it were me as a user, and I saw that no one was saying "me too", and a bunch of people were saying everything was mostly fine, I'd have looked into it more to try and help the Dev.

I was actually a little short with you and I apologize for that.
[Nexus 7 (2013) Android Development] atifsh:
no problem, what I'll do is try this time with no gapps, because it was doing it on normal screens and settings too so if it didn't do it with no gapps than it will be gapps doing it.

I'm using aroma gapps7.1.

same setup with 7.0 has no such issues.
[Nexus 7 (2013) Android Development] nbehary:
And, if you could do that, it would be awesome! At the end of the day, this is a "development" thread.

Going backwards from what I said above about you being the "only" one reporting it, it is the nature of things that it is likely that you aren't the only experiencing it. I do appreciate you reporting it, and should have asked for more info at the start.
[Nexus 7 (2013) Android Development] nbehary:
Aroma. What would be really useful is what you are installing exactly there. (since anything not in Micro or less, 99% of users aren't installing that way. What you are leaving out, if anything, also matters).

I'd assume sharing your saved config file* would work for me to try the same install. If you could do that, it would be very helpful.

*- I have no idea how to do that. Could figure it out. I use Aroma on my phone.
[Nexus 7 (2013) Android Development] ryanexec:
I understand your point, and I didn't take your posts negatively at all. But, basically, when you state the problems you're having, without any context, it may misrepresent the build to others, and possibly discourage some from trying it out for themselves. The same goes for when people flash, reboot, and then post to say that everything works perfectly because they can reboot and open a webpage.

If you're going to post, just try to include some information that helps others better understand whether your issues are random or consistent, and how likely they may be to experience similar issues, based on the apps/mods/hacks involved. And if you post to say it's great, maybe note what was actually confirmed. I am not trying to discourage anyone from posting, but try to make sure the content of the post is helpful enough to others to be worth the electricity and emissions. Unlike this reply from me, which is pretty much a complete waste.

(--_--)
[Nexus 7 (2013) Android Development] nbehary:
Good point. But let's stop harping on [MENTION=2046044]atifsh[/MENTION]. They have said they are willing to be helpful now, which I welcome.
[Nexus 7 (2013) Android Development] ryanexec:
Understood, concur and no harping; I was just trying to help smooth out the harping since it was a bit tense for a moment, but I didn't see some of those updates and I was late to the party.
[Nexus 7 (2013) Android Development] Extreemator:
Custom kernels from 7.0 work here?
[Nexus 7 (2013) Android Development] atifsh:
http://cloud.tapatalk.com/s/5815d16b007ce/Aroma.zip

---------- Post added at 05:01 PM ---------- Previous post was at 04:54 PM ----------

Any specific logcat program?

I'm not rooted yet, last time was using latest stable superSU.

Thinking not to root until I get a reboot just to rule out superSU.
[Nexus 7 (2013) Android Development] atifsh:
Still enough free space in system.

View attachment 3920402

7.1 doesn't replace camera, rest are all replaced to google.
[Nexus 7 (2013) Android Development] Byooxyde:
Hi, In settings/sounds/other sounds: charging sounds and power on sounds do not work, by activating its changes nothing maybe, it is an incompatibility with a Nexus 7

---------- Post added at 12:30 PM ---------- Previous post was at 12:28 PM ----------

What Gapps you have installed? Aroma?
[Nexus 7 (2013) Android Development] atifsh:
Yes aroma 7.1

---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------

What are you even talking about, better read few post before jumping in.
[Nexus 7 (2013) Android Development] Byooxyde:
I concluded that you do not want help

I signal a bug, it's not for me, nobody talked about it,I signal juste to improve the rom. There is nothing personal. If you want help is personal, I can nothing
[Nexus 7 (2013) Android Development] atifsh:
You concluded wrong and your poking your nose on things without knowing things.

Again i tell you read few previous posts.
[Nexus 7 (2013) Android Development] Byooxyde:
it is to improve the ROM, to help people and that chat is well, why do you blame for anything?

You don't understand is that you reproach utfluc

So good day I will not dirty chat with you
[Nexus 7 (2013) Android Development] atifsh:
I think OP should answer you as i think you have only one intension and I'm ignoring going that way.
[Nexus 7 (2013) Android Development] Extreemator:
Kernels from 7.0 work on 7.1 tested
[Nexus 7 (2013) Android Development] nbehary:
They are providing what I asked them to in case this issue is something I can fix in the Rom.
[Nexus 7 (2013) Android Development] nbehary:
Thanks, I'll look at it later today. Don't worry about logcats for now. Let me play around with that and see if I can reproduce your issue first.
[Nexus 7 (2013) Android Development] jimbob_sf:
A big thank you for this effort! It installed without a hitch and no issues with micro open gapps. There's lots of information in the thread that one has to read for a new rom and I'll list what I did that is working perfectly so far. I don't use Bluetooth on my flo (32gig), only wifi.

1. Most recent TWRP.

2. Complete wipe of the device

3. Flash FLO_AOSP_7.1.0_r4-v0.8.1

4. Reboot to recovery

5. Flash latest micro open gapps for 7.1 (the first time in memory that it installed without a single hiccup)

6. Flash supersu 2.78 SR2

7. Reboot system and it started up without a hitch. I ran through the normal setup and Play restored my apps in what felt like record time.

8. I flashed ElementalX 6.01 (downloaded manually as it's unsupported as of writing this) because I couldn't do without dt2w and no issues.

I'm in mild awe at how I don't notice any issues. We're lucky to have such generous developers to keep this device going. I still feel it's the best Android device I've ever put my hands on and there is zero indication that it's underpowered. Maybe that's why I have four of them (2 for cars, 1 for touring on my 'big' motorcycle, 1 for home)

I haven't touched or tried xposed yet. I'll wait for others to pave the way on that one.
[Nexus 7 (2013) Android Development] atifsh:
OK so far no hungups, no random reboots, will run for couple of days more before root, then I'll root (stable one) just to be sure if that's the problem.
[Nexus 7 (2013) Android Development] nigelhealy:
[MENTION=3286382]nbehary[/MENTION], what is the intention with this ROM? I see it seems to be updating patches which is good for a security, but if it is a fork of an unmaintained ROM then what does that mean?