yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] nbehary:
That isn't the point. You are distributing copyrighted software without a license. It is unfourtuanate since you have put together a really good stable build for the N7'13. The only one.

If you completely don't care, fine. I'll post a clean version later tonight once it is done building and I get home from work (with proper credit and all). Not trying to start a fight or anything, I just can't stand by with this sort of thing as someone who writes software. (I did report this post for copyright. Sorry, but it needed to be)
[Nexus 7 (2013) Original Android Development] ermacwins:
But no 60fps?
[Nexus 7 (2013) Original Android Development] Laskr1999:
60fps same bad like at 6.0
[Nexus 7 (2013) Original Android Development] DevSwift1:
so If I share gapps separately then I didn't share copyrighted software?? Where is difference because I don't see
[Nexus 7 (2013) Original Android Development] nbehary:
Because G, being nice, allows an independent package of just the Gapps to exist. They don't allow others to merge them with AOSP without a license. As I alluded to, way back in '09, CyanogenMod did get a C&D from them for doing so which led to the ways things are done today with keeping them separate.

Here's G's official statment on it from back in '09.

http://android-developers.blogspot.com/2009/09/note-on-google-apps-for-android.html

Not trying to be a nitpicky asshole. Especially working with open source, it is important to respect copyrights, of everything you distribute.
[Nexus 7 (2013) Original Android Development] DevSwift1:
Ok so If I will release ROM package and inside of this package I will put gapps package and updater-script will extract this gapps package then will be ok ?? This is very funny I must say :D

and I love open source so all what is needed to build 7.0 for Nexus 7 2013 is there: https://github.com/aosp-msm8960
[Nexus 7 (2013) Original Android Development] Masterchief87:
MOD EDIT: Removed off-topic quotes.

I guess you think youre going to get some brownie points for trolling someone who points out the fact that the rules aren't being followed? There is a reason why aosp based Roms never include Google apps. Google makes all the GApps and its up to them how they can or can't be distributed so if you don't like it then take it up with Google.
[Nexus 7 (2013) Original Android Development] nbehary:
No, that's distributing them together still. Gapps has to be an entirely different package, distributed separately. That is actually a concession on G's part going back to the beginning (If you read that statement, you could infer that distributing Gapps AT ALL is forbidden). There's no reason they can't stop Gapps packages from being distributed at all. They just have chosen to look the other way as long as they aren't merged.
[Nexus 7 (2013) Original Android Development] morenoa48:
So, you are going to try to get this ROM shut down. Then copy it and release it as your own?

Why don't you spend some of your time trying to solve the remaining issues instead. C'mon man, no one is forcing you to use it. Build your own and use that if you don't agree.
[Nexus 7 (2013) Original Android Development] DevSwift1:
For me this is sick logic, because what is the difference how I share something? I can share something or I can't do this

but I don't want hurt google developers feelings so I will delete download link

and please if you can post link where Google said that I can share it separately
[Nexus 7 (2013) Original Android Development] nbehary:
No. I will release it, free of Gapps, fully crediting [MENTION=4318865]DevSwift1[/MENTION] and pointing out why I'm doing so. I have no desire to maintain a Rom honestly, but a clean version needs to exist.

I do want to help with this, and I'll even contribute my changes back to original (I'm only forking the mainfest and dev tree, the latter just for the most recent commit breaking the build.). This isn't about a pissing contest, it is about doing what is right. If this Rom stops including Google's Apps, I have no need to worry about all that and can just help.
[Nexus 7 (2013) Original Android Development] Masterchief87:
You seem to be missing the point. There are rules. Those rules were not being followed. When people ignore the rules it is bad for the whole community.
[Nexus 7 (2013) Original Android Development] dadymon53:
Trolls!
[Nexus 7 (2013) Original Android Development] morenoa48:
I understand the rules. But why not make the clean Rom as intended, free of GApps. Post that, state the reason, give the credit that's due and let the community chose which to use. I've seen these guys work on this since day one, I think they deserve the consideration of maybe contacting them through other means. Posting throughout the development thread is not the best way to go about it.
[Nexus 7 (2013) Original Android Development] Masterchief87:
It was brought up politely the first time. Then the op decided to say "I DONT CARE" about the rules and that is what lead to where things are now.
[Nexus 7 (2013) Original Android Development] nbehary:
That is basically what I am doing, as [MENTION=6111214]Masterchief87[/MENTION] pointed out, I did start with a simple question thinking the Dev may not realize. The I Don't Care response made it clear that making a clean version (with credit, including the contribs list on the OP) needs to happen. At the same time, I have a strong desire to convince [MENTION=4318865]DevSwift1[/MENTION] to simply remove gapps and distribute THIS rom properly. As I said before, I don't want to maintain a ROM. I want to help with this one (which is why I have a tree setup that I can build it from with Gapps stripped already.)
[Nexus 7 (2013) Original Android Development] DevSwift1:
My statement:

I did not want to offend anyone especially Google developers

I made this rom for fun because I like it, I have my life so I don't have time to argue on XDA [MENTION=3286382]nbehary[/MENTION] said that he will contribute ROM development from now so I hope that he will fix rest of bugs

I think that here should be end of topic and thread should be deleted so I ask moderators to do this
[Nexus 7 (2013) Original Android Development] Masterchief87:
I'm sorry you feel that way. I don't think it was the intent of anyone here to run you off. The rules simply needed to be pointed out so that they would be followed. With that said I'm now withdrawing myself from this discussion. Hopefully development can still go on.
[Nexus 7 (2013) Original Android Development] DevSwift1:
ok but from this http://android-developers.blogspot.com/2009/09/note-on-google-apps-for-android.html I read that I can't share gapps so 70% threads on xda broke this rules. Where I can read that I can share gapps separately??
[Nexus 7 (2013) Original Android Development] ReelFiles:
Dude, you just bake the ROM without Gapps and tell users to download the Gapps package from opengapps, no extra work on your part.
[Nexus 7 (2013) Original Android Development] DevSwift1:
first I need to know if I can do this, so I want see official Google statement
[Nexus 7 (2013) Original Android Development] Tool Belt:
[MENTION=4318865]DevSwift1[/MENTION] Keep on keeping on brother. Please continue your valiant and appreciated work. Just make a note in the OP to have people download the gApps on their own. We all appreciate your time, effort and sharing. A beer is on the way.
[Nexus 7 (2013) Original Android Development] ReelFiles:
That's how everybody else does it on XDA

I've never heard of somebody getting in trouble for including Gapps in an AOSP build on a Nexus device. That guideline is supposed to only apply to custom ROMs. Somebody please correct me if I am wrong about that.
[Nexus 7 (2013) Original Android Development] osm0sis:
We had a similar discussion over on the N5 thread, and it ended with the dev [MENTION=5480061]Santhosh M[/MENTION], the user [MENTION=6100326]itigr[/MENTION] who first presented the idea, myself and [MENTION=3989659]Rapper_skull[/MENTION] from Open GApps collaborating to come up with an overlay that works, so no GApps needed to be included in the ROM.

http://xdaforums.com/google-nexus-5...at-nexus-5-t3446875/post68482257#post68482257

I was on the side of not including GApps, and things were perfectly amicable and it was a mature discussion, and it was a good time, like development should be, so let's get back on track here, since there's already a good solution for this problem. :)

Hopefully [MENTION=3989659]Rapper_skull[/MENTION] can link us the final version of the overlay since I'm not sure where it ended up. :good:
[Nexus 7 (2013) Original Android Development] Rick949:
Well, no, I have to disagree. I had volume control on my Nexus 7 when using the slimport device to play HD video on a TV running stock MM.

Now with the same apps (Netflix, YouTube, Amazon Video), the same slimport, the same Nexus 7, and the same TV, I can't control the volume. The only thing changed is the operating system. The problem happens with all video playback on the slimport, regardless of the app. The fact that the TV won't let me control the volume may be another issue. I will try on another TV later tonight to see what happens.

I don't know of any other video playback that doesn't let you control the audio from the source, so I'll also have to disagree that's its by design.

Does your n4 have a custom ROM as well? I bet if it does, it has the same issue. Just my opinion.
[Nexus 7 (2013) Original Android Development] DevSwift1:
I think that it should be explained because from 2009 we can't share but we can share and vice versa :D
[Nexus 7 (2013) Original Android Development] osm0sis:
As was already explained, on principle GApps shouldn't be distributed as part of a ROM, but to paraphrase the post I linked for you, many smaller ROMs fly under the radar since big G probably won't bring the hammer down on a single enthusiast. That said, I still agree it shouldn't be done, since it does violate terms of use, especially when there are solutions that don't violate those terms.
[Nexus 7 (2013) Original Android Development] TheManii:
My N4 has AOSP 6.0, my brother's has stock 5.1 (not rooted/bootloader locked), and both behave identically to my N7 on AOSP 7.0: the youtube app/media audio on mydp (slimport) is all or nothing. Notifications/non-media volume IS still standard step-wise volume even on mydp out, but that's not important in comparison/not what we're talking about.

