yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Scott:
I had to unzip and manually add it to the ROM. Plus I made some other changes to the boot.img after it compiled as I learn to edit things before compile.

I havent had time but there is a way to add the keymaster to vendor without unzipping. But Every time I google I get a Nexus 4 thread where no one explains and I get this thread we are doing... Kinda sucks!

I hate doing it the way it is... But it works... You can also make it a flashable zip too, just the keymaster files. But that sucks too.

So until I find a way I will be doing it the way I am, compile ota package then add the files and edit the boot.img the way I want.

Hmmm... Not sure on that one. I use AOSP browser and it remains fast and accurate for me.

Maybe it is your GAPPS. Does GPS reboot any other program?

As far as the binaries, the only posted ones are for 36R but these seem fine for now.

There have been no updates by google that I coudl find. Correct me if I am wrong.

Hmmmm.... Not sure. I can try to figure it out... I just hate Chrome mobile so much, lol.

If I get time I will take a look. I may have some ideas. If you look at the asus-flo-blob.txt from google it would "appear" some files are not being installed by the binarie files from google. But I just glazed over it and did not study it hard.

If I get time this week, assuming 4.4 doesnt come out and make this all mute, I will look again.
[Nexus 7 (2013) Android Development] ridobe:
36R? Do you mean 15R? I tried the aosp browser and I get no reboots but no location either.

Agreed on 4.4 but I hate when I can't figure something out. Thank you btw, for the response and the great thread.
[Nexus 7 (2013) Android Development] Scott:
Yes, 15r is what I mean!

IM getting too old for this... lol
[Nexus 7 (2013) Android Development] Scott:
I confirmed the issue with Chrome...

Not sure the deal but here is the debug output...

http://pastebin.com/hr37nR64

Any more senior developers have any input?
[Nexus 7 (2013) Android Development] Lolento:
Is there an expand desktop option in this rom?
[Nexus 7 (2013) Android Development] Scott:
No, as the title states this is a pure AOSP ROM and a place for developers to discuss how to build.

There are no special features, no crazy options, rediculous themes, Nothing. Its pure AOSP.

AOSP is the most basic form of Android.
[Nexus 7 (2013) Android Development] Scott:
I have a feeling this issue is java related. I tried lots of different things with Gapps and found if I dirty flash a stripped down google rom with the EXACT same options it works fine... AND... It prompted on boot if Google Location services were OK to use.

So... Could there be a "issue" with AOSP? Yes, that makes me thing that google is modding the code for the nexus devices to work but gives us the scraps.

So my next step in troubleshooting this (other than googling) would be to reverse and de-compile the Google framework... Then I need to convert the smali code to java and then compare the java...

Sad thing is...

1. I cant remember the name of the tool that can turn smali to Java

2. Even if I did not sure where to start looking...

Any thoughts from any one? Otherwise I might have to see what the google machine can tell me but I like the challenge first...
[Nexus 7 (2013) Android Development] mpmilestogo:
Hi [MENTION=426561]scrosler[/MENTION] and thanks for the confirmation and research. Are you saying that you flash a aosp ROM over the same one that you initially flash? Like I dirty flash this aosp ROM over the top of the same ROM and it works then? Is like to give a few more things a try. I'm judging this does not happen for some reason with certain ROM like carbon or aokp or even cm 10.2 nightly for some reason. Like something changed there compared to the aosp ROMs.

Going to try some stuff tonight.
[Nexus 7 (2013) Android Development] Scott:
No, what I am saying is... I took my Google stock rooted ROM, took out all the files that would make it look like this AOSP ROM, flashed it over this AOSP ROM, and location kicked in.

So my theory is that google edits the code to add the "Google Location Services"

Or one other possibility but was too tired to check... Maybe set up didint ask so it never got granted permission. To test that you woul flash this ROM, then Gapps, then do a factory reset.

But even then... When I did my test method above with a direty flash of google stock ROM it immediately asked about location service on boot.

Does that clarify better?
[Nexus 7 (2013) Android Development] Scott:
And just to futher clarify, google stock ROM is not technically AOSP. Its built from AOSP but modified with apps and what not.

So I think they modify the code as far as the Google location services.

Im sure it could be figured out what needs editing but I like doing it the hard way...

So I want reverse all the Google ROM framework and then turn the smali into java and do a side by side compare to find the differences...

