yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] eX1337:
I cant even flash gapps because the updater binary only accepts Android 4.4.X

Some1 knows how to fix it?
[Nexus 7 (2013) Android Development] eric00716:
delete
[Nexus 7 (2013) Android Development] skiwong20:
Here is a the PA pico modular edited to work with Lollipop...it will say 4.4.4 in the install..but don't worry it will work for now

GAPPS
[Nexus 7 (2013) Android Development] newellj79:
Play store to?

---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------

Playstore?
[Nexus 7 (2013) Android Development] 0.0:
Deleted. Posted in q&a thread
[Nexus 7 (2013) Android Development] eric00716:
2.16 was working fine so I don't see why not.
[Nexus 7 (2013) Android Development] sudoeste:
Why not build with the preview binaries that are available on the developer preview page?
[Nexus 7 (2013) Android Development] Scott:
Because I did not know they were available until just a little while ago.

Might give it a another spin.
[Nexus 7 (2013) Android Development] EvanA:
Don't bother, you'll get the same results. GPS doesn't work.

PA Gapps are a work in progress. We're getting really close to an initial minimal package (play store and gms). NO TIMETABLE SO DON'T ASK
[Nexus 7 (2013) Android Development] Scott:
|

|

|

\/

Correct!
[Nexus 7 (2013) Android Development] Scott:
Well then... That answers that question.
[Nexus 7 (2013) Android Development] sudoeste:
The comment was meant as a suggestion, sorry if it sounded like something else!

I'm curious to if the updated binaries support the camera2 api or not (the famous L camera app from pkmx)
[Nexus 7 (2013) Android Development] skiwong20:
pico modular is just really the playstore

i built my own build with the LP preview bianaries and work great
[Nexus 7 (2013) Android Development] Scott:
I'm testing now.

Question?

Were you able to get a flashable zip format?

EDIT: And did you try GPS?
[Nexus 7 (2013) Android Development] Megaflop666:
If you make a flashable I'll flash it on my nexus and try it out for ya chief! In getting tired of my Dev preview. Lol
[Nexus 7 (2013) Android Development] skiwong20:
i couldn't get a flashable zip from the build enviroment..it didn't flash ..the update script was pretty much blank..but GPS does work great
[Nexus 7 (2013) Android Development] Scott:
Thats the thing... I cant get a flashable zip.

Thanks for the info. I am almost done my rebuild not and will test it.
[Nexus 7 (2013) Android Development] Megaflop666:
You'll get it, you're awesome at what you do.
[Nexus 7 (2013) Android Development] Scott:
This is the updater script that pops out...

HEre is the OTA package when you build it...

Something has changed and I am not sure how.
[Nexus 7 (2013) Android Development] skiwong20:
like i was saying to my team members..it looks like for stock recovery to flash over last 4.4.4
[Nexus 7 (2013) Android Development] SHABBYLEA:
Just out of curiosity, what is the problem with creating a zip?

TIA.
[Nexus 7 (2013) Android Development] Scott:
Thats what I was thinking too.

Usually OTApackage will give a full flashable zip.

I wonder if recoveries will need to be updates?
[Nexus 7 (2013) Android Development] Scott:
It boot loops when you do.

The otapackage builds are funky. See above.

Everything has changed a bit.
[Nexus 7 (2013) Android Development] SHABBYLEA:
I'm sitting here with a dev mate, and he says it could be bootloader problem. Not so sure myself...
[Nexus 7 (2013) Android Development] Scott:
Very possible. Hard to say until we get a full factory image which seems to be lagging.
[Nexus 7 (2013) Android Development] skiwong20:
nope shouldnt be..if u look up at the other post by scott he shows the update script and ota package is made as patches not apks
[Nexus 7 (2013) Android Development] Scott:
I think we have two different conversations...

When I try to convert the image files to a file system for flashing thats when I bootloop.

The ota does not flash at all

