yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Scott:
Alright then...

Build 20131008.010041 up!

Changes

Re-synced repo for 2013/10/08

Fixed Settings -> Security F/C

Changed SU to SuperSU

Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.

Any help with that would be appreciated. Damn trolls, lol!
[Nexus 7 (2013) Android Development] ktkr:
You fixed the security settings fc! Mind sharing how you managed to fix that?
[Nexus 7 (2013) Android Development] vibranze:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links. :confused:

Thanks.

:cowboy:
[Nexus 7 (2013) Android Development] Scott:
Its under the actual "Building for devices" page...

http://source.android.com/source/building-devices.html

Wich leads to...

https://developers.google.com/android/nexus/drivers
[Nexus 7 (2013) Android Development] mpmilestogo:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
[Nexus 7 (2013) Android Development] TheDarkDefender:
hi scott,

could you please share the sources you build from? and specifically how you fixed the Security settings FC?

thanks.
[Nexus 7 (2013) Android Development] Scott:
Your welcome!

Its in the OP. Post 1. I just changed the link. Happy downloading!
[Nexus 7 (2013) Android Development] Scott:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).

Fixing the Settings F/C was creative... had to Google to get the answer, lol

Here is what I found...

CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it :))

Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!

So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.

Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).

Please feel free to share anything you know in this thread.
[Nexus 7 (2013) Android Development] mpmilestogo:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!

Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
[Nexus 7 (2013) Android Development] Scott:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.

If someone else knows then do tell.

However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.

Im sure a fix can be found with enough effort.
[Nexus 7 (2013) Android Development] mpmilestogo:
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place ;).

Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
[Nexus 7 (2013) Android Development] TheDarkDefender:
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?

Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?

I'd be happy to share anything I get to know about this. Been researching about this too. :) Thanks.
[Nexus 7 (2013) Android Development] TML1504:
they do work, at least for me... :)
[Nexus 7 (2013) Android Development] pHyR3:
same here.... how do i fix it? cause i cant boot up the device properly past the setup wizard and usb doesnt seem to be working. how can i transfer a better Gapps package across?
[Nexus 7 (2013) Android Development] Scott:
Yes, they work well for me! Thank you for sharing those!

Just look 1 or 2 posts abov yours and you will see TML1504 was kinda enough to post a link to gApps for 4.4.
[Nexus 7 (2013) Android Development] cabagekiller:
Any idea of the camera issue? Assuming it needs new binaries?
[Nexus 7 (2013) Android Development] Scott:
Yeah, your probably right. Using the binaries from 4.3 R release. They are the latest posted.
[Nexus 7 (2013) Android Development] pHyR3:
yea the issue was more that i couldn't transfer that file to the device since it wouldn't boot properly so i couldnt use usb or airdroid. And i was in the process of try to learn adb but for some reason it couldnt see my device after entering TWRP adb sideload thingy and installing the google devices (which i checked)

but luckily i had a rom file from a week or two ago on my device and i flashed that to boot up and transfer the Gapps.
[Nexus 7 (2013) Android Development] Rouz.:
Could you please at least tell me if it boots on deb, or if flashing it can brick the device? I seem to be the only person on the planet with the lte version
[Nexus 7 (2013) Android Development] Scott:
Yeah, I noted a glitchy thing about that...

You have to enable developer settings, turn off USB debuggin, and then you can turn it back on if so choose, then the MTP / Nexus 7 will show up in your PC.

Wierd?!?!
[Nexus 7 (2013) Android Development] Scott:
This will not flash on Deb because the updater script looks for Flo.

I built a Deb version but I can not test it...

You are 100% on your own if there is an issue, bricked device, etc.

If you want to test it I will upload it but you do so at your own risk.
[Nexus 7 (2013) Android Development] Rouz.:
PM me the link, I'll do the testing. At my own risk
[Nexus 7 (2013) Android Development] adulel08:
Typing on this stock keyboard feels much better for some reason ? Layout is better too.

Omg no root but this 4.4 is worth it! Thanks for making this ROM so quickly op. ???

Should include the new launcher in there
[Nexus 7 (2013) Android Development] Scott:
Technically it is rooted. Open an ADB shell and you will see.