Then implent the differences in the AOSP branch on my machine and rebuild it...
[Nexus 7 (2013) Android Development] A.C.Sanchez:
Yeah i don't get it. I tried 8 or 9 times. ROM worked fine, as soon as i install gapps it breaks. Tried 3 different gapps too.
[Nexus 7 (2013) Android Development] freakzapster:
I FlashedGapps Mentioned In Op

Did U Try Flashing With Multirom ????
[Nexus 7 (2013) Android Development] SHABBYLEA:
If you flash tasadars lpx13d zip for flo, you do not need to flash the latest bootloader.

All you have to do after that is dirty flash latest rom...
[Nexus 7 (2013) Android Development] A.C.Sanchez:
I don't have multi ROM. Never tried it.
[Nexus 7 (2013) Android Development] Scott:
I think you two are in the same boat...

I was having some wierd crap happen. FOr me the status bar would not show up as I noted. As well another guy had constant Gapps failures a couple days ago...

You know what fixed it (both) reflashing the stock preview 3 image!

Once I did that my tablet was good go. Yeah, its like it didint like to be flashed any more.

Here is where you can get the 3rd Dev Preview: http://developer.android.com/preview/index.html

(which is also where I stole the bootloader from)

I know it sounds crazy, especially the status bar but I kid you all not!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Edit: scroll down untill you see lpx13d flo, flash that, then flash rom following intructions in OP.
[Nexus 7 (2013) Android Development] Scott:
Let me know if that works. I had tried a couple insertion points but never got it to take.

And dont put it at the very end... It will error out for you, lol

SORRY!

I am rebuilding Deb now to make sure. But when I was fixing the scripts I may have used the flo script. But to be sure I am rebuilding entire ROM now. Its all cached as it was my last build so it wont take very long (unless I have clear cache then will take a while).
[Nexus 7 (2013) Android Development] Scott:
Look Mom, No GUI!

Sorry I just though that was funny! Get it, look mom, no hands!

Ok Ok... I have had a long week, lol

Ok, maybe its not that funny but when you spend hours and hours recompiling this stuff, you just start to laugh at EVERYTHING!
[Nexus 7 (2013) Android Development] hhairplane:
Thank you for all that you are doing. No need to apologize. It was untested, so you wouldn't have known. Hopefully not to much trouble for you.

Also don't forget to hit thanks in the original post. Scott here has been working super hard, and it takes less than 2 seconds..., but means a lot...
[Nexus 7 (2013) Android Development] bmccoy11:
After struggling to get Google Play Services working on build 2, I finally realized build 4 was up... And pretty much everything works great now! One suggestion, could you change the device name to Nexus 7 instead of AOSP on Flo? As other users have said, it's causing compatibility issues in some apps.
[Nexus 7 (2013) Android Development] freakzapster:
Scott Why My Recovery Is Getting Wired In Every Step Like I Flashed Rom Recovery gone Then Flashed Gapps Again Recovery Gone ???

WHY ???
[Nexus 7 (2013) Android Development] Scott:
A new will be up in about 7 more minutes. It actually took less time to compile than it does to upload. It was still fresh on my HD. I'll post again when its up.

How did you get build 3? I pulled it in less than an hour because GApps was not working, lol

Impossible I tell you!

If you flash build 4, there are lines in the script that delete the stock recovery.

Maybe you should try this, same thing I told those other two guys, revert to preview image 3 then recovery of choice and then flash ROM.

BTW: Are you SURE you are flashing build 4. Its the Build I spent 12 hours on trying to figure out how to stop that from happening.
[Nexus 7 (2013) Android Development] bmccoy11:
Whoops, I meant to say build 2...
[Nexus 7 (2013) Android Development] Scott:
Strange. If you continue to have any issues like that make sure you flashed: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141107-signed.zip

Thats the specific 1 from that thread and it was perfect for me.

Also try the factory restore method I noted above if all else fails.
[Nexus 7 (2013) Android Development] bmccoy11:
I'm not having issues Gapps anymore in build 4, but it looks like Basketbuild's Gapps have some weird signature issues so I can't update them without them failing the signature check...
[Nexus 7 (2013) Android Development] freakzapster:
I'm 100 % sure I've flashed latest build V4

But if I flash factory images I'll loose my data

??????

See one flashed this built only.

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] Scott:
Something is freaky with your device then. I know for a fact the ROM deletes the stock recovery before it even boots up.

