yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Reginald476:
That's pretty much where I am at with Github.

What I did was look through these commits and did the edits manually to the files. I also used Jak's commits to add the Advanced Power Menu

I used GEdit to make changes to the files.

I am sure someone can explain repo sync but I am pretty sure they are the close to the same.
[Nexus 7 (2013) Android Development] DJLamontagneIII:
Hey guys how are you getting the camera launcher to show in the app drawer? It builds and is usable for me if I set it as a activity or install the 2012 N7 camera launcher.
[Nexus 7 (2013) Android Development] nbehary:
It's just there in mine w/o doing anything special. (Though I now have 2. One that came from my build, one from my backup of Stock 4.4 I assume. Same version, different build #'s. The one was there before I did the restore though.)
[Nexus 7 (2013) Android Development] DJLamontagneIII:
finally tryed a full wipe and it installed correctly :good:
[Nexus 7 (2013) Android Development] Scott:
I had some wierd issues building for the past 3 days...

Not sure if its hardware or something else...

I would build with the typical "make -j24 otapackage" and half way through it would die with "Compiler segmentation fault error" or some similiar verbiage.

So I did this...

Dumped Repo and Re-synced repo - did not fix

Re-installed ubunutu fresh and resynced repo - did not fix.

Compiled the otapackage with just one core... Compiled just fine. I let it run over night.

Its a Xeon X5550. Was slightly O/C'ed but dropped the O/C back to normal when I re-installed. And still had the issue.

Think I was just pushing the processor too hard?
[Nexus 7 (2013) Android Development] Scott:
Nevermind, I was wrong...

Its failing with 1 process

This is a fresh install.

Anyone else see this?
[Nexus 7 (2013) Android Development] Scott:
Wow, now it gets weird...

I created the same set up except in a Windows 8 Pro Hyper V config (on a different box) and it built fine :eek:

So that rules out the repo and the make command, lol

Must be some hardware thing on that other X5550 box.
[Nexus 7 (2013) Android Development] jakdillard:
sometimes when you use an arguement such as -j24 or higher make will build a package that depends on something else before building the something else
[Nexus 7 (2013) Android Development] dre1187:
[MENTION=426561]scrosler[/MENTION] this has happened to me before and I ended up dumping the repo and then did

repo sync -j4 -f --no-clone-bundle

finally after that was done I did

repo sync -j1

. the first time it tried to build it failed so I did

repo sync -j1

again and then finally it built. Not really sure what happened but it worked. I hate dumping the repo cause it sucks up unnecessary bandwidth and time and it seems like ISP's are becoming stringent on usage up in the Great White North...on the bright side at least I have unlimited bandwidth.
[Nexus 7 (2013) Android Development] Scott:
Interesting...

I ended up dumping the OS, re-installing, and its going good now.

I think I will limit my builds to -j8 as they actually build just as fast.

I think I hit the point of diminishing returns.
[Nexus 7 (2013) Android Development] Scott:
Updated ROM and Build guide to reflect the latest KRT16S Update.

Enjoy!
[Nexus 7 (2013) Android Development] roger99:
Hi, noob Android builder here :)

I followed your guide a little while ago and got as far as sync'ing the repo. I've got a little time to play around again now and I see the source in the repo has updated to 1.2.

I have a *very* slow connection and the sync took a very long time last time. If I reissue the repo init command for 1.2 then sync again, will that just update the code I already have, or will I have to re-download everything again?

EDIT: OK, i think i have answered my own question, I just reissued the init command for 1.2 and sync'd and it didn't take hours and hours and hours :) like last time. So i'm gonna move onto the next steps now.......
[Nexus 7 (2013) Android Development] Grizzly420:
quick question i have gotten everything to build properly. Do you have to install a kernel also when building from aosp? I found some information saying yes but they were a couple years old, and didn't know if something has changed. Also, there is a boot.img file in the ota package. After install in just sits at the google splash screen this is the only thing i can think of.
[Nexus 7 (2013) Android Development] Scott:
Yes, that is how I udpated both my machines.

Kernel is in the boot.img and if you synced repo propelry it would be a prebuilt kernel. If you didint sync correctly you would not have boot image and the build would fail.

However, If you are stuck at splash I would challange you to confim you installed the propriatary binary files. When I was frist trying to figure all of this out I did not have the binaries installed causing me to not have the Adreno drives and the device just to sit at boot screen. Then it would soft brick itself.
[Nexus 7 (2013) Android Development] Grizzly420:
I made a directory aosp then downloaded binaries from op. I unziped the asus, broadcom, and qualcomm, folders in the (i hope) root of aosp folder. Man i hope I did this right LOL. I opened the folder and just pasted them in with everything else when you initially open the folder or root. Did i put them in the wrong location?

