yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Tool Belt:
Dirty flashed 6 over 5, flashed gApps micro. Google Play Services kept force closing even after giving permissions.

Clean flashed, rebooted to recovery, flashed gApps micro, set up as new device skipping everything, Play Services permissions were already ok, flashed SuperSU, zip for AdAway, "Update" from Tit. Backup and all is well.

Thanks Developer(s)!!
[Nexus 7 (2013) Original Android Development] osm0sis:
It's not a normal assert causing a problem, it's this:

||
abort()

MultiROM needs an update for the way the new AOSP zips have that crossing 2 lines, but until then you can change the || to ; and remove the abort.
[Nexus 7 (2013) Original Android Development] lollyjay:
Dirty flashed v0.6 over v0.5 successfully

1 clear cache and dalvik

2 flash v0.6

3 clear cache and dalvik

4 reboot back into RECOVERY (NOT SYSTEM)

5 flash micro gapps

6 clear cache and dalvik

7 reboot back into RECOVERY (NOT SYSTEM)

8 flash supersu 2.77

9 clear cache and dalvik

10 reboot to system

Worked like a charm I'm happy :)
[Nexus 7 (2013) Original Android Development] Tool Belt:
Cool
[Nexus 7 (2013) Original Android Development] vbaros:
You don't have to clear and reboot to recovery so many times. Nothing is happening between flashing the packages.
[Nexus 7 (2013) Original Android Development] lollyjay:
]

Check out post by Tool Belt:

Many have had similar problems from the beginning. I don't know why but this works for me. :D
[Nexus 7 (2013) Original Android Development] MT2-User:
Yup.

1. flash v0.6

2. reboot back into RECOVERY (NOT SYSTEM)

3. flash micro gapps

4. flash supersu 2.78

5. clear cache and dalvik

6. reboot to system

---------- Post added at 01:07 PM ---------- Previous post was at 01:06 PM ----------

He might forget to reboot to RECOVERY before GApps flashing
[Nexus 7 (2013) Original Android Development] Tool Belt:
I had rebooted to system initially after flashing 6. I then flashed gApps. I did not feel like exploring further "dirty" permutations and went "clean". It is not that big a deal to restore after a wipe.
[Nexus 7 (2013) Original Android Development] osm0sis:
3, 6, 7, and 9 in lollyjay's are unnecessary. ;)

MT2-User's is correct. One reboot recovery is often necessary with block system.dat ROM zips like this one to allow it to mount correctly again. :good:

Only difference with the way I do things is I flash SuperSU before GApps.
[Nexus 7 (2013) Original Android Development] nbehary:
Hey [MENTION=4318865]DevSwift1[/MENTION], can you push the updates used to build this to github? What is there won't build, and isn't fully updated to r6, so isn't complete. I'd like to work on the 1080p problem since I have a reasonable theory as to the issue, but I need to see what you did in this build. (In case you already did it.)

I can work off my fork, but again, you may have fixed or tried what I want to already.
[Nexus 7 (2013) Original Android Development] lollyjay:
Thanks for the clarification.

So reboot to RECOVERY after flashing the rom. Then flash gapps and supersu.
[Nexus 7 (2013) Original Android Development] vbaros:
He actually did a clean flash. That's why it worked for him. Cache is used by Android OS. Recovery doesn't even touch it. When you reboot to recovery you actually just go from recovery -> bootloader -> recovery again. So nothing is happening in between to cache.

For me standard procedure worked. Flash ROM, micro open gapps and Nougat compatible Supersu. All in one go. Clear caches and reboot.
[Nexus 7 (2013) Original Android Development] bd177:
Yes and you might want to get SuperSu 2.78 also. :o
[Nexus 7 (2013) Original Android Development] DevSwift1:
guys what about video recording?? I think it is same like on MM
[Nexus 7 (2013) Original Android Development] DevSwift1:
probably tomorrow I will upload all my changes

but I think now 1080 recording works very good, but I never used it so I am not sure:)
[Nexus 7 (2013) Original Android Development] nbehary:
Thanks.