IDK man, thats wierd!
[Nexus 7 (2013) Android Development] Scott:
Blah, my ROM will fail Sig check. I turn that off. Its not like it means anything.
[Nexus 7 (2013) Android Development] Scott:
Deb Build for has been reposted!
[Nexus 7 (2013) Android Development] freakzapster:
Any solution you can suggest this is happening with v4 only I tried your previous builds no such problems

Help me out of this

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] Scott:
I honestly do not have a single suggestion.

Build clearly deletes the stock recovery.

When you flash your custom Recovery what do you type exactly?
[Nexus 7 (2013) Android Development] GROGG88:
Yes, it will work if placed after the unzipping of the target files before they are built into the final zip by releasetools.py. If the goal is to remove them rather than prevent them from being created then we must perform it at that point and delete them from /out/target/product/flo/obj/PACKAGING/target_files_intermediates/(package name).

The only issue I run into now is that I need to define the script and point things in the right direction. See my screenshot...
[Nexus 7 (2013) Android Development] Scott:
Thats the error I was getting too when I placed it at the very end. Good luck.

I just secure erased my Linux SSD so I could re-install Ubnutu 14.04. The 14.10 was nothing but crash after crash so I will be out of the build game for the rest of the night but will be on XDA.
[Nexus 7 (2013) Android Development] GROGG88:
OT: Been running Ubuntu-gnome14.04 since it was beta. No problems at all! Haven't bothered with 14.10. Good luck getting things back up. I'm done for the night...
[Nexus 7 (2013) Android Development] freakzapster:
fastboot flash recovery recovery.img

Sent from my Nexus 7
[Nexus 7 (2013) Android Development] supersaayuj:
[MENTION=426561]scrosler[/MENTION] you've made my day! I've no intention of flashing factory images of lollipop after they come out!

PureAOSP is a alot stable and is pre-rooted now with some battery-draining issues(which will get solved later on) :highfive:

Awesome work! :D
[Nexus 7 (2013) Android Development] Scott:
Yes, thats proper. I dont know what to say other than consider a fresh reload of factory images.

Right on!
[Nexus 7 (2013) Android Development] hhairplane:
Deb boots great, everything working great :). Stable, faster than previous build (maybe just my imagination). Only problem is root for some reason not working. Thanks again for your hard work.
[Nexus 7 (2013) Android Development] Scott:
Root works but it depends on the app

For example; I cannot obtain root with ES File Explorer but can with Root Browser by jrummy.

Apps need to be updated.

But glad I got it right this ;)

Faster... Nah, shouldn't be, lol
[Nexus 7 (2013) Android Development] Ambious:
Yup, some apps work with root and some don't.

Guess it's in the hand of the devs now.
[Nexus 7 (2013) Android Development] Scott:
Yeppers!
[Nexus 7 (2013) Android Development] hhairplane:
Strangely though, none of the root apps work, StickMount, AdAway, MultiROM, Solid Explorer. These all worked in Build2 with the modified boot.img by darkobas.

The SuperSU log is also empty. This is similar to how B2 without boot.img.
[Nexus 7 (2013) Android Development] matcho13579:
I got same problem on my brother's Lenovo A7-50 (root not working in some apps), then I tried to install stericson's Busybox Installer from Play and I was able to gain root on these apps(don't know if there's any busybox presented in the ROM and if it's possible to use it on Lollipop)
[Nexus 7 (2013) Android Development] Ambious:
Thank you, that indeed solved root issues for whatever remaining programs didn't work!

Titanium Backup even loads now :D

Perfect solution!
[Nexus 7 (2013) Android Development] Scott:
Yeah, there is no busybox installed.

When you go into the SuperSU what version do you have and it does it warn binaries are not installed?
[Nexus 7 (2013) Android Development] mcflyy_:
Could i juat flash the B4 zip to update it?
[Nexus 7 (2013) Android Development] Scott:
You would have to flash Gapps and SuperSU afterwards.

There is no actual change in the ROM from build 1 to build 4 except HOW the ROM installs.

So if you flash build 4 over build 1 your going to have the EXACT same thing.
[Nexus 7 (2013) Android Development] mcflyy_:
Thanks, and I've noticed I can't get Google+ why is that ?
[Nexus 7 (2013) Android Development] Scott:
Because you didint flash the correct Gapps.

Flash the latest as of 11/7. It includes Google+
[Nexus 7 (2013) Android Development] Ambious:
Use the newer gapps package (here), that solved it for me.
[Nexus 7 (2013) Android Development] Scott:
Same thing I said :p
[Nexus 7 (2013) Android Development] FooFighter312:
Is there anyone else still experiencing the inability to find location via WiFi? I tried with another clean install but it didn't fix it. GPS works great on the other hand
[Nexus 7 (2013) Android Development] Scott:
Just curious... Why would you not want to use GPS?
[Nexus 7 (2013) Android Development] FooFighter312:
I use GPS for specific things, like tracking my exercises when running and riding a bike, and for navigation when flying. But in kitkat I used to be able to pinpoint my location with WiFi to about 30m accuracy which was enough for all apps that use it to get me weather updates and directions. Now, for example, I'm unable to get a weather update automatically when indoors because the device has no clue where it is and can't get a GPS fix unless I go outside or near a window, which takes a bit more time to fix.

I know this sounds like a first world problem but I'm really curious to know why it doesn't work :D
[Nexus 7 (2013) Android Development] Scott:
Ohhh, I see. I never looked at it that way.

I may look into at another day. I am pretty spent right now. Lost time with 4.4.x we had to inject code into AOSP to make it use the Google Location Services. But I thought that was fixed 4.4.4. They could have changed it again though.

I'll take a look when I have time.
[Nexus 7 (2013) Android Development] FooFighter312:
No need to rush, I know you're busy and it's weekend too. Thanks again and keep up the good work! :)
[Nexus 7 (2013) Android Development] lolo696:
I can not make a screenshot . Writes drive is busy. And in the photo gallery is not displayed. DeB version

