yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Startrek852:
I downloaded v0.6 and I added it as a secondary ROM with MultiROM, and it works really well! The only problem is it gets stuck on the Google logo EVERY time I try to flash SuperSU, doesn't matter when I flash it, it always gets stuck. Any help? I've attached a last_kmsg if anyone wants it. Also, [MENTION=4318865]DevSwift1[/MENTION], can you please upload the updated kernel source?
[Nexus 7 (2013) Original Android Development] tommi_han:
It's my fault. ..I forgot I had data and cache partition in f2fs instead of ext4...Always learning!
[Nexus 7 (2013) Original Android Development] nbehary:
I think I have an idea what your issue is. Though, it should be more widespread. I'll play with it more in the morning. (well, later in the morning after I sleep)

I'll push a commit for the security issue in the kernel shortly, assuming I have permission to, that is easy. (What is there is what 0.6 was built with)

---------- Post added at 01:34 AM ---------- Previous post was at 12:38 AM ----------

The Download link is absolutely v0.6. Are you sure it is flashing correctly? (easiest way to tell is Settings-About Tablet, and then is the Security Patch Level "September 6, 2016"? If it is, you are on V0.6. First that said that. Earlier is V0.5 or before.)

Bigger question is, are you seeing issues that were present in v0.4 still in v0.6? We'd like to know about that.
[Nexus 7 (2013) Original Android Development] :
Hi, can you push the changes made to the kernel binary v0.6 to sources as well. Because, the kernel seems to be pretty outdated.
[Nexus 7 (2013) Original Android Development] doitright:
Seem to have incredibly high idle power consumption. First night I started with about 20% battery, in the morning it had shut down completely. Second night started with 100%, in the morning it had 67% remaining. It should only have dropped by about 0.5%. Battery consumption reported 30% on "Miscellaneous", which it describes as "the difference between computed and actual power use". In other words, unexplained power sucking.

One curious thing, is that it is reporting a perpetual "red line" for cellular network signal. Now this device doesn't even have a cellular radio, so something is obviously wrong there. On devices that DO have a cellular radio, low or no signal equates to massively increased power consumption.
[Nexus 7 (2013) Original Android Development] jisoo:
You should use BetterBatteryStats or something similar to see what is causing the wakelock. I have the same red bar for cellular, and my N7 only drains 0.2% of battery charge per hour while idle.
[Nexus 7 (2013) Original Android Development] ahernandezsanchez:
First of all, thanks to all devs for the effort. I'm running 0,6 and everything is working just fine.