I can only get image files to flash using fastboot.
[Nexus 7 (2013) Android Development] EvanA:
OTA format has changed. Recoveries need updating.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Yeah, that sinks bootloader theory...
[Nexus 7 (2013) Android Development] Scott:
Thats what I figured.

And you are correct about Preview binaries. No go for me.
[Nexus 7 (2013) Android Development] EvanA:
It might be something other than binaries because GPS doesn't work on my Nexus 5 AOSP build either.
[Nexus 7 (2013) Android Development] Scott:
You know I looked at the file system of 5.0.0 and it makes a folder and lib folder for each APK.

Did you see that?
[Nexus 7 (2013) Android Development] EvanA:
Yep and it's awesome. Going to make gapps maintaining so much easier.
[Nexus 7 (2013) Android Development] Scott:
Thats cool.

Seems like it may make stock ROM building harder though.
[Nexus 7 (2013) Android Development] freakzapster:
LOL ;););)

Thanks ForReply
[Nexus 7 (2013) Android Development] supersaayuj:
I'm currently on Kitkat.. and i'm downloading this latest 5.0 build to flash!

The question is does it update bootloader to v4.04?

Sorry if it felt like Noobish!:p :silly:
[Nexus 7 (2013) Android Development] eric00716:
Is there any advantage for using preview binaries over 4.4?
[Nexus 7 (2013) Android Development] Scott:
Hmmm

Well stop in any time and share anything you find out. Happy to have you here!

IN the build process, I did not see a difference.
[Nexus 7 (2013) Android Development] Scott:
Well, I went meandering through the Nexus 5 forums and it looks like they are all at the same point we are.

However I do see a flashable ROM so I am going to try otapacakge again as I can plainly see that is how they did there ROM: IllusionRom

Be back in a bit!
[Nexus 7 (2013) Android Development] Scott:
Holly **** it worked. I had to update my bootloader as someone suggested earlier!
[Nexus 7 (2013) Android Development] freakzapster:
WhatWorked ??

Oh Flashable Zip ???
[Nexus 7 (2013) Android Development] eric00716:
Wondering why we dont have the white app drawer like the nexus 9, shouldn't that be part of aosp.
[Nexus 7 (2013) Android Development] Scott:
Not all devices have same features.

Nexus 7 uses Launcher2.apk, Nexus 9 uses Launcher3.apk

IM sure when we get FACTORY images it will be all shored up. But AOSP can have minor differences across devices.
[Nexus 7 (2013) Android Development] Scott:
Yep, Uploading flashable zip now!
[Nexus 7 (2013) Android Development] p4rot:
Is it better to use the 4.4.4 binaries or the preview binaries?
[Nexus 7 (2013) Android Development] Scott:
They both are the same TBH

The preview builds were really 4.4.3.43.43.43.43.43.43.43 (yes this is true!)

So basically the preview binaries are for 4.x

There are no 5.0 binaries

I used preview binaries and still dont have GPS.
[Nexus 7 (2013) Android Development] Scott:
Enjoy!
[Nexus 7 (2013) Android Development] p4rot:
I will give it a try thanks.

If i would build for my nexus 4 also would everything work except for the gps?
[Nexus 7 (2013) Android Development] Scott:
As long as you use some sort of binaries. I cant say for sure because I dont have Nex4 but you could try the 4.4.4 binaries... They worked well except GPS. Have not tried B/T.
[Nexus 7 (2013) Android Development] Scott:
Tell him he was correct!

Updating the bootloader allowed the funky OTA package to flash like a normal ROM!
[Nexus 7 (2013) Android Development] metalblaster:
Im on The last preview build of L, do i need to flash backwards to 4.4 because of the 4.4 binaries you used or can i just proceed as though flashing a normal rom over top of it?
[Nexus 7 (2013) Android Development] Scott:
Binaries are only something people who build the source need to worry about.