Послал U9500 с форума xda-developers.com. Работает на appyet.com
[Nexus 7 (2013) Android Development] Scott:
I think I found it...

ON the right is the actual code that gets compiled.

On the left is some included sample code. This is the same code we had to move over to the AOSP base code on prior builds to get ANY location services at all. I thought maybe it was deprecated but maybe note. If you look closely you will see the image on the left has the google location service provider entry.

I will spin it up tomorrow if you can test it then... Not sure if it will be the fix but its worth a shot.

Try this: http://xdaforums.com/showpost.php?p=56533391&postcount=635
[Nexus 7 (2013) Android Development] FooFighter312:
I'll be happy to test when it's ready :) I'm free tomorrow afternoon GMT+1. And seriously now, go get some rest!
[Nexus 7 (2013) Android Development] lolo696:
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------

[/COLOR]

does not work

http://iscr.ru/1415532770/
[Nexus 7 (2013) Android Development] freakzapster:
see properly its done check your file manager
[Nexus 7 (2013) Android Development] lolo696:
flashed firmware 4.4.4 officially . set twrp flashed aosp_deb-5.0.0_r2-11-8-2014.zip superSU. And I was able to take a screenshot and see the pictures in the gallery. maybe it's because of the Bootloader-4.0.4-Flo? until then just set and could not do it
[Nexus 7 (2013) Android Development] THANHVO31:
Since not much change and I have perfect build 2 at the moment so I skip this build.

Anyway, thank you very much for hardworking, @scrosler
[Nexus 7 (2013) Android Development] duryard:
Hi Guys. Come someone explain in a bit more detail please how to "Must have 4.0.4 Boot loader from latest Preview build. If not its attached. Reboot to bootloader and run the batch file that says update bootloader" as I am on 4.01 Boot loader.

TIA
[Nexus 7 (2013) Android Development] LiquidSolstice:
So oddly enough, it seems I didn't have the same luck as everyone else here.

I upgraded my bootloader, verified it, used TWRP 2.8.0.1 to flash, and then flashed GAPPs without leaving recovery, and somehow, I wasn't able to turn on Wifi. Then I discovered that my recovery was overwritten by stock recovery as well. Any ideas why? I flashed the latest Build 4 for the Flo (Yes, I have a Flo and not a Deb).
[Nexus 7 (2013) Android Development] mrw1215:
Going to update my bootloader today after work, but might still hold off on flashing the ROM for now. After I go through the process, how do I check to make sure my device's bootloader updated correctly? Is it listed somewhere in the "About" portion of settings, on the tablet?
[Nexus 7 (2013) Android Development] qubanaso:
Having issues with WiFi as well after flashing build 4
[Nexus 7 (2013) Android Development] Ambious:
Yeah, I somehow missed that. Sorry :o
[Nexus 7 (2013) Android Development] Scott:
Just download the batch file and run it. AS long as you have Nexus drivers installed it will do everything for you automatically.

Sounds like you are using an old version of TWRP. You need be on the latest which is 2.8.1.0.