I greatly appreciate the help. This is the first time I have actually gotten java set up right and build with out stupid errors. Its been almost a year since i messed with all this and no more than beginer noob LOL.
[Nexus 7 (2013) Android Development] roger99:
You need to run the three scripts that you pasted into the directory so they extract the binaries into their relevant vendor folders. So, open a terminal, make sure the aosp dir is your current directory then execute the scripts.

Thanks for the guide Scott by the way, my build completed successfully and booted, but location services don't seem to work ?
[Nexus 7 (2013) Android Development] Grizzly420:
Sweet makes total sense thank you very much man. :good::D

---------- Post added at 08:30 PM ---------- Previous post was at 08:10 PM ----------

OK I am an idiot i cant find how to run the scripts I have looked and cant find how to do it. It actually pissing me off because I am going to feel like an idiot as soon as I do it. Any help is appreciated.
[Nexus 7 (2013) Android Development] roger99:
No worries, tis easy ?. Im not at my machine right now, so i cant remember the exact filenames so you will have to fill that bit in.... ? When you are in the terminal in your aosp dir issue

./asus-blah-blah.sh

./qcom-blah-blah.sh

Etc. They should then run and extract. If for some reason they don't you *may* have to make sure they are set as executable, so right click em in your file browser and go to properties to set the execute flag.
[Nexus 7 (2013) Android Development] Grizzly420:
when your at your terminal it would look like

toycrawler81@ubuntu:~/aosp$ sh extract-broadcom-flo.sh then it pops up and hit enter a million and one times then type I ACCEPT

Thank you very much for pointing me in the right direction i hate to be spoon fed commands. I like to hunt and find what to do so it re enforces the learning portion. The (sh) command is probably a basic command but I still have a lot to learn with Linux. I have gotten to the point though I don't use windows at all except for a few exceptions. Like i don't know if you can root your htc one with out a tool being a noob/novice. Also I just learned you cant upload movies to vudu/ultra violet for your personal library on Linux, but for the most part I am done with windows.

Enough off topic I did asop$ make clean and I am building again. I am confident this will fix my issue.

I should be able to put superSU in the system/app folder for root. What do i do so that it does not flash a stock recovery?
[Nexus 7 (2013) Android Development] roger99:
Glad you got there in the end ? a future heads up, putting a ./ in front of a command in Linux indicates that what you are trying to run is in your current directory in which case it won't look for the command in your path. So $./extract-broadcom-flo.sh is essentially the same as $ sh extract-broadcom-flo.sh. also hitting space instead of enter when reading the agreements is a lot faster ?
[Nexus 7 (2013) Android Development] Grizzly420:
Right on thank you very much help I do greatly appreciate it.
[Nexus 7 (2013) Android Development] Grizzly420:
Alright booted up but no wifi. So i think something got screwed up up instaling the binary/blob.

Unless someone has something else in mind will clean build folder, reinstall that driver and build again. Damn i thought i had it.
[Nexus 7 (2013) Android Development] Scott:
There should be "3" driver files that need installed, aka decompressed to "vendor"

Make sure you get all 3 and of course make sure they are KRT16S versions.
[Nexus 7 (2013) Android Development] Grizzly420:
Yea i amgoing to go through the process again make sure i did each one, and not actually the same one twice. But it booted up at least. That was progress
[Nexus 7 (2013) Android Development] Scott:
Indeed. what I do to make it easier (and less tasking) is rename the files when I download them to 1.sh 2.sh 3.sh.

Then in the terminal I only have to type "./1.sh" 2 and 3...

Makes it easier for me and saves time from typing out the whole name of the file.

Laugh but it works :silly:
[Nexus 7 (2013) Android Development] Grizzly420:
no makes sense to me I hit properties on the file and when it pops up it's already highlighted then hit copy and past, but that works also.

I just checked all vendor files were there. I went ahead and reinstalled the qcom which is for wifi driver, and building again. I thought it was weird that it saw my router just would not even attempt to sign in. I saw in another thread that someone else mention something similar. One response was it took them three or five times before it actually worked. Which doesn't make sense to me, but building again we will see what happens.

I am actually going to wait to leave for deer hunting till 3 in the morning so i can mess with this. I kills me to be close to figuring something out and leave it without completion/victory. LOL
[Nexus 7 (2013) Android Development] Scott:
We call that Addiction...