The only way to control youtube/media volume at all while inside android, and with a hdmi cable involved is to use full device casting via chromecast. Even directly casting a youtube video (not using full device casting) to my nexus player has the NP outright say to use the tv's own volume control. Android TV also does not have any volume control.

Summary:

N4: stock 5.1 + youtube + mydp: all or nothing

N4: aosp 6.0 + youtube + mydp: all or nothing

N7: aosp 7.0 + youtube + mydp: all or nothing

N7: aosp 7.0 + youtube + full screen casting: step-wise volume

N7: aosp 7.0 + youtube + youtube app casting: all or nothing

NP: stock 7.0 + youtube + hdmi out: all or nothing

IF your media app has step-wise volume in any of the above where i have all or nothing: it may be your app is written incorrectly and using the wrong audio path. There's nothing technically stopping an app from simply not using the media channel and using the general sound/notification channel for volume purposes.
[Nexus 7 (2013) Original Android Development] Rick949:
Ok, let me tell Netflix and Amazon their apps are written incorrectly. :)

All I can tell you is I had volume control, now I don't. Hence the issue.
[Nexus 7 (2013) Original Android Development] TheManii:
With amazon: I wouldn't at all be surprised if they were intentionally doing it differently then what goog has as standard best practices.. Amazon and goog very much do not see eye-to-eye, especially in the realm of video and video out.

Actually, do fireos devices even have a media volume channel? I wouldn't be too surprised if they simply pretended it didn't exist and use general audio for everything.
[Nexus 7 (2013) Original Android Development] Link_of_Hyrule:
[MENTION=4318865]DevSwift1[/MENTION] not a huge deal but apparently Miitomo doesn't work for some reason.
[Nexus 7 (2013) Original Android Development] mjc2251:
Any chance this ROM will be compatible with custom kernels in the future? I'm missing DTW right now.
[Nexus 7 (2013) Original Android Development] goodpanda520:
good job ,tks
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Try glitch 5.21...
[Nexus 7 (2013) Original Android Development] anykill:
I just miss the skip track with volume keys..

Any sugestion?
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=4318865]DevSwift1[/MENTION], found it again, here's the config xml overlay to use: https://gist.github.com/sandymanu/c018f4944d545fd56fa801a1fb12ef23

It goes in device/asus/flo/overlay/frameworks/base/core/res/res/xml/

Fixes all WebViews and you can leave AOSP's in the ROM and let GApps do their thing replacing it.

The r4 tag is out now too with some Nougat fixes from Google. :)
[Nexus 7 (2013) Original Android Development] pmhashir:
You won't get this because officially Google has not allowed sideloading Gapps. But they have not said anything against it also (Surely, the big G knows about it all). You may find this interesting : http://www.slashgear.com/paranoid-android-0-day-gapps-bring-roms-to-legal-gray-area-15301518/
[Nexus 7 (2013) Original Android Development] Az Biker:
***Thread Cleaned***

Please remember when posting/responding to NOT be disrespectful, to NOT be insulting, and to NOT use offensive language as these violate Xda Rules. In the event users are not familiar with XDA Rules, please refer to them HERE. Your cooperation is appreciated.
[Nexus 7 (2013) Original Android Development] vkk178:
For the love of ROMs lets just fix the squabble. Gapps or no gapps this ROM should not stop developing for some silly reason.
[Nexus 7 (2013) Original Android Development] nbehary:
It was never my intention to drive [MENTION=4318865]DevSwift1[/MENTION] off, and for my part I could have handled this a bit better. I apologize for taking it a bit too far.

I want this Rom to succeed, but it was really a nagging question of mine wheter I really wanted to contribute to something when it is being distributed in violation of G's Terms.

[MENTION=4318865]DevSwift1[/MENTION] as has been said a few times, you will not find any official word from G regarding distributing Gapps. They haven't said anything, they just haven't stopped it. You don't even need to distribute them, just provide a link to opengapps and say to get it from there. Linking to them isn't a violation of anything and they are distributing it, not you.

I'd quite honestly not like to take over, my skills are better served helping quash bugs.