Just proceed like normal :good:
[Nexus 7 (2013) Android Development] metalblaster:
Thanks for the quick reply. Alright! diving in. Thank you for the effort of putting together this rom, so many people are *****ing about not having the images for L yet officially that an ASOP version is more than welcome imo.

---------- Post added at 08:23 AM ---------- Previous post was at 08:13 AM ----------

The PAGapps failed due to not being 4.4, is there something i need to do to the file to make it bypass this check or is there some specific PAgapps package i need to use?

edit: Never mind, i ripped the Gapps out of my image for the dev version of L and used that. Then i realized that you already had one posted up here.
[Nexus 7 (2013) Android Development] Scott:
Its something... Just add the Google Bloat and you have a factory image, lol :p

Edit: Cleaned up the OP a bit to make it easier to follow.
[Nexus 7 (2013) Android Development] metalblaster:
just a quick post in case you didn't know. If you install the Gapps directly after installing the rom you end up with a error message and cant access anything. If you boot up however and then reboot into recovery and install those gapps they work but some apps don't seem to be available through the playstore, im assuming because its reading as a weird version of android. Some of the apps i owned were not recognized as owned by Google play despite me being logged in the XDA premium app for instance. The rom its self seems decently stable most of this seems to be with the Gapps. I pushed the newest version of google play into the rom via fastboot/adb after the fact and it gave me some weird errors. Ill check back on the rom later tomorrow, time to multirom back :p
[Nexus 7 (2013) Android Development] Scott:
Good info.
[Nexus 7 (2013) Android Development] Scott:
Did you get it built?
[Nexus 7 (2013) Android Development] vibranze:
Hey Scott,

I think so.

But I don't know what's next? The instruction from android page is to flash the device directly but mine is a VM so I don't think it's applicable. How do I create the .zip file from the build and how do I make customization?

Appreciated your advise. Thanks.

:cowboy:
[Nexus 7 (2013) Android Development] :
Please add hybrid to this, a pure hybrid version would be awesome! And a first!
[Nexus 7 (2013) Android Development] Scott:
Looks like it created "a" file system but if you want to make flashable zip you have to use this command....

make -j(your number here) otapackage

Im building on a 8 core Xeon so I run 3 threads per core for maximum efficency..

so my build command is this...

make -j24 otapackage

That will get me full signed zip from a clean workspace in about 30 minutes.

And the name of my zip is something like "aosp.flo.eng.debug.scott.zip"

So if you just "make" with no directive after you select the build you will get .img files, such as boot.img, system.img, etc. You can than fastboot flash those img files.

But obviously a .zip is better 99.99% of the time.
[Nexus 7 (2013) Android Development] vibranze:
Thanks!

Do you know if I want to make changes to build.prop or some other optimizations, where should I do it?

In the meantime, I will do more research on this but if you already knew about it, kindly share. :)

Cheers.

:cowboy:
[Nexus 7 (2013) Android Development] Scott:
Thats what I am researching myself. I know how to edit the apps and all.

But the default props I am not sure :eek:
[Nexus 7 (2013) Android Development] vibranze:
Thanks Scott.

Btw, make otapackage failed with no target error. I read somewhere that you have to include recover inside, I'm figuring out now how the whole things works. :)

Cheers.
[Nexus 7 (2013) Android Development] Scott:
Works for me. Just synced and building for tonights build.

I see that they did "something" to the keymaster stuff so I am hoping they realized it was missing... and added it, lol
[Nexus 7 (2013) Android Development] meekrawb:
I added the keymaster stuff from your zip to my build folder and did a make clobber, but my build still FC's the security setting.

Edit: NM, I guess it wasn't meant to work that way.
[Nexus 7 (2013) Android Development] Scott:
Indeed!

A lot of people take for granted the complexities that can be had when working with ROMS. They just see ROMS, download, flash, go to next ROM and not even realize the time and effort that goes into just a single ROM and or Mod for that ROM.

Thanks for seeing this!

No, there has to be some sort of "vendor" binaries we can download but I am not sure which vendor to look for. I am going to ask around this weekend.