Also, you can try to flash SuperSU and see if that works. I bet they changed root again.
[Nexus 7 (2013) Android Development] ghost02:
Sorry for the noob question guys but what do the binaries do in an android rom? Will there be any performance difference once the 4.4 binaries are released? Downloading this right now though anyway,
[Nexus 7 (2013) Android Development] Scott:
No, unlikley as the binaries are basically "drivers" as in Windows computers needs a driver for a WebCam or a Bluetooth device. So doesn't Android but just differently.
[Nexus 7 (2013) Android Development] ghost02:
Thanks, does one need binaries to interact with the CPU, GPU and screen digitizer?
[Nexus 7 (2013) Android Development] Scott:
I uploaded an untested Deb version. Its is 100% untested. It may cause your device to burst into flames and cause Congress to shut down the government again. This is the risk you take when I dont own a device.

Remember, no one is making you flash anything!

I just put the file there ;)
[Nexus 7 (2013) Android Development] Rouz.:
It stuck on the Google logo, anything I can do to help you identify the issue?
[Nexus 7 (2013) Android Development] Scott:
Oh wait, I didnt include the vendor folder for deb... (thats why it was so much smaller!)

Arghh...

Let me recompile with the vendor folder...

Pulling link...
[Nexus 7 (2013) Android Development] horst0815:
[MENTION=426561]scrosler[/MENTION]: you rock buddy ;)

Thanks for delivering sooooo quickly.
[Nexus 7 (2013) Android Development] GROGG88:
Yep, un-merged changes... Unless you commit your changes it will overwrite them on sync. If you checkout a new branch it will leave that branch on sync as well...

---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------

If all he's doing is building then he doesn't need to touch git. Repo is all that is necessary and git config is not required.
[Nexus 7 (2013) Android Development] Scott:
So my burning question is... How do you use overlays instead of syncing the repo over main source?

My goal is to learn that.