I see no difference in the video quality, but I also never use it for video, it is dumb to shoot video on a tablet. Rear camera anyway. (it looks pretty bad though. Can't imagine it has always been that bad.)

What did you change? I think the problem goes back to this commit by [MENTION=4217103]zaclimon[/MENTION]:

https://github.com/aosp-msm8960/android_device_asus_flo/commit/6b60c8bcc47aed895c12138b6a2060e958d502b5

I think he was right about it breaking things. My thought is going back to the MM libstagefrighthw, but that didn't seem a lot better, but again, note sure, and it can lock the device up, which makes it hard to test before fixing that. (I've barely messed with it yet though. I didn't expect it to work right away.)
[Nexus 7 (2013) Original Android Development] mikefnz:
Full Screen

Fantastic ROM guys. Well done.

This may be premature given that it is a WIP, but I'm just trying to figure out the best way of getting some apps to run full screen i.e., no status bar or nav bar.

Any suggestions or should I just be patient and wait for version 1.0?

Many thanks
[Nexus 7 (2013) Original Android Development] gangrenius:
I use my tablet for alot of Chromecast ing how does it work on here? Does anyone know if it's smooth and no issues before I switch? Thanks guys
[Nexus 7 (2013) Original Android Development] nbehary:
Apps that should run full screen,ie Play Books in reading mode, do without problems from what I've seen. Is there a specific app that isn't?

---------- Post added at 03:15 PM ---------- Previous post was at 03:08 PM ----------

It seems to work fine. I've had issues casting to my Shield, but I'm pretty sure I did before. (I may have too many "Chromecasts" in my apt)
[Nexus 7 (2013) Original Android Development] DevSwift1:
It is good path, just look into msm8974/android.mk and there you can see build target also for other socs and our soc is there
[Nexus 7 (2013) Original Android Development] kryptikal:
[MENTION=4318865]DevSwift1[/MENTION]

Amazing ROM! Super smooth and a fantastic user experience for being in beta. It runs better than official Marshmallow! You've breathed new life into my aging tablet! Thank you very much for not giving up on this ROM! I very much look forward to watching it develop and mature to perfection.
[Nexus 7 (2013) Original Android Development] EpicPlayer:
Words can't describe how ecstatic I am about the link being back up for me to install it
[Nexus 7 (2013) Original Android Development] ReelFiles:
My thoughts exactly, I grabbed my N7 used off eBay for $90, well worth it now :D
[Nexus 7 (2013) Original Android Development] gangrenius:
My adaway isn't working is anyone's else not working?
[Nexus 7 (2013) Original Android Development] Beachbum2049:
Same, even after flashing the systemless v2 zip.
[Nexus 7 (2013) Original Android Development] klaust58:
My adaway works fine ... after using /data/hosts and making a symlink in /system/etc :)
[Nexus 7 (2013) Original Android Development] mi9ke123:
yeah, I've noticed this too. My battery definitely doesn't feel as solid as it was on 6.0 stock. I notice a lot of idle drain and this cellular network issue. Any update on this?
[Nexus 7 (2013) Original Android Development] gangrenius:
This way said symlink can't be created because of s-off ....
[Nexus 7 (2013) Original Android Development] klaust58:
Boot into recovery, mount system, connect to PC and make the symlink from adb shell.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] gangrenius:
I've never worked from adb but I'm sure I can if I tried . never had to all these years .
[Nexus 7 (2013) Original Android Development] Starphish:
Anyone running Amazon Prime video on this ROM? That's the one app I can't do without. TIA.
[Nexus 7 (2013) Original Android Development] Nevermindthelabel:
Working well here so far, just installed
[Nexus 7 (2013) Original Android Development] klaust58:
Yes, you can.... :cowboy:

First, create the new hosts from adaway as /data/hosts. Then, boot to TWRP, mount /system, connect to PC and make the symlink.
[Nexus 7 (2013) Original Android Development] bd177:
Works fine here. You have to flash the systemless zip after SuperSu 2.78
[Nexus 7 (2013) Original Android Development] gangrenius:
What systemless zip? Can u point me to this.
[Nexus 7 (2013) Original Android Development] bd177:
here u go
[Nexus 7 (2013) Original Android Development] gangrenius:
Yeah so I searched and found it like I should have before I asked . anyway I have adaway installed do I need to uninstall it? Then flash this zip in twrp then reinstall the app? It also says something about having systemless su . I flashed SuperSU 2.78 when I flashed the ROM earlier. Do I need to do anything else?
[Nexus 7 (2013) Original Android Development] nbehary:
Yeah, it is, from that. I guess my question stems from why [MENTION=4217103]zaclimon[/MENTION] suspected it would break things in Qcamera2? That commit in AOSP pulled a lot from CAF from its description. (it doesn't even list all the commits it pulled). I wouldn't be surprised if there's something in there. (going back to MM's libstagefright isn't the answer).

All that said, we need to know if there is still an issue, since neither of us can tell.
[Nexus 7 (2013) Original Android Development] bd177:
I would uninstall adaway then reinstall the latest version (3.12, i think) after you flash Supersu 2.78 (which is systemless) then the adaway zip.
[Nexus 7 (2013) Original Android Development] gangrenius:
I got it working thanks for the help

---------- Post added at 05:31 AM ---------- Previous post was at 05:11 AM ----------

Does anyone have the 4.08 bootloader zip?
[Nexus 7 (2013) Original Android Development] schufti:
@ DevSwift1:

please, please, please: can you bring an updated rom for N7 LTE 2013 (deb) ???

pretty please!
[Nexus 7 (2013) Original Android Development] :
Hi just wanted to ask you something.

Why are your trees made to use the prebuilt kernel and not source? This causes some problems while compiling other roms.
[Nexus 7 (2013) Original Android Development] Link_of_Hyrule:
[MENTION=4166848]DevSwift[/MENTION] perfect now we just need otas with seemless system updates ? I know I'm just dreaming lol. Well keep up the great work!
[Nexus 7 (2013) Original Android Development] nbehary:
I haven't actually see a ROM that doesn't do that. It isn't that hard to inject your own built kernel if need be. (once you have it built, that's "fun"). Did it for my very last build of the clean fork since for some reason the pre-built one in the repo before 0.6 was vulerable to CVE-2016-2059. Just set TARGET_PREBUILT_KERNEL to the path of yours and build.
[Nexus 7 (2013) Original Android Development] :
I did now I have a new problem, I cloned se policy from the op's git compiled and was stuck at splash screen ?
[Nexus 7 (2013) Original Android Development] nbehary:
(The one in the repo at the moment still is the pre-0.6 one since the updates aren't up yet. It is vulnerable to that CVE. It shouldn't be used)
[Nexus 7 (2013) Original Android Development] :
Hi are you on telegram or somewhere I can't hit you up on chat.
[Nexus 7 (2013) Original Android Development] nbehary:
The repo for this isn't build-able at the moment. Pulling from it may not be a good idea. (though, there were no r6 changes that effected the sepolicy tree) But also, just cloning that may not be enough.
[Nexus 7 (2013) Original Android Development] bob8x:
Great ROm, it's super super smooth! ( maybe because I'm from a galaxy s2 plus, while my N5X is repairing )

However with the version 0.6 seems like that is having difficulties to connect to wi-fi 5ghz, it sees them but the network remains "Saved" as it does not connect/fails instantly.

Is something new/recognized/only me ? ( Right now I can't runs tests as I'm at work with no 5ghz hotspot)
[Nexus 7 (2013) Original Android Development] :
So the devs haven't open sourced everything?
[Nexus 7 (2013) Original Android Development] nbehary:
They have always been slow in updating things, and/or not understanding what to update. I think they know now, but just haven't pushed the latest. (said they will today or tomorrow.)

There's a fully buildable r6 version of roughly it here: (minus the things they added that weren't the r6 update)

https://github.com/nbehary/manifest

I'm not updating that anymore though. It only exists because of the issue here with gapps that has been resolved.

The pre-built kernel in that tree is also the vulnerable one. Build the kernel and include it!

(I'm not sure I forked the kernel sources. The ones on the OP's repo are fine)
[Nexus 7 (2013) Original Android Development] bd177:
I had that problem too. I went in to Settings->Backup & reset->Network settings reset and then did the reset then rebooted.

5gz works now.
[Nexus 7 (2013) Original Android Development] biontx:
Running v0.6: the following security vulnerability CVE-2016-2059

Running v0.6 : great work!!!

However: still the following security vulnerability CVE-2016-2059

https://www.codeaurora.org/projects/security-advisories/linux-ipc-router-binding-any-port-control-port-cve-2016-2059

>>

fix:

https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=9e8bdd63f7011dff5523ea435433834b3702398d

>>

Could this be fixed please?
[Nexus 7 (2013) Original Android Development] nbehary:
It isn't though. At least the program you used to report this on my fork shows it isn't, and this build is using a kernel, built on the same date as the ROM itself, that I'd assume [MENTION=4318865]DevSwift1[/MENTION] compiled from the sources in his repo (they, like the stock N7 kernel, do not include the ipc_router code that addresses.)

---------- Post added at 04:59 AM ---------- Previous post was at 04:56 AM ----------

Did you flash this one and not my 0.6 which was vulnerable by mistake?
[Nexus 7 (2013) Original Android Development] manxexile:
Adaway

Good man, I thank you.
[Nexus 7 (2013) Original Android Development] DevSwift1:
ok, all my changes uploaded to aosp-msm8960 organisation

[MENTION=3286382]nbehary[/MENTION] I can add you to organisation if you want
[Nexus 7 (2013) Original Android Development] zaclimon:
Just so you know the kernel doesn't have really everything patched. Only the memory allocator and ext4 part. The audio subsystem among others still need to be patched.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] biontx:
No, I did not flash yours :)