I need a break...
[Nexus 7 (2013) Android Development] TheDarkDefender:
These are the binaries

https://developers.google.com/android/nexus/drivers

Sent from my Nexus 4
[Nexus 7 (2013) Android Development] meekrawb:
I have all of those binaries on my github. It looks like there is something else missing...
[Nexus 7 (2013) Android Development] Scott:
Yes, I pointed that out on the first page... When intially asked by someone to not forget the binaries... See more below...

Exactly. I dont know what is missing. When I google keymaster nexus7 2013 this is the thread that pops up first...

Second thread is showing a change in keymaster to 4.3.1 but 4.3.1 doesnt compile for Flo, only Deb (I tried last night and 2 nights ago when I initially repoirted that I had seen 4.3.1_R1). I also see that there is an OTA for Deb that is 4.3.1! So maybe we will have 4.3.1 soon.

Maybe google made a mistake because prior to 4.3.0_R2.2 there was not reported ittus. I think they changed "something" in 4.3.0_r3 which is JSS36G.

4.3.1 = JSSL36I??? See LTE forums for info.
[Nexus 7 (2013) Android Development] Scott:
I changed the name of the thread to "[ROM][FLO][10/8][JLS36G] - Pure AOSP ROM - AOSP build discussion for newbs by newbs!"

So maybe more people will join in and discuss instead of ask for changes.

Maybe we can start a movement.
[Nexus 7 (2013) Android Development] meekrawb:
Last night I used

repo init -u https://android.googlesource.com/platform/manifest -b android-4.3.1_r1

put all the proprietary blobs in vendor and it built 4.3.1. Only problem I noticed was the security setting FC.

I have built Slim and CM successfully but this is my first attempt at pure AOSP.
[Nexus 7 (2013) Android Development] Scott:
I gave the exact same command and it refused to pull it. I wonder if the time of day matters :eek:

But still F/C with keymaster... Interesting...

In the Nexus 4 the keymaster files are in the /vendor partition. I checked ours and no such files exist. Which is what originally prompted me to pull them from /system/vendor.

Now that I think about it I probably did android_4.3.1_r1 instead of android 4.3.1_r1!

I would try it tonight but i had to pull the SSD out of my build box to replace a drive in my laptop. New drive is here today but I wont have time to install and sync again until this weekend.
[Nexus 7 (2013) Android Development] vibranze:
Finally I managed to compile it successfully. :)

And I have a 'aosp_flo-ota-eng.vibranze.zip' file in my out folder.

Next question is can I flash this directly to my Nexus as usual? Regarding the keymaster F/C, is this happen after you flashed the ROM?

Will update here again later.

Cheers.
[Nexus 7 (2013) Android Development] vibranze:
I'm using 'repo init -u https://android.googlesource.com/a/platform/manifest -b android-4.3.1_r1'.

Hope this help.

Cheers.
[Nexus 7 (2013) Android Development] vibranze:
Quick Summary

Here is the summary of the whole process, hope it helps who want to build their own ROM instead of keep flashing other people ROM.

1. Install Ubuntu - in this case I'm using 13.04 but I believe any earlier version will do with some adjustment

2. Install OpenSSH server - I installed Ubuntu as a Virtual Machine and I prefer to use Putty (SSH client) to work instead of working directly within the console.

sudo apt-get install openssh-server

3. Ubuntu repo update

sudo apt-get update

4. Dist upgrade

sudo apt-get dist-upgrade

5. Reboot and connect via Putty

6. Follow the guide from - http://xdaforums.com/showthread.php?t=2224142 up to source code folder creation.

7. For the Android repo address, I used

curl http://commondatastorage.googleapis.com/git-repo-downloads/repo

instead of the one from the guide because I kept having an 'Failed with could not verify the tag 'v1.12.4' error if I used that.

8. After the source code folder is created, configure the git username and email.