That batch file that I created will tell you its successful or not. Otherwise you just look down at it in bootloader mode and it will say the version.

CHeck your TWRP version and ensure you have 2.8.1.0

If that is not the issue flash Google preview three release to reset your device back. A few people have needed to do this including myself. I had some odd issues like this and restoring it to factory resolved the problem... Similiar to the guy above.
[Nexus 7 (2013) Android Development] LiquidSolstice:
Thanks, it looks like TWRP was the suspect. Now that I'm on 2.8.1.0, things are going well.

Thanks for giving this to us! :)
[Nexus 7 (2013) Android Development] Megaflop666:
how to use fastboot

---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------

Reboot into bootloader and check version.
[Nexus 7 (2013) Android Development] Scott:
No worries. I forgot to put that in the OP so I will take the hit on that one ;)
[Nexus 7 (2013) Android Development] Zwulf:
Is there a way to update bootloader in Linux or do I really have to buy and install a whole closed-source operating system only for the script to work...? Help is much appreciated... Did not find anything about updating bootloader in Google...
[Nexus 7 (2013) Android Development] Megaflop666:
Open the zip and extract it. Go to that directory and fastboot the bootloader image over. I Did it in Ubuntu.
[Nexus 7 (2013) Android Development] Zwulf:
Thanks a lot!

Sorry, did not see your post before on how to use fastboot... very helpful! :)
[Nexus 7 (2013) Android Development] cudencuden:
okay..bottom line is i did not move the files to internal storage..so...now i can only enter TWRP or bootloader...i cannot enter system...i tried using adb sideload in TWRP but gets "Devices not found"...any help?
[Nexus 7 (2013) Android Development] Scott:
Well, I guess its irrelevant but why did you format System?

Anways... If ADB hits Device not found make sure you ADB drivers are loaded. Thats all that you need to do.

Check device manager and you will probably see something sticking out like "flo" and then just double click it and force the google driver. It may say its not 100% compatible and give you a warning but its fine.

Also, make sure you r USB cable is good if your drivers are there.

Also, do you have a USB to Micro USB converter? I bought one a long time ago and its great for this situation, just connect USB stick to it.
[Nexus 7 (2013) Android Development] cudencuden:
Latest EDIT: I got it working..had to start adb sideload in twrp...scanned for hardware changes in Device manager....executed adb sideload fine in CMD after that...muchas gracias

it was a noob move..i actually did move the files to internal storage..but then unlocked bootloader (thought i had to to update bootloader version, which i did successfully)...in turn..wiping everything....hmm....

about sideload, not sure what i am doing wrong...started sideload in twrp...executed adb sideload xyz.zip...but gets error...the issue is PC is not seeing my nexus 7...(showed no devices when i ran "adb devices"
[Nexus 7 (2013) Android Development] mrw1215:
Okay, pretty sure I got my bootloader is up to date, now. On a side note, I wonder if this will have any positive effects for a random reboot issue I've been experiencing on my Nexus 7 for the last 8-9 months. Not really sure what a "bootloader" is or does, to begin with, and it probably doesn't have any kind of effect on anything that would cause random reboots, but I noticed my bootloader was previously on 3.something. Eh. I'm sure I'll still get my random reboots, I just wish I could properly fix that problem instead of having to live with it, heh...

So, I might give the ROM a try later tonight; has it been set up now so that all I have to do is flash the ROM, gapps, and SuperSU? The only reason I might still hold off is simply because a lot of extra tweaks and goodies haven't been ported over to Lollipop yet, and I'm not sure I can live with a device without said tweaks, heh.
[Nexus 7 (2013) Android Development] Scott:
Oh I see what you did...

Well... Take a screenshot of Device manager and post it. That will tell me what is wrong and why its not seen.
[Nexus 7 (2013) Android Development] cudencuden:
yup..i scanned for hardware changes in device manager (Windows)...actually i had to do it everytime i want adb sideload to see my device.

after scanning for hardware changes (per sideload) ..it works fine...

thanks though!!!
[Nexus 7 (2013) Android Development] Scott:
See there you go. Dont forget to hit thanks on the OP if you have not all ready :good:
[Nexus 7 (2013) Android Development] frischeis:
It is possible to flash the extracted boot.img via flashify app?

Or it is possible to flash the boot.img via terminal?

After flashing the new boot.img run kitkat 4.4.4 normaly?

Or is the new boot.img only for lollipop?

The problem is i dont have a pc at the moment and i want lollipop :)