...except for this one thing: for some reason, the list of recent apps that you can see when you click on the multitask button is not complete. In other words: I can only see 'some' of my recent apps, which is very annoying when you're multitasking. I usually find only the last 8-10 recent apps there, although I've been using many more. It looks like some memory problem... I'm not a developer so I just can't really figure out what the problem is. (Needless is to say, this didn't happen with stock Marshmallow)

I have read all 70-something pages of this thread and I couldn't find any of you complaining about this, so.... maybe I screwed something up in development options or something like that? Does anybody knows how to fix that?

thanks!
[Nexus 7 (2013) Original Android Development] afonsov:
Recent apps changes

The recent apps menu, or app overview, or multitasking menu or whatever you want to call it, has also been slightly modified in Android 7.0. Cards are now larger and there's fewer of them, meaning the potentially endless list we had in Marshmallow has been trimmed down to something a little more realistic. The Android system itself can now remove long-unused apps from the list.

This was copied from this article about Nougat

https://is.gd/3UCYfl
[Nexus 7 (2013) Original Android Development] doitright:
There is no wake lock. It CLAIMS to be sleeping.
[Nexus 7 (2013) Original Android Development] ahernandezsanchez:
Wow I did not know that.

It kinda sucks, to be honest. I just checked and there's only 5 (five!) recent apps in the multitasking menu. When I wrote my post I had 10 if I recall correctly. So very strange behaviour.

Thanks for the answer anyway.
[Nexus 7 (2013) Original Android Development] wmuflyer:
My N5X only shows four apps right now, my N7 shows five.
[Nexus 7 (2013) Original Android Development] abler98:
Thank you very much for this rom!

Why not Pixel Launcher?
[Nexus 7 (2013) Original Android Development] lollyjay:
New Nova Launcher beta has most Pixel Launcher functionality
[Nexus 7 (2013) Original Android Development] ReelFiles:
Recent apps works "normal" if you flash Nexus/Pixel launcher
[Nexus 7 (2013) Original Android Development] Broken303:
because is isn't released yet, and it isn't even clear if it is going to be a standard addition to to stock nougat roms. but ofc you are always free to sideload the leaked version yourself
[Nexus 7 (2013) Original Android Development] nbehary:
[MENTION=4318865]DevSwift1[/MENTION] pushed a new kernel binary to the sources 2 days ago when he updated everything else. I'm sure that is what v0.6 was built with. (actually sure, I built it myself after he uploaded those and the kernel has the same build day and time)

[MENTION=4217103]zaclimon[/MENTION] will push the CVE changes to his version of the kernel sources soon.
[Nexus 7 (2013) Original Android Development] doitright:
Just to reply to myself to add some details, in case anybody is paying attention to this possible bug... It appears to be related in some manner to the wifi. Previous two evenings had no wifi connection. Presently, its been running on battery for about 2.5 hours and has not budged from 100% battery power. I've also disabled the "network notification" background scanning, see if that prevents battery suckingness tonight.
[Nexus 7 (2013) Original Android Development] nbehary:
That seems like something we could change. (as an option) I'll look into it.
[Nexus 7 (2013) Original Android Development] Startrek852:
I know that there's an updated kernel binary, I want the updated kernel source so I can make some modifications. Any progress on my problem?
[Nexus 7 (2013) Original Android Development] typongtv:
I'm getting this message when installing or updating apps from play store... Anyone?
[Nexus 7 (2013) Original Android Development] nbehary:
I'm 99% sure what is up there is what the current binary was built with. There just haven't been recent changes to the kernel source. zaclimon mentioned it needing quite a bit of updating a couple days ago. The only imminent change should be that CVE fix which is a very small change to one file. You can work without clashing with that.
[Nexus 7 (2013) Original Android Development] Startrek852:
OK, thanks. Have you made any progress on my SuperSU problem? :)
[Nexus 7 (2013) Original Android Development] nbehary:
A bit. I know it is an sepolicy issue. There's even a commit from Google back in June that is supposed to address the exact message in the log you posted. Digging into that.

---------- Post added at 04:24 PM ---------- Previous post was at 03:34 PM ----------

Report back what you find with all that. I am paying attention to it (though I haven't seen issues). The Cellular thing seems to be it treating GPS as a "cellular" thing. Not sure what is up with that. Going to look into it. It isn't a big deal other than mislabeling maybe. (or maybe G decided that is where it belongs and it is "right")
[Nexus 7 (2013) Original Android Development] nbehary:
I'm a bit lost as to how to tell you how to flash this with TWRP. Been chatting with [MENTION=4544860]osm0sis[/MENTION] about that. (If they could reply here with the answer that would be awesome). Or, if you know, do that.

But, the attached boot.img will work with this ROM, and includes a kernel that should fix the CVE-2016-2059. (Please let me know if not. I don't trust the app [MENTION=6663838]biontx[/MENTION] was using to be completely accurate. I'll upload the exact sources used for this kernel shortly)

Again, thanks to [MENTION=6663838]biontx[/MENTION] for being vigilant about this being truely fixed.

I know you can flash this in fastboot. Reboot to the bootloader (adb reboot bootloader), then,

fastboot flash boot boot.img

Do that after everything else. (so, have v0.6 running as you want). To make sure it worked, you should have a Kernel Version in About that says 'nate@ace #2' on the second line. Something with pawel, you have the kernel included in v0.6.

https://www.androidfilehost.com/?fid=24723757092307297

---------- Post added at 10:40 PM ---------- Previous post was at 10:19 PM ----------

This isn't exact, but close enough. I forked zacilmon's sources, then patched in [MENTION=4166848]DevSwift[/MENTION]'s last 2 commits for 4.9 compilation and the CVE patch. (for some reason I couldn't fork DevSwift's directly, but I built from them). Should be about the same. (The CVE fix isn't affected at all by the changes in the original)