Congrats, you are now in the club...

My name is Scott and I am an android ROM Builder.
[Nexus 7 (2013) Android Development] Grizzly420:
Well Houston we have lift off and a successful build. Not sure if it was the qcom blob. All I did is reinstall that, but all is good. Now I need to learn adb to zip align and a few other tricks.

Thanks everyone, I am very thankful for this thread so we can learn together.

Edit: just want to say everything is running awesome or it could be bias placebo affect just saying
[Nexus 7 (2013) Android Development] lotherius:
Thanks for this guide. I'm getting a build environment set back up because of the apparent lack of DEB roms versus FLO roms. Looks like they're too different to port without actually rebuilding, so I want the build env ready to go. Gotta say though, the desire to build/run custom roms is much less with modern versions of Android than it was back in the Froyo/Gingerbread days. Amazing how much better stock is now.
[Nexus 7 (2013) Android Development] Grizzly420:
Is there a way to see what changes are in the repo updates? Or the lines of code have been added or changed?
[Nexus 7 (2013) Android Development] DJLamontagneIII:
https://android.googlesource.com/
[Nexus 7 (2013) Android Development] Grizzly420:
Thank you sir
[Nexus 7 (2013) Android Development] Grizzly420:
Does any know of a good tutorial on doing tweaks, advanced power menu, and different things?

I don't want to stray away from stock but with to learn now to do some manipulating of some code and add just a few custom features I use.

I have found some but looking for more
[Nexus 7 (2013) Android Development] Scott:
Google what you are looking to do.

I dont know many people that share guides.
[Nexus 7 (2013) Android Development] GatorsUF:
Anyone else having trouble getting Facebook to open? Keeps crashing, however I don't get a force close message. It just never opens..
[Nexus 7 (2013) Android Development] Grizzly420:
Well trying to find good stuff for free is a little taxing, but check out all these free tutorials freaking awesome.

http://thenewboston.org/tutorials.php

---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

No facebook is fine for me. Try clearing data, cache, force stop. Then try to sign back in and see if that works.
[Nexus 7 (2013) Android Development] Reginald476:
I really like the tuts from The New Boston as well.

What I did for tweaks and such was to look to other Devs Githubs. Rascarlos is a really good one, Jak's is also very helpful. I posted some links a couple of pages back. If you look at the commits, they will typically title them in such a way that it is easy to figure out what they are doing.
[Nexus 7 (2013) Android Development] LeeC:
Salute. for scrosler's awesome build guide. Not only give us a wonderful ROM but also a guide how to build our own.:good::good::good:
[Nexus 7 (2013) Android Development] lotherius:
Is there a simple way to get the correct build.prop values to be included in the build? That is, the correct model name (Nexus 7) not "Aosp on Deb" and such...

EDIT: found a thread. Looks lengthier than I wanted to tackle tonight:

http://rootzwiki.com/topic/15145-build-overrides-on-pure-aosp-builds/
[Nexus 7 (2013) Android Development] DJLamontagneIII:
Depends how you want to do it. You can really just edit one line https://github.com/DJL4-4/android_device_asus_flo/commit/ea4678b2f4a9a6a769c800171a7bedcfc6cdb6bc
[Nexus 7 (2013) Android Development] Scott:
Updated the guide to reflect the 4.4.2_r1 repo....

Will post ROM tomorrow if anyone wants to play with it.
[Nexus 7 (2013) Android Development] Scott:
ROM Updated to 4.4.2

Links in OP!​
[Nexus 7 (2013) Android Development] jdmegkoupe:
binaries/ drivers

can anyone direct me please? im trying to find opensource drivers/binaries for sprint evo 4g "supersonic" and the sprint evo 3d (any source for binaries would be appreciated). im trying to do some rom creation and development on these devices before i mess with my note 3 and nexus 7 2013. thanks in advance guys.
[Nexus 7 (2013) Android Development] Scott:
You will need to pull them from the device. Maybe you can use the vendor folder already on the phone.

Otherwise they are not open source nor are they distributed to the public.
[Nexus 7 (2013) Android Development] jdmegkoupe:
thanks, my research seems to point to the same solution using "./extract-files.sh" but id rather ask and get it right the first time. appreciate the quick response scrosler!
[Nexus 7 (2013) Android Development] Scott:
Good luck!
[Nexus 7 (2013) Android Development] dre1187:
Good evening folks,

Hoping someone here can help me out, I am going crazy trying to get this going...my problem is trying to compile a rom using a different kernel source then the one that ships with the ROM.