I flashed the right one :)

https://threatpost.com/google-patches-quadrooter-vulnerabilities-in-android/120374/

---------- Post added at 02:25 PM ---------- Previous post was at 01:49 PM ----------

@DevSwift1
[MENTION=3286382]nbehary[/MENTION]

//CODE BASED ON

https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=9e8bdd63f7011dff5523ea435433834b3702398d

TWO FILES:

1. android_kernel_lge_geehrc-n\android_kernel_lge_geehrc-n\arch\arm\mach-msm\ipc_router.c

2. android_kernel_google_msm-flo-nougat\android_kernel_google_msm-flo-nougat\arch\arm\mach-msm\ipc_router.c

Fix?

//...

mutex_unlock(&port_ptr->port_rx_q_lock);

return rc;

}

//TO CHANGE ???

int msm_ipc_router_bind_control_port(struct msm_ipc_port *port_ptr)

{

if (!port_ptr)

return -EINVAL;

//------------

//CHANGE TO???

int msm_ipc_router_bind_control_port(struct msm_ipc_port *port_ptr)

{

if (unlikely(!port_ptr || port_ptr->type != CLIENT_PORT))

return -EINVAL;

down_write(&local_ports_lock_lhc2);

//------------

//..

mutex_lock(&local_ports_lock);

list_del(&port_ptr->list);
[Nexus 7 (2013) Original Android Development] DevSwift1:
which app you used to check vulnerables? and please post commits to pastebin or at least code this
[Nexus 7 (2013) Original Android Development] biontx:
First things first ... I will buy you a Belgian beer :)

Now:

- Flashed all as it should be to install your latest v0.6 version (gapps micro, rooted: SU 2.78)

- Tested with 'QuadRooter Scanner':

https://play.google.com/store/apps/details?id=com.checkpoint.quadrooter

- I ran the same app on my hammerhead for Nexus 5: 6.0.1 (MOB30Y) : vulnerability CVE-2016-2059 detected ... after patching to 6.0.1 (MOB31E): vulnerability test with the same app was gone!

Note: same apps and settings on my nexus 7 as on my nexus 5 (also rooted)!

- I did some digging in your code and the above was a quick result and suggestion after

>>

reading:

https://www.codeaurora.org/projects/security-advisories/linux-ipc-router-binding-any-port-control-port-cve-2016-2059

>>

apply:

https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=9e8bdd63f7011dff5523ea435433834b3702398d

>>

I guess 'ipc_router_core.c' mentioned in the article is the same as 'ipc_router.c' in your kernel after a quick comparison...

for example an example of an old 'ipc_router_core.c':

https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release/net/ipc_router/ipc_router_core.c

//--

Keep up the good work!
[Nexus 7 (2013) Original Android Development] amppcguru:
http://xdaforums.com/showthread.php?t=

Bootloader from badboys stock mm
[Nexus 7 (2013) Original Android Development] javielillo:
Thanks so much guys for this development, as soon I have time I would like install it because I love the idea of split window (and report any bug if necessary).

How much "stock" is this Rom? I mean, I'm interested if there is native NTFS support when I plug any USB drive without tricks like apps that allow it.
[Nexus 7 (2013) Original Android Development] doitright:
NTFS is NOT a native filesystem on Linux though.
[Nexus 7 (2013) Original Android Development] alfick3:
Exactly! It's Windows NT file system (thus NTFS).
[Nexus 7 (2013) Original Android Development] t0mm13b:
You can always compile in NTFS kernel support as a kernel module or built in.
[Nexus 7 (2013) Original Android Development] alfick3:
Why'd you quote me? I'm not the one asking.
[Nexus 7 (2013) Original Android Development] javielillo:
Oh my... isn't hard to understand that I asked if the kernel used for this stock rom has those changes to support natively that MS fylesystem without replacing the kernel by one custom with those compiled modules or using 3º party apps to do the same... :rolleyes:

Simply saying that will work (internally, not the GUI) exactly like the original Google roms is sufficient to imagine the limitations.
[Nexus 7 (2013) Original Android Development] nbehary:
Odd. That program doesn't find it on mine with this or the one I compiled the other day, but did on the previous pre-built kernel.

But, you are right it is in there. I missed it because that isn't the path where that is in AOSP (I was looking at their commit to patch it).

So, even my "fixed" one is still vulnerable.

Again, good catch.

---------- Post added at 07:58 PM ---------- Previous post was at 07:53 PM ----------

Sure.

---------- Post added at 08:29 PM ---------- Previous post was at 07:58 PM ----------

@DevSwift1 and thanks for pulling out my updates for r6. I'd have seriously questioned your ability as a developer if you hadn't. (really.)

Also thanks for keeping the history intact. (not that I'd have cared. I recommited G's commits, nothing else. It wasn't real original work or anything)
[Nexus 7 (2013) Original Android Development] nbehary:
You were agreeing with the "answer" of it not being a native Linux filesystem, or you wrote it that way. (TBH, your comment was a pedantic, unnecessary addition.)

NTFS over USB is totally something that can be supported. I'd classify that as something that is useful while still keeping this basically AOSP. (I'd work on it, despite never needing it.)
[Nexus 7 (2013) Original Android Development] bob8x:
Thanks, worked for me too!, should be added to main post?
[Nexus 7 (2013) Original Android Development] biontx:
So it will be fixed in a future version. We should buy you another beer :)
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Hi Guys!I just want to know how much battery life you can get with this rom.Because me i just got about 3hours just watching movies at 100% brightness.I want to know if my battery is the problem or i need to replace it?I dont have any complain about this rom.I love this rom is very smoothThank You!
[Nexus 7 (2013) Original Android Development] vkk178:
Standby drain was amazing in 0.5 build.Yet to properly assess the usage drain
[Nexus 7 (2013) Original Android Development] typongtv:
I concur regarding battery life. Doze worked very well on v0.5... Not so well yet not that bad on v0.6.
[Nexus 7 (2013) Original Android Development] MadHacker:
I'm seeing fast battery drain with video playback too on all the versions I've tried (4,5, and 6). After 30 min, the tablet also gets very warm. Never seen that on JB,KK,LP, or MM. It seems to really struggle streaming 1080p (like buffering), same video downloaded plays fine, other than high battery usage and getting warm. I'm thinking this is why Google not doing it and/or the lack of support from Qualcomm for the Snapdragon 800/801. Other than this issue, this is the best, fastest version of Android to ever run on my N7, witch I've always kept Stock android, why not.