Again, I'm sorry for maybe being a bit too harsh in my reaction. (That "I don't Care" thing seemed more negative on your part than I think you meant to.)
[Nexus 7 (2013) Original Android Development] andrewNY:
Thanks DevSwift1!

I'm happy to have Nougat on my Flo, even if Google seems to have abandoned us! I haven't made heavy use of my tablet since upgrading, but for the most part, everything seems to work.

I did get the weird email from Google after signing in for the first time about adding my Nexus 7 (2012) to my account, but I've noticed that happening for a while whenever I flashed a new rom and logged into my account from scratch. I think some Google database must be corrupted and is misidentifying the 2013 edition as a 2012.

The other problem I've noticed seems to be something with location services when I'm indoors. Things like Google Maps seem to work fine regardless, but when I launch Ingress, it is unable to get my location when I'm inside if I don't get a GPS lock. Normally this app is able to locate me by wifi triangulation, so it should be able to work even without a GPS lock.

Thanks again!
[Nexus 7 (2013) Original Android Development] vkk178:
I think one of the reasons google ditched is coz of the system partition size . It can't fit in stock gapps .Here's the space after installing micro gapps ...only 90MB :eek:

/dev/block/mmcblk0p22 827.8M 737.0M 90.7M 89% /system

google should have atleast released an unofficial version .Anyways thx to [MENTION=4318865]DevSwift1[/MENTION] and team we have something
[Nexus 7 (2013) Original Android Development] Rick949:
Well, second TV is the same result, all or no volume on the Nexus 7. I found out that someone had changed the speakers on the first TV I tested. The speakers only had manual volume control, so that explains why I couldn't adjust the volume from the remote!

I guess I can live with just adjusting the volume at the output/TV device. It just was a nice feature to have on the Nexus 7 when I had it, though.

Now I've noticed that my AOSP keyboard doesn't do the swype function, even though I enabled it in the settings. I managed to download the Google keyboard and the swype function works with it.

"The Manii", is that a reference to a people in the Elric of Melniboné series?
[Nexus 7 (2013) Original Android Development] Hackerlacka:
I also have the same issue with my device being identified as the old Nexus 7.
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Same thing happened on the first AOSP M builds. Probably something to do with build.prop
[Nexus 7 (2013) Original Android Development] nbehary:
"fly under the radar" was also part of my concern. This ROM is really popular, and was getting a lot of attention. (very deservedly.) XDA will actually ignore including Gapps until they get a C&D from Google*. I thought it could with the attention. As has been said, exactly how I handled this may make that more likely, which wasn't my intention. I wanted this to follow the rules, both so it wouldn't get shutdown and so I could feel comfortable contributing.

Also, I was a bit optimistic in my "tonight" prediction for releasing a clean version of this ROM. (partly because I got a little overzealous and tried upping to r6, which seems broken for reasons that have nothing to do with flo, and I had made my build tree a bit of a mess.) By tomorrow afternoon, definitely, probably. (and it'll probably include the location fix, since I'm pretty sure I know what that is.....started my questions about contributing)

I'd still rather not maintain it, but I did volunteer. (trying to work that out with devswift privately.)

*- I admittedly wasn't completely sure about that when I reported this post, have found out since that is their policy.
[Nexus 7 (2013) Original Android Development] gaja22:
Hello guys !

First, I wan't to thanks everyone who makes that dream come true.

I didn't read the thread but I want to know if there is a tip for using adaway ?

Thanks !
[Nexus 7 (2013) Original Android Development] ranaxda200:
If device is systemless supersu rooted first flash adaway_systemless_hosts then install apk. Enjoy.
[Nexus 7 (2013) Original Android Development] gaja22:
Thank you buddy for tour advice, works very fine !!!
[Nexus 7 (2013) Original Android Development] zulu99:
To fix volume when you connect slimport or hdmi the dev should add a patch in the firmware:

https://android.googlesource.com/pl...va/com/android/server/audio/AudioService.java

// Devices for which the volume is fixed and VolumePanel slider should be disabled

int mFixedVolumeDevices = AudioSystem.DEVICE_OUT_HDMI |

AudioSystem.DEVICE_OUT_DGTL_DOCK_HEADSET |

AudioSystem.DEVICE_OUT_ANLG_DOCK_HEADSET |

AudioSystem.DEVICE_OUT_HDMI_ARC |

AudioSystem.DEVICE_OUT_SPDIF |

AudioSystem.DEVICE_OUT_AUX_LINE;