If I go into the kernel directory and I can compile the kernel and get a zImage using the config file pulled from /proc/config.gz

The issue occurs when I change the kernel source in the board config file and I use the $device_defconfig file, I get the following error:

make[3]: *** [block/test-iosched.o] Error 1
make[3]: *** Waiting for unfinished jobs....
CC drivers/base/regmap/regmap-debugfs.o
CC fs/proc/version.o
CC drivers/base/regmap/regmap-i2c.o
CC fs/proc/softirqs.o
CC drivers/base/regmap/regmap-spi.o
CC fs/proc/namespaces.o
make[2]: *** [block] Error 2
make[2]: *** Waiting for unfinished jobs....
CC fs/proc/proc_sysctl.o

any ideas/hints would be great, I have tried googling errors but nothing really caught my eye.

thanks in advance!
[Nexus 7 (2013) Android Development] DJLamontagneIII:
Could you upload the defconfig your using. Some build test-iosched as a module which may not be enabled or you may have some other unmet dependency like DEBUG_FS. You can find the dependencys in your block/Kconfig.iosched. a simple fix would be to disable it with # CONFIG_IOSCHED_TEST is not set but you should be able to build test with the build it builds fine in my builds.
[Nexus 7 (2013) Android Development] dre1187:
Thanks for the reply!

My first thoughts were to diff the two defconfigs I only found three lines that were different and those refer to kexec multi-boot patch.

here is the defconfig for the ROM: https://github.com/omnirom/android_kernel_asus_flo/blob/android-4.4/arch/arm/configs/flo_defconfig

and the custom kernel defconfig: https://github.com/franciscofranco/flo/blob/nightlies-4.4/arch/arm/configs/flo_defconfig

also test-iosched isnt the only one it errors on, it does so on the other schedulers like ondemand as well.

I will take a look at the Kconfig files now...

thanks again!

UPDATE:

I looked at the kconfig.iosched file and the only difference was the addition of the ROW scheduler...

if i compare the Makefile of the both kernels I notice that Omni uses REAL_CC and franco does not ...would that have anything to do with it?
[Nexus 7 (2013) Android Development] markwebb:
Thanks for the great Rom. I really prefer aosp!
[Nexus 7 (2013) Android Development] Scott:
Has any one tried building 4.4.2_r2? I think it is KOT94R (I forget exactly)?

I tried and can no longer get AOSP browser to nab my location!
[Nexus 7 (2013) Android Development] jakdillard:
Yep.

Browser is doing what its supposed to
[Nexus 7 (2013) Android Development] Scott:
Edit: Oh... I see!
[Nexus 7 (2013) Android Development] Scott:
Well, well, well, look what I just made :)

I also update the instructions to build to reflect building on Ubuntu 14.04 LTS. Really only one dependency changed. Every thing else was the same. I also note that on the google page on how to build from source they made an error. They tell you to use open JDK 7 but in reality they go on to say you must use Oracle Java 6. I dont get it :confused:

Eitherway...

Enjoy!

-Scott
[Nexus 7 (2013) Android Development] Scott:
Well, I had to have a tooth pulled today (NOT FUN!) so after I woke up from the narco pain meds I decided I slept too much and needed to do something constructive...

So I updated PureROM to android 4.4.3_r1.1 / KTU84M!

Download links in the OP

Other than that this is the same as all the other builds, PURE AOSP with the exception of Root and BusyBox added for convenience.

I also added Trim commands during install. If you dont know what TRIM is look HERE!
[Nexus 7 (2013) Android Development] v3rk:
New builds running great! Thanks for this, I've been looking for a simple vanilla ROM. Looking forward to following your tutorial once I can get the proper equipment. I've put off learning this for too long.
[Nexus 7 (2013) Android Development] Scott:
Updated to 4.4.4_r1 KTU84P

I also updated the build guide to reflect the new version number in the repo init command

Enjoy!
[Nexus 7 (2013) Android Development] droidroidz:
wouldnt the repo init command in the fp need to be:

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

Just realized this after Ive been waiting for it to sync for an hr o.O
[Nexus 7 (2013) Android Development] Scott:
Yeah, thats what I have. I just updated the 4.4.4 from 4.4.3_r1.1
[Nexus 7 (2013) Android Development] droidroidz:
Sry I musta copied wrong or something..my mistake.
[Nexus 7 (2013) Android Development] Scott:
Updated to 4.4.4_r2 - KTU84Q

Build Info

Build: KTU84Q

Build Verision: 4.4.4_r2

Build date: 7/28/2014

Rooted with SuperSU

FSTRIM during install