[MENTION=632469]jakdillard[/MENTION] started to explain a LONG time ago in this thread but he just dissapeared :( .
[Nexus 7 (2013) Android Development] sykopompos:
You mean a vendor. A vendor is a basically a device tree that you setup to build on top of the device tree. The actually overlay only works on resources
[Nexus 7 (2013) Android Development] sykopompos:
I'm doing the same thing and it is a pain in the butt to update them which is why I try to limit what repos I replace and find other methods
[Nexus 7 (2013) Android Development] GROGG88:
I am not looking forward to the next version release... I'll be busy for a while!
[Nexus 7 (2013) Android Development] sykopompos:
Same here. I was mad each time google released a new .1 or r
[Nexus 7 (2013) Android Development] GROGG88:
Update is AVAILABLE

**Changelog**

01/07/15

soundrecorder materialized and made visible in launcher

adaway compiled by me from source and included as prebuilt
[Nexus 7 (2013) Android Development] Scott:
NICE! That is my fav android app of all time!

Good job!
[Nexus 7 (2013) Android Development] Scott:
Wow, Ok, so its NOT just me. I thought i was dumb because of the over writes, etc. Thought that there was a better way to do it.

I think you two just solidified what my concern was and how to handle :highfive:
[Nexus 7 (2013) Android Development] sykopompos:
I found a trick for that for the most part if it is small changes that mine don't get interfered with. Make branches to put your features and then do pull request to pull those commits in when you merge up
[Nexus 7 (2013) Android Development] Scott:
You know what... You know a lot more about Git and Repo than I do. Maybe you could do an advanced training session that explains how to do all that.

I only know the basics of git and repo; which I shared in this thread but I think you know a lot more than me. Please continue to share what you know. If you can provide examples for us to learn from that would be great!

-Scott
[Nexus 7 (2013) Android Development] sykopompos:
I'm far from a expert myself, just things I figured out from using it and the annoyance of trying to merge in all my changes each time google pushed a update
[Nexus 7 (2013) Android Development] Scott:
Either way your input is appreciated! :good:
[Nexus 7 (2013) Android Development] sykopompos:
I have a question for you. Your clean ROM, are you using apktool to make changes to the stock google ROM?

If so, I have something I could maybe use your help with
[Nexus 7 (2013) Android Development] GROGG88:
That's about the only way I could think of to help simplify things. Lots of branches and merges.
[Nexus 7 (2013) Android Development] Scott:
Yes, at times I do. Depends on what I need / want changed. I havent used it on Lollipop yet but used it all the time on KK and back. Shoot me a PM.
[Nexus 7 (2013) Android Development] sykopompos:
I don't need it just yet but just need to get some commits into the framework. I'll hit you up about it a little later. still working on making what I'm working with useful and just would need to fix it on stock based Roms and gpe device Roms to make it work properly
[Nexus 7 (2013) Android Development] GROGG88:
If either of you need a copy of apktool working with lollipop let me know...
[Nexus 7 (2013) Android Development] sykopompos:
I just suck with apktool and smali which is why I was looking for someone with better skills then me with it.

It is just what I'm working on right now won't work with stock android builds because there are parts broken that need a couple fixes to work.

That means gpe or other device 5.0 builds out there wouldn't work unless their frameworks are fixed too
[Nexus 7 (2013) Android Development] GROGG88:
Is this your theme engine? Just a guess...
[Nexus 7 (2013) Android Development] sykopompos:
Well it is more then a theme engine but yes, we are working on the built into android theme engine
[Nexus 7 (2013) Android Development] papikev:
Been running build 1/4//15 for only a couple of days now, but I must say it is quite impressive. Battery life is outstanding on stock kernel. I typically run third party kernels, but seeing how this one is performing, I am going to stick with it for awhile. Good stuff [MENTION=3667193]GROGG88[/MENTION]...:good:
[Nexus 7 (2013) Android Development] GROGG88:
Update is AVAILABLE

**Changelog**

01/08/15

audiofx replaces musicfx

apollo music player added
[Nexus 7 (2013) Android Development] APark95:
I am having trouble with the Wi-fi. The device won't search for other wi-fi sources and it just keeps saying "Turning Wi-Fi on...."

Please help.
[Nexus 7 (2013) Android Development] GROGG88:
What did you flash?

What firmware were you running previously?

What bootloader are you on?

Did you make any changes to the packages you flashed?

You see where I'm going with this? I'm hunting a user issue, not a WiFi issue... I know that neither mine or [MENTION=426561]scrosler[/MENTION]'s builds have broken WiFi. Not trying to be a jerk, but we need more info from you in order to get you on the right track. We're here to help.
[Nexus 7 (2013) Android Development] APark95:
I was coming from scott's [ROM][Flo][11/12/14] - Factory Stock Rooted ROM - LRX21P - Android 5.

Do I have to flash the bootloader again even though I was on 4.0.4 previously?

Thank you and sorry for the lack of information.
[Nexus 7 (2013) Android Development] GROGG88:
No. The bootloader is a one time deal. Did you dirty flash over Scott's?
[Nexus 7 (2013) Android Development] APark95:
No I did a complete wipe.
[Nexus 7 (2013) Android Development] GROGG88:
Perform a factory reset, reboot, try WiFi again. If it still fails then download again and install fresh again. Post your results...
[Nexus 7 (2013) Android Development] Scott:
Check the MD5 sum as well.

But when I see that error its a mismatched kernel issue. Like the kernel and the modules are not talking to each other.

Did you install any kernel other than Groggs?
[Nexus 7 (2013) Android Development] GROGG88:
To [MENTION=535343]all[/MENTION]:

The next update is building. I went ahead and took some time to materialize Apollo and materialized the status bar for AudioFX...

**edit**

** builds were postponed, I added xxxhdpi support for launcher icons to eliminate fuzzy upscales **

** attached files updated. builds coming tonight or tomorrow **
​
[Nexus 7 (2013) Android Development] GROGG88:
Update is AVAILABLE

**Changelog**

01/11/15

materialized apollo and audiofx
[Nexus 7 (2013) Android Development] GROGG88:
Silly me. Here I am working on Apollo when I could just build Eleven instead... Ugh.

Machine is building at home. I'll update later.

https://www.androidfilehost.com/?fid=95897840722641437
[Nexus 7 (2013) Android Development] Scott:
Is it any more stable than Apollo? I always had problem with Apollo just down right stopping in the middle of long MP3's.
[Nexus 7 (2013) Android Development] Scott:
Here is another stupid question for you about commits...

Say I want to switch back and forth between your commits and stock AOSP.

Is there any easy way to do that?
[Nexus 7 (2013) Android Development] sykopompos:
Not sure if it will work with repo syncing but there is always git stash for things like that

http://git-scm.com/book/en/v1/Git-Tools-Stashing
[Nexus 7 (2013) Android Development] Scott:
I will certainly take a look! Thanks!
[Nexus 7 (2013) Android Development] Scott:
Meh, will only work for "git" repositories :(
[Nexus 7 (2013) Android Development] sykopompos:
Well yeah, you have a bunch of git repositories right there
[Nexus 7 (2013) Android Development] GROGG88:
Seems to be pretty solid.
[Nexus 7 (2013) Android Development] Scott:
[MENTION=3667193]GROGG88[/MENTION]

I just built with your commits for Shamu and they are very nice!

You did a great job of merging the best of the best!
[Nexus 7 (2013) Android Development] GROGG88:
Cool! I think all you'll be missing is bootanimation and USB storage.
[Nexus 7 (2013) Android Development] GROGG88:
Update is AVAILABLE

**Changelog**

01/12/15

'apollo' replaced with 'eleven' music player

reverted back to musicfx

'screenshot' and 'screen record' icons changed in apm

gapps package updated
[Nexus 7 (2013) Android Development] jakdillard:
Hi Scrosler ...
[Nexus 7 (2013) Android Development] Scott:
Your back!
[Nexus 7 (2013) Android Development] Scott:
[MENTION=3667193]GROGG88[/MENTION], when I screen record on Shamu the file is always 0 bytes. Where and what do I need to edit to get this working? And it wont even attempt to record with mike on.

Every thing else is working great!
[Nexus 7 (2013) Android Development] GROGG88:
That is an excellent question which I do not have the answer to... :confused: No changes were made at the device level to add the function. It is working fine for me on hammerhead and flo (though flo has some edge distortion). I'm afraid you'll need to debug for your device...

vmalloc?? https://github.com/SimpleAOSP-Lolli...mmit/eb357b3eec1fb7e1d0df97ce9a334481862da427
[Nexus 7 (2013) Android Development] Scott:
I shall give it a try!

Edit: Nope
[Nexus 7 (2013) Android Development] Scott:
[MENTION=3667193]GROGG88[/MENTION] Which files do I need to edit to remove screen recorder from Power Menu and settings?

I can take the app out, that was easy but I need to find the strings to remove them from those two portions.
[Nexus 7 (2013) Android Development] GROGG88:
Revert all of these:

https://github.com/grogg/platform_p...mmit/9653d62858af4a3a8dfad47773310ad41c4197a0

https://github.com/grogg/platform_p...mmit/4ae4c635a0886c65b17b377d97804201a51ababb

https://github.com/grogg/platform_frameworks_base/commit/13d29a9c1cb5773d3a1cfc008f69a5778fd83d79

https://github.com/grogg/platform_frameworks_base/commit/31cb4e5a944c155be13a259f6764757ca5d8ccee

https://github.com/grogg/platform_frameworks_base/commit/006071ada1830d88db12c1a199da424552224cff

https://github.com/grogg/platform_frameworks_base/commit/15f8297dc5ebcafdf754916d6a5a393dedf3990e

You can check with [MENTION=2915683]BaNkS[/MENTION] and [MENTION=5334172]Gnome[/MENTION] to see if there was something special to get it working on Shamu...
[Nexus 7 (2013) Android Development] Scott:
I forgot I have Beyond Compare, lol :p
[Nexus 7 (2013) Android Development] GROGG88:
No need.

git revert "hash"
git commit

Ctrl+x

Return
[Nexus 7 (2013) Android Development] nottoosmart:
when ytou say "hash" do you mean the "9653d62858af4a3a8dfad47773310ad41c4197a0" commit number?
[Nexus 7 (2013) Android Development] GROGG88:
Yes sir. That is correct. Just revert them in reverse order of when they were committed.
[Nexus 7 (2013) Android Development] nottoosmart:
did you list them in order there? if not how can i tell which order they were committed in?
[Nexus 7 (2013) Android Development] GROGG88:
Time/date...
[Nexus 7 (2013) Android Development] nottoosmart:
This is what I have as far as data and time as well as hash numbers. Now just do that in reverse order so newest to oldest and i will be good.

9653d62858af4a3a8dfad47773310ad41c4197a0 - Jan 6 6:26PM

15f8297dc5ebcafdf754916d6a5a393dedf3990e - Jan 6 6:35PM

006071ada1830d88db12c1a199da424552224cff - Jan 6 6:36PM

31cb4e5a944c155be13a259f6764757ca5d8ccee - Jan 6 6:40PM

4ae4c635a0886c65b17b377d97804201a51ababb - Jan 6 9:09PM

13d29a9c1cb5773d3a1cfc008f69a5778fd83d79 - Jan 7 12:50PM
[Nexus 7 (2013) Android Development] GROGG88:
That is correct. Reverting in reverse order should avoid any conflicts.
[Nexus 7 (2013) Android Development] nottoosmart:
I think im doing something wrong lol. It yells at me saying that its an invalid object for each of them. My Ubuntu must be screwed lol.
[Nexus 7 (2013) Android Development] GROGG88:
Are you in the proper directory?

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------

cd ~/AOSP/frameworks/base
git revert "hash"
git commit

cd ~/AOSP/packages/apps/Settings
git revert "hash"
git commit
[Nexus 7 (2013) Android Development] nottoosmart:
apparently i was not in the correct folder lol. Still learning.
[Nexus 7 (2013) Android Development] GROGG88:
No problem. I figured that was the case... Just remember that repo is basically a container for multiple git repositories. If you're going to make changes to one of the git repos then you need to navigate to it's directory.
[Nexus 7 (2013) Android Development] Scott:
FYI, Latest Google 5.0.2 build is out

See here for stock rooted ROM by yours truly: [ROM][Flo][1/15/15] - Factory Stock Rooted ROM - LRX22G - Android 5.0.2! Lollipop!
[Nexus 7 (2013) Android Development] andyskelly:
Shame it's not the deb version. Still waiting for an update.
[Nexus 7 (2013) Android Development] sykopompos:
I updated my binaries for flo/deb/manta. It was just qcom binary changes for flo and deb
[Nexus 7 (2013) Android Development] alphahere:
Did a repo sync this morning now I am have the following error when trying to compile for deb. Has the target package changed? Everything else is working fine.

make otapackage

make: *** No rule to make target 'otapackage'. Stop.
[Nexus 7 (2013) Android Development] GROGG88:
I ran into that before. Only way I fixed it was to start clean.
[Nexus 7 (2013) Android Development] nottoosmart:
I saw prior to the change in this thread that you updated a file to give the deb/flo a mor readable version number, do you remember which file you made that change to? Also, I noticed that some of the changes i make wont commit. I updated the apns file under device/sample/etc and I get the following message

Not currently on any branch.

Changes not staged for commit:

modified: apns-full-conf.xml

no changes added to commit
[Nexus 7 (2013) Android Development] GROGG88:
build/core/Makefile : https://github.com/grogg/platform_build/commit/f88e11356be2670e54b9adffc8615a138488a858

You need to add that modified apns-full-conf.xml for staging:

git add "path/to/file"
git commit -am 'commit message'

;)

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

git has pretty useful error messages. If you read the whole error message you will see a portion describing that "git add" can be used.

It looks like you're not on a branch either. I would advise that you checkout a new branch before you start making changes...
[Nexus 7 (2013) Android Development] Scott:
OMG! They finally fixed the browser!

EDIT: Nope they didint
[Nexus 7 (2013) Android Development] Scott:
Updated Pure AOSP ROM with official 5.0.2 Binaries!

Link in the OP!
[Nexus 7 (2013) Android Development] Scott:
Pulled download for now... Re-uploading...

FIXED THE BROWSER SETTINGS!!!!!!!!!!!!!!!!!!!!!!!
[Nexus 7 (2013) Android Development] Scott:
File is back up!​
[Nexus 7 (2013) Android Development] GROGG88:
Update is AVAILABLE

**Changelog**

01/17/15

flo and deb binaries updated

soundrecorder reworked from base