THANKS AGAIN dev's, I really hope you all can solve this issue.

Going to flash back what looks like the final version on Marshmallow MOB30X, no September security updates for razor/flo :(

EDIT: August 5, 2016 security update is last official version of MM.
[Nexus 7 (2013) Original Android Development] buhohitr:
Where can I download .5 version? Thanks
[Nexus 7 (2013) Original Android Development] doitright:
Heat, power consumption, and glitchy playback? That tends to point towards software video decoding. I wonder if there is something missing for the video processor?
[Nexus 7 (2013) Original Android Development] krapfa:
Hi,

could you help with an issue. I am on 0.1 and I tried to update to 0.6 by flashing the new Version and gapps afterwards (and deleted cache). But after rebooting I had to set permissions again for play services and also Google Account was gone. When i tried adding it again it couldnt connect to the Google Servers to finalize it...

What have i done wrong?
[Nexus 7 (2013) Original Android Development] lollyjay:
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] sebanc:
Big thanks to everyone involved in this.

The below commit from zaclimon seems to have fixed the hardware encoder :

github.com/aosp-msm8960/android_hardware_qcom_media/commit/e3671e5e1e917583a11761c3e99d94a8e7f13194

Though for it to work I changed the msm_vidc permissions to camera in ueventd.flo.rc :

/dev/msm_vidc_dec 0660 system camera

/dev/msm_vidc_dec_sec 0660 system camera

/dev/msm_vidc_enc 0660 system camera

Hope it is useful.
[Nexus 7 (2013) Original Android Development] krapfa:
Worx this time! Thank you!
[Nexus 7 (2013) Original Android Development] DevSwift1:
github.com/aosp-msm8960/android_hardware_qcom_media/commit/e3671e5e1e917583a11761c3e99d94a8e7f13194 this is already included

just make pull request and we will see if it is good patch
[Nexus 7 (2013) Original Android Development] praxis22:
Took me ages to get the USB driver to see TWRP, but after that smooth sailing. Quite a performace boost in games compared to Marshallow, so far. A quick test of YouTube, and it's slick and fast, especially screen autorotation. Well worth the effort.
[Nexus 7 (2013) Original Android Development] brenty108:
The link is only giving me 0.4. the download days 0.6 but when it does it's 0.4 with settings FC and stuff. Why?
[Nexus 7 (2013) Original Android Development] tommi_han:
I tried to do the install as directed but I'm stuck on the android screen for 15min? How long does it take to first boot?
[Nexus 7 (2013) Original Android Development] nbehary:
It shouldn't take that long. First boot should only be a bit longer than normal. (1-2 min)