https://github.com/nbehary/android_kernel_google_msm
[Nexus 7 (2013) Original Android Development] osm0sis:
Yeah, TWRP can flash it directly. Press "Install image", choose the boot.img, select "Boot" for the target partition and swipe to confirm flash.
[Nexus 7 (2013) Original Android Development] biontx:
[MENTION=3286382]nbehary[/MENTION]

Great!!! No more security vulnerabilities ... for now :) Thanks again and what a great ROM it is becoming :)

Suggestion: replace boot.img in FLO_AOSP_N_7.0_v0.6.zip with your new one?
[MENTION=4544860]osm0sis[/MENTION]

Indeed you can install boot.img with TWRP

If you are rooted, don't forget to flash SU (SR1-SuperSU-v2.78-SR1-20160915123031.zip) afterwards or your root will gone!
[Nexus 7 (2013) Original Android Development] DevSwift1:
anyone know why here https://github.com/aosp-msm8960/and...s/base/core/res/res/xml/power_profile.xml#L77 we have 3448? our battery capacity is 3950mAh
[Nexus 7 (2013) Original Android Development] mr_rubbish:
I'm devastated, Pokemon Go v0.37 and above don't like the v0.6 build of nougat.
[Nexus 7 (2013) Original Android Development] osm0sis:
Wrong, it doesn't like root/non-stock, and checks via SafetyNet. Google "suhide".
[Nexus 7 (2013) Original Android Development] RazGame:
[MENTION=4318865]DevSwift1[/MENTION], you change bootscreen animation on never build ?
[Nexus 7 (2013) Original Android Development] poondog:
Seems like Google's initial commit had it at 2100

https://github.com/CyanogenMod/andr...mmit/4ffa22bb4af373abff09b8c3423c67235f8e132d

But a second commit, prior to device released changes to a "correct" value

https://github.com/CyanogenMod/andr...mmit/d48dc1e79cc4d2a95d798d6b3c0586734cbf7aba

Dunno why but its google's value, not the community's
[Nexus 7 (2013) Original Android Development] jisoo:
(@DevSwift1, sorry this was supposed to be a reply to your question but I clicked the wrong button. Also, already replied to just above by poondog...)