git config --global user.email "your@emailaddress.com"
git config --global user.name "your name"

9. Create a .netsh file which contains a password from password generator - https://android.googlesource.com/new-password

10. First time repo initialization

repo init -u https://android.googlesource.com/a/platform/manifest -b android-4.3.1_r1

11. Tweak TCP/IP stack, this is optional.

sudo sysctl -w net.ipv4.tcp_window_scaling=0

12. Repo sync

repo sync -jXX

The value of the XX is depend on how many CPU socket and core you have, adjust accordingly.

13. Initialize the build environment

. build/envsetup.sh

14. Choose a host target to use with lunch, I'm using aosp_flo-userdebug, not sure if this is correct or not

lunch aosp_flo-userdebug

15. Last step is code compilation

make -jXX otapackage

This is briefly the process I went through and there are some other areas that I have not explore yet, e.g. setting up the local mirror, ccache which is good to have to speed up the build time.

I will share more once my hand is getting dirtier. :laugh:

:cowboy:
[Nexus 7 (2013) Android Development] meekrawb:
". build/envsetup.sh" works as well. Saves a few key strokes.
[Nexus 7 (2013) Android Development] IIIIkoolaidIIII:
Dirty Flashin Notes

Dirty flashed this over last Preview build and all working pretty much out of the box. A few notes for those trying:

Certain Google apps fail to work and will have to be uninstalled and reinstalled, of note were Google Search and Google Now Launcher.

A reboot is required before flashing the Gapps package, got all sorts of FC's when flashed all in one go.

You need to give the OS a bit of time to settle before can do much with your accounts, a resyncing an authentication issue from what I can tell.

All user setting are reset.

Thanks for the great work.

BTW I used TWRP to flash, I also cleared Dalvik Cache (out of habit I guess lol) which really isn't necessary as we're now on ART ;)
[Nexus 7 (2013) Android Development] sevenup30:
Oooh, the old good one bootanimation "Android"... :D

It's working well, But i had to reboot after adding my account to playstore because it was searching for a while.

here's what i've exactly done to install it (i was on stock unrooted 4.4.4 with unlocked bootloader)

1- Reboot to bootloader to flash TWRP
adb reboot bootloader
fastboot flash recovery twrp-flo.img

2-boot to recovery
formart data parition in Wipe > Advanced Wipe > Format Data partition

3- back to bootloader to update it to 4.4 from OP
adb reboot bootloader
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader

4- back to recovery, now push all necessary ZIP
adb push Android-5.0.0.r2-aosp_flo-ota-eng.11-5-2014.zip /sdcard/
adb push wu_lollipop_gapps.zip /sdcard/
adb push Save-Recovery.zip /sdcard/

5- Now flash :))
5-1: Flash Rom.zip
5-2: Flash save-recovery.zip (DO NOT MISS THIS PART)
6- Reboot (thanks to @metalblaster warn about this)
7- reboot to recovery
7-1 flash wu_lollipop_gapps.zip
7-2 reboot system
8- Enjoy your new Lollipop :)

Now i'll try this more to see what's not working, but it first seem sooo sweet, thanks you for the build [MENTION=426561]scrosler[/MENTION]
[Nexus 7 (2013) Android Development] hasrussian:
Bootloader