int mFullVolumeDevices = 0;

// Devices for which the volume is fixed and VolumePanel slider should be disabled

int mFixedVolumeDevices = AudioSystem.DEVICE_OUT_DGTL_DOCK_HEADSET |

AudioSystem.DEVICE_OUT_ANLG_DOCK_HEADSET |

AudioSystem.DEVICE_OUT_HDMI_ARC |

AudioSystem.DEVICE_OUT_SPDIF |

AudioSystem.DEVICE_OUT_AUX_LINE;

int mFullVolumeDevices = 0;

https://android.googlesource.com/pl...oid-7.0.0_r6/audio/AudioPolicyManagerBase.cpp

// if volume is not 0 (not muted), force media volume to max on digital output

if (stream == AudioSystem::MUSIC &&

index != mStreams[stream].mIndexMin &&

(device == AUDIO_DEVICE_OUT_AUX_DIGITAL ||

device == AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET)) {

return 1.0;

}

// if volume is not 0 (not muted), force media volume to max on digital output

if (stream == AudioSystem::MUSIC &&

index != mStreams[stream].mIndexMin &&

// (device == AUDIO_DEVICE_OUT_AUX_DIGITAL ||

(device == AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET)) {

return 1.0;

}

About Gapps inclusion, do what you want.

We bought the Nexus 7 with Gapps inside and as end users we already have the right to have Gapps on this device. Indirectly we already paid Google to have this apps on our Nexus 7. The price of the device already include the fee that the Manufacturer must pay to Google to have the Google apps inside and for the device certification. And don't forget that this firmware is FREE, the developer don't earn nothing.

Can someone know the price for the device certification and google apps inclusion ? How many money Google get for this, TAX excluded :) ?

Or is a FREE service without TAX ? If is a FREE service, can an independent developer requests the device certification and Gapps inclusion ?

Apart the provocative above questions, a company can not steal everything from the Linux world and then lock users in a walled garden just to protect their economic interests. If is not illegal is immoral.

Thanks to the dev for this good firmware.
[Nexus 7 (2013) Original Android Development] Rapper_skull:
This is the last version of the XML file (found in framework-res): http://pastebin.com/6HtaXL7v

It works with the AOSP WebView (in /system) and with Google WebView and Chrome Stable/Beta/Dev in /system or installed from the Play Store. Obviously at least one of them should be present is /system to avoid crashes.

Just a side note: Chrome stable is using a different signature from Chrome Beta and Dev. It means nothing, but since on the official Google ROM it's not stored anywhere, they could change it at any time, requiring a ROM update to support Chrome (as a WebView provider, not as a standalone app) when not installed in /system.
[Nexus 7 (2013) Original Android Development] osm0sis:
Thanks! At a glance looks the same as the last one [MENTION=5480061]Santhosh M[/MENTION] posted?:
[Nexus 7 (2013) Original Android Development] Rapper_skull:
Yes, I just updated the pastebin with the one provided by [MENTION=5480061]Santhosh M[/MENTION]. Apparently I made some mistakes with XML formatting.
[Nexus 7 (2013) Original Android Development] ReelFiles:
So is this project dead now? The other dude uploaded his "clean" version, but it's too clean, can't install xposed on his :/ Could you just reupload .5 without gapps please?
[Nexus 7 (2013) Original Android Development] AdeTheux:
Yeah a mirror for 0.5 would be nice… anyone?
[Nexus 7 (2013) Original Android Development] Nevermindthelabel:
Xposed not compatible with Nougat yet AFAIK.
[Nexus 7 (2013) Original Android Development] bat_in_the_stacks:
Does this support the LTE razorg model? Are there any quirks in accessing the LTE network? Maybe it was implied, but LTE is not in the list of supported or broken features in the first post.

Thanks for this amazing development.
[Nexus 7 (2013) Original Android Development] LEMONEIDOS:
Then fixing problem about video playback means try to hide that video option?
[Nexus 7 (2013) Original Android Development] DevSwift1:
probably :)
[Nexus 7 (2013) Original Android Development] PradeepMurugan:
I just edited updater-script and installed in my deb. It booted and stuck at starting apps. any idea how to get it to homescreen?
[Nexus 7 (2013) Original Android Development] Nous16:
Can your post the update-script file?

And the logcat?
[Nexus 7 (2013) Original Android Development] DevSwift1:
this is thread for flo, please keep calm and stay tuned. When version for flo will be ready we will make it also for deb