As you can see from git-blame, that was originally even lower and was adjusted by a Google engineer in July 2013 before the device was released (https://github.com/aosp-msm8960/and...mmit/d48dc1e79cc4d2a95d798d6b3c0586734cbf7aba).

It would be interesting to see if modifying this value makes any difference. Though I suspect (haven't checked the code yet) that it doesn't actually control the battery itself but only the way values are calculated and reported in the UI.
[Nexus 7 (2013) Original Android Development] poondog:
Try increase it to 10000 pls [MENTION=4318865]DevSwift1[/MENTION]

Its also worth noting that above that, the values don't match the comments. Something we are probably missing here, but I'd say its for a good reason
[Nexus 7 (2013) Original Android Development] RazGame:
Google Camera not available via play store.

And some stock ringtones and notification I can see twice when try to choose.
[Nexus 7 (2013) Original Android Development] Debanka:
I have downloaded its apk via Apkmirror app. Some bugs,but otherwise workable
[Nexus 7 (2013) Original Android Development] Cobra11Murderer:
I believe this is a bug in android 7.0 my Nexus 6 does the same from time to time. The apps still are there and will reappear after a while (days even)
[Nexus 7 (2013) Original Android Development] vkk178:
Some system UI tuner settings don't seem to persist .The battery % indicator for example resets back to default after some time .Not sure if I need to do anything extra ?
[Nexus 7 (2013) Original Android Development] Link_of_Hyrule:
Glad to see so much progress already hopefully you can finish it off and get the last parts working! How is stability is there any crashing or does everything pretty much work just as good as Android 6.0.1 other than the sensors and camera?
[Nexus 7 (2013) Original Android Development] typongtv:
Things are working very well here. No crashing yet some apps will struggle waking up on multitasking.
[Nexus 7 (2013) Original Android Development] woeds:
Has anyone managed to get LastPass to work? Every time I start it, a toast message pops up saying 'Android is currently updating a system component, please wait for the update to complete before starting LastPass'
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
Stock Nougat boot animation is same as marshmellow

http://cloud.tapatalk.com/s/57c150b783ffe/bootanimation.zip

Here's the original . Copy it to system/media
[Nexus 7 (2013) Original Android Development] typongtv:
Which brings us to a related question..... Anyone successfully rooted here?
[Nexus 7 (2013) Original Android Development] yiannis1621991:
I can't install gapps (opengapps), it says that i need 7.0 system...

Edit: Rebooted again into recovery and it did the trick!! Excellent built btw!!
[Nexus 7 (2013) Original Android Development] DevSwift1:
first boot to rom then again to recovery and flash gapps
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
I rooted successfully by flashing Supersu stable version from here.

http://xdaforums.com/showthread.php?t=1538053

나의 Nexus 7 의 Tapatalk에서 보냄
[Nexus 7 (2013) Original Android Development] yiannis1621991:
I installed gapps from recovery all good, but when i boot into the rom i dont see them. Which package should i flash? I tried with pico.
[Nexus 7 (2013) Original Android Development] Link_of_Hyrule:
Can anyone post a video showing the ROM off on YouTube?
[Nexus 7 (2013) Original Android Development] Drac13l:
I flashed micro package. I Tried with stock but its too big.
[Nexus 7 (2013) Original Android Development] sillycat98:
It's saying that version 7 is the wrong version after flashing, says it's 6.0.1 sdk23?

Edit:

Never mind, just saw you have to reboot to recovery.
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
https://youtu.be/PKuve2B7ttU

Poor quality...
[Nexus 7 (2013) Original Android Development] Nous16:
Can you take a picture with the front camera?
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
So sad....

Camera error

Can't connect to camera

나의 Nexus 7 의 Tapatalk에서 보냄
[Nexus 7 (2013) Original Android Development] Drac13l:
Also, Freeform Mode works good. Sometimes occurs graphic bug while resizing window.

to unlock via adb shell:

adb shell settings put global enable_freeform_support 1

then reboot.

Probably you dont need root, found this method on reddit (cant post source link, due to limitation lol).

If you want to revert changes just replace 1 to 0.
[Nexus 7 (2013) Original Android Development] Nous16:
Can you kill mediaserver and then take a picture?
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
http://cloud.tapatalk.com/s/57c17a247bad6/2016_08_27_20_30_19.mp4

I couldn't find "mediaserver". Is it renamed??
[Nexus 7 (2013) Original Android Development] Nous16:
Do you have root access?
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
Yes. Is it wrong?
[Nexus 7 (2013) Original Android Development] Ja_som:
It resets when you go to tuner again, it is a bug in Nougat on all devices
[Nexus 7 (2013) Original Android Development] Ranbato:
I get this as well for every app, even after wiping. Not sure what I am doing wrong, but haven't played with gapps before.
[Nexus 7 (2013) Original Android Development] lollyjay:
Some of us had similar experience. To solve it, start over with full wipe and follow these steps:

1. flash v0.6

2. reboot back into RECOVERY (NOT SYSTEM)

3. flash micro gapps

4. flash supersu 2.78 if you want su

5. clear cache and dalvik

6. reboot to system
[Nexus 7 (2013) Original Android Development] osm0sis:
5 is still unnecessary. But otherwise :good:
[Nexus 7 (2013) Original Android Development] nbehary:
As mentioned before, it is a "feature" of Android 7.0. They changed recent tasks to not show everything. I'm not sure exactly how it decides what to show when since it doesn't seem to be just last X. I'll be looking into it.

Specifically, from a quick read through of the Recents loading behavior, it will load at least the last 5 tasks, plus any others that were active in the last 6 hours.

At least that is how it should work. If not, it may be a bug. (though a bug common to all N devices most likely, not this ROM), or there is more in there I haven't seen yet.
[Nexus 7 (2013) Original Android Development] DevSwift1:
I know it but with 3448 now we have for a long time 100% of battery but it isn't true
[Nexus 7 (2013) Original Android Development] biontx:
3448: indeed very strange:

In comparison to the nexus 5: power profile.xml in 6.0.1 MOB31E:

value set in xml:

<item name="battery.capacity">2300</item>

this is exactly the same value as the battery property!!!

nexus 5: 'Non-removable Li-Po 2300 mAh battery'

http://www.gsmarena.com/lg_nexus_5-5705.php

So: perhaps adapt 3448 to 3950: 'Non-removable Li-Ion 3950 mAh battery'?

http://www.gsmarena.com/asus_google_nexus_7_(2013)-5600.php

PS: I am not an engineer ;)
[Nexus 7 (2013) Original Android Development] tommi_han:
Does keyboard gesture swipe work for anyone?
[Nexus 7 (2013) Original Android Development] Masterchief87:
Gesture typing with the stock AOSP Keyboard should work if you are using the correct Open GApps package. If you install the Nano or Micro GApps it should give you the needed swipe libs for gesture typing. The Pico GApps give you just the bare minimum for the Play Store and other Google apps to work. What I do is install the nano GApps and then flash TeamBlackOut's theme ready Google apps and install all other Google apps from the Play Store. If the gesture typing still doesn't work then your other option is to use Google Keyboard which is identical to the AOSP Keyboard but has more features now.
[Nexus 7 (2013) Original Android Development] Ranbato:
Unfortunately, tried a couple times and still no bueno.

I'll play with it more tomorrow.
[Nexus 7 (2013) Original Android Development] mikefnz:
Have you tried the Pico or nano Gapps version?

You can add various Google apps in later if needed.
[Nexus 7 (2013) Original Android Development] nbehary:
I've always thought the tablet stayed at 100% for longer than made sense. If that is the only effect it has, I see no reason not to fix it. (though, if it has always been that, why bother now? It is equal either way.)
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Hello!How you ware able to install version 6 as second with multirom because I get failed to install. As first ROM I have custom marshmallow rom.
[Nexus 7 (2013) Original Android Development] Startrek852:
You need to open the updater-script and remove this:

||
abort("E1001: Failed to update system image.")

Make sure NOT to remove the semicolon. The line should look like this when you're done:

package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Do you wasn't to say the updater-script from multirom zip?because I forgot where I can find updater-script?thank you!
[Nexus 7 (2013) Original Android Development] Startrek852:
I mean the updater-script in META-INF/com/google/android in the ROM zip.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
I can't edit updater-script. I've delete what was need to delete but I was not able to save.I use solid explorer and I get operation failed.I tried with other file manager and the result is same.I don't know why I can't edited.in the past I was able to do that but not now.

---------- Post added at 05:57 AM ---------- Previous post was at 05:48 AM ----------

Sorry I did that in zip file that's why I was getting error.now I know how to doit

---------- Post added at 06:25 AM ---------- Previous post was at 05:57 AM ----------

I've installed the Rom with Multirom but like you I get stuck on Google screen.
[Nexus 7 (2013) Original Android Development] Startrek852:
Delete the ROM and re-add it but DON'T flash SuperSU this time.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
That mean i cant root the rom.Or is other method for root.
[Nexus 7 (2013) Original Android Development] Startrek852:
You can't root the ROM until either a fix comes out or you flash it as primary. No one else has this problem, it seems to only happen with MultiROM.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Thank You for everything.But i think i will wait for a fix and then i will try again.
[Nexus 7 (2013) Original Android Development] Startrek852:
You're welcome.
[Nexus 7 (2013) Original Android Development] nbehary:
So, I haven't actually looked into how Recents works much more since implementing a way to change it from what I think it should be doing is the best way to test what it is doing.

So, I'm writing my proposed "update" which would take this away from being "pure" AOSP, but an addition I'd think makes sense and is close enough.

It is this: Add a "Recents" option to SystemUI Tuner that, for now, just changes the 2 things recents should use in determining what to show: the minimum number of tasks to show no matter what (5), and how much time to consider as the current "Session" (6 Hours). [The latter is just how many hours back to show "everything" for, unless that is less than the minimum to show no matter what....it isn't tied to hours, the default is just that. It is straight time, the option could be more fine tuned. The initial, for me to test, will be minutes since that fits testing it.]

That seems simple enough, unless there is behavior I haven't noticed.

Thoughts on adding that. (I'm writing it anyway. It's a fun little project)
[Nexus 7 (2013) Original Android Development] Startrek852:
That sounds like a good addition.
[Nexus 7 (2013) Original Android Development] ahernandezsanchez:
Sounds great, thank you!
[Nexus 7 (2013) Original Android Development] Ranbato:
I ended up having to do a clean install. Something had gone wrong on my data partition - even going back to stock the UI was crashing.

Once I did that and rebooted before flashing SU everything was happy.