My pc cannot connect through fastboot, and so the update doesnt work. i have been using the preview with 4.02 and multirom v28 for a while. do i need to update the bootloader, or can i get away without it. If i cannot, could you put the bootloader onto a flashable zip so i can install it?
[Nexus 7 (2013) Android Development] IIIIkoolaidIIII:
You need the updated bootloader, you can't use a zip to update. You really need too look into why your not getting fastboot access, it's really crucial when using ROMs under development. Likely a driver issue plenty of advice on solving in QA and other threads.
[Nexus 7 (2013) Android Development] sudoeste:
Can someone test if the PkmX L Camera app works?
[Nexus 7 (2013) Android Development] Snap Shot:
yup its working fine
[Nexus 7 (2013) Android Development] sudoeste:
You can use manual focus? That's really good news!
[Nexus 7 (2013) Android Development] hasrussian:
I used a zip on my tf700t to update boot loader. I have fastboot access on other devices, on this device is just connects and immediately disconnects
[Nexus 7 (2013) Android Development] Snap Shot:
yes
[Nexus 7 (2013) Android Development] darkobas:
any way to get root ?
[Nexus 7 (2013) Android Development] sudoeste:
Any chance GPS isn't working because the rom was compiled from 5.0 r2 (the version for fugu) that doesn't have GPS support?
[Nexus 7 (2013) Android Development] sudoeste:
Why in the hell did you lie? did you even tried what i ask ?

And no, the app does not work
[Nexus 7 (2013) Android Development] banny7000:
is bluetooth still a no go?
[Nexus 7 (2013) Android Development] busventinc:
Awesome job Scott thanks
[Nexus 7 (2013) Android Development] EvanA:
No

Bluetooth was never broken
[Nexus 7 (2013) Android Development] b0ld:
gapps issue

hi all,

I've got a strange issue here...I am somehow not able to flash the gapps provided in the first post. I always get the error message:

file_getprop: failed to stat "/system/build.prop": No such file or directory

E:Installation error in /tmp/sideload/package.zip (Status 7)

Installation aborted.

The rom itself works, which means that I can boot up and use it just fine...just without gapps. I already tried using two different recoveries (twrp and cannibal), doesn't really make a difference however. So yeah, any ideas? :P

/edit:

nevermind, tried it with the latest cwm and it works. :P
[Nexus 7 (2013) Android Development] p4rot:
The latest PaGapps fail to install with the latest TWRP recovery, is there any link for 5.0 Gapps or compatible one?

Btw why Twrp gets overwriten with the stock recovery everytime i boot back in recovery?

(i know you have a save recovery file but i just want to understand why and how you came up with this save recovery zip to prevent that to happen)
[Nexus 7 (2013) Android Development] petran_7:
For me in the latest preview it is broken :eek:
[Nexus 7 (2013) Android Development] DelphinusMinor:
If you build it, they will come.
[Nexus 7 (2013) Android Development] AarSyl:
[MENTION=426561]scrosler[/MENTION]. Finally some recognition.

Android Lollipop Unofficial Builds Now Available For Nexus 4, 5 And 7

http://www.androidheadlines.com/201...fficial-builds-now-available-nexus-4-5-7.html
[Nexus 7 (2013) Android Development] darkobas:
Yeah bluetooth seems to turn on. but pairing wouldn't really work

nfc works thoigh
[Nexus 7 (2013) Android Development] hotshot2:
Thanks Scott

Scott thanks for the hard work you do for us keep up the good work .
[Nexus 7 (2013) Android Development] sudoeste:
I made my own build from source using r1 and gps works perfectly as you can see below

Dont know about pairing with headsets as i dont have one, but receiving files work ok!
[Nexus 7 (2013) Android Development] hotshot2:
Got everything working even GPS and blu-tooth

I did a dirty install over OSE-flo-4.4.4-OFFICIAL-2014-09-07.zip and everything is working my GPS is working my Blu-tooth work with my wireless keyboard and mouse .

I installed OSE-flo-4.4.4-OFFICIAL-2014-09-07.zip first then reboot then i updated to Bootloader-4.0.4-Flo.zip then i did the Save-Recovery.zip then installed over everything Android-5.0.0.r2-aosp_flo-ota-eng.11-5-2014.zip then reboot and everything was working good .Camera works good
[Nexus 7 (2013) Android Development] jackxlj:
google now homescreen

i cant get google now homescreen to replace launcher as default launcher
[Nexus 7 (2013) Android Development] sudoeste:
camera always worked perfectly. what i wanted to know was if the builds would support the new camera2 API that requires new binaries and, at the moment, are only available to the nexus 5