Busybox v1.22.1-Stericson

MD5: 35E1D4D25B7CFC9DA77FBDEA03F0AE45
[Nexus 7 (2013) Android Development] jordirpz:
Hi, where is this rom please? I only look ktu84p odex/deodex, but i dont look ktu84q. Thanks

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Android Development] Scott:
http://www.scottsroms.com/downloads.php?do=file&id=544
[Nexus 7 (2013) Android Development] jordirpz:
[MENTION=426561]scrosler[/MENTION] hi, gps doesnt work for me?

Enviado desde mi AOSP on Flo mediante Tapatalk

---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------

I installed gps status

Enviado desde mi AOSP on Flo mediante Tapatalk
[Nexus 7 (2013) Android Development] Scott:
Maybe the binary files have to be updated.

Google has not made an update to them yet so this may be a problem until an official release.
[Nexus 7 (2013) Android Development] Scott:
I hobbled together an AOSP Lollipop ROM.

I had to use the drivers from 4.4.4_r1 so I dont expect some features to work like may GPS or Bluetooth.

I also cannot get it into flashable format so it has to be fastboot installed.

There is a simple batch file included wiht the download.

Download to PC, unzip file, run batch file... enjoy AOSP lollipop!

Uplaoading now...

Teaser...
[Nexus 7 (2013) Android Development] hotshot2:
Can't Wait!

Can't Wait! to download
[Nexus 7 (2013) Android Development] Scott:
Uploading now...

Wont be long...

Remember this is pre-google release so there will be bugs...

But its damned smooth!
[Nexus 7 (2013) Android Development] markwebb:
So this isn't based on yesterday's release?
[Nexus 7 (2013) Android Development] Scott:
It is based on yesterdays release.

HOWEVER google is dragging there ass in the sand to release the updated drivers.

So I used the 4.4.4 Drivers but the Operating system is Pure AOSP 5.0.0_r2.

The only thing that will change when the drivers come out will be... The drivers.

But this is 100% the source code. You have to understand Source code and Binary drivers are two different things.

Does that clarify a bit better?
[Nexus 7 (2013) Android Development] Scott:
ROMS Up!​

READ the instructions FULLY before you flash (or try to flash)!!!!!!!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Don't believe this... fired up the pc ready for DL and the goddamed thing just shat the bed!

I can't take this anymore....
[Nexus 7 (2013) Android Development] N1ldo:
"aosp_flo-img-eng.scott.zip"

Only English language?
[Nexus 7 (2013) Android Development] Scott:
Its pure AOSP. Im not sure what languages AOSP Source has in them.
[Nexus 7 (2013) Android Development] $tefanDroid:
Thx for your rom. But what Gapps version should i flash on top of your lollipop release? are the 4.4.4 gapps ok?
[Nexus 7 (2013) Android Development] TheIronMaiden:
don't need to flash gapps, theyre already baked in

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Either way, I'll wait for the drivers and a cleanROM 5.0
[Nexus 7 (2013) Android Development] eric00716:
Need to flash PA Gapps package they are not built in read OP.
[Nexus 7 (2013) Android Development] Scott:
Yes, this is not CleanROM so you will need to flash GApps
[Nexus 7 (2013) Android Development] TheIronMaiden:
aaarrrrgghhhh my bad, I mistook it for a factory image, not used to the "built lollipop from source" notion yet.. flash ROM and then GApps.... thanks scrosler.... Rock on
[Nexus 7 (2013) Android Development] Bright09:
I'll wait till they release factory image I'm stoked
[Nexus 7 (2013) Android Development] zaclimon:
[MENTION=426561]scrosler[/MENTION] Have you tried the drivers from there to see if it makes a difference?
[Nexus 7 (2013) Android Development] Megaflop666:
Woot Woot!
[Nexus 7 (2013) Android Development] freakzapster:
Correct me if I'm wrong

As the source code is released fully then why not drivers of 5.0 ????

Sent From My Xperia L
[Nexus 7 (2013) Android Development] Snap Shot:
read Here
[Nexus 7 (2013) Android Development] zaclimon:
Because while the code of android is open source, the drivers are not and they depend on the discretion of the chip manufacturer. Normally both factory images and the drivers binaries come at the same time.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] hotshot2:
GPS dont work but i dont use it anyways i know who i am lol
[Nexus 7 (2013) Android Development] atlharp:
Awesome work! Thanks again!
[Nexus 7 (2013) Android Development] newellj79:
Can anyone confirm the PA gapps are working correctly? I'm looking for gapps to use on a build for my nexus 10.