yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] droidroidz:
Just went through this, very informative..thank you. As far as not downloading everything with repo sync ..is it possible to edit the .repo/manifests/default.xml file and take out the ones we don't want?

<project path="device/asus/deb" name="device/asus/deb" groups="device,flo" />
<project path="device/asus/flo" name="device/asus/flo" groups="device,flo" />
<project path="device/asus/flo-kernel" name="device/asus/flo-kernel" groups="device,flo" />
<project path="device/asus/grouper" name="device/asus/grouper" groups="device,grouper" />
<project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" />
<project path="device/common" name="device/common" />
<project path="device/generic/armv7-a-neon" name="device/generic/armv7-a-neon" groups="pdk" />
<project path="device/generic/common" name="device/generic/common" groups="pdk" />
<project path="device/generic/goldfish" name="device/generic/goldfish" groups="pdk" />
<project path="device/generic/mips" name="device/generic/mips" groups="pdk" />
<project path="device/generic/mini-emulator-armv7-a-neon" name="device/generic/mini-emulator-armv7-a-neon" groups="pdk" />
<project path="device/generic/mini-emulator-mips" name="device/generic/mini-emulator-mips" groups="pdk" />
<project path="device/generic/mini-emulator-x86" name="device/generic/mini-emulator-x86" groups="pdk" />
<project path="device/generic/x86" name="device/generic/x86" groups="pdk" />
<project path="device/google/accessory/arduino" name="device/google/accessory/arduino" groups="device" />
<project path="device/google/accessory/demokit" name="device/google/accessory/demokit" groups="device" />
<project path="device/lge/hammerhead" name="device/lge/hammerhead" groups="device,hammerhead" />
<project path="device/lge/hammerhead-kernel" name="device/lge/hammerhead-kernel" groups="device,hammerhead" />
<project path="device/lge/mako" name="device/lge/mako" groups="device,mako" />
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" />
<project path="device/sample" name="device/sample" groups="pdk" />
<project path="device/samsung/manta" name="device/samsung/manta" groups="device,manta" />

Assuming we need everything except the devices and possibly a few others? Also this file doesnt get created till you sync for the first time so wont help in the initial sync but thereafter it should...

Ive done some kernel dev but this is brand new for me so correct me if im wrong.
[Nexus 7 (2013) Android Development] Scott:
Actually when you issue the repo init command it downloads and creates that file.

Then when you repo sync it downloads what is in the manifest.

Hence, yes, you can edit that file. but... I dont know what happens when you do. Last time I did that to save time I ended up erasing by build folder and re-syncing so I am not the best to give advice on this.
[Nexus 7 (2013) Android Development] ridobe:
[MENTION=426561]scrosler[/MENTION] - Hey, I just noticed that this thread was reopened. That's what I get for unsubscribing too quickly :) Wow, lots of good information since being reopened. I'm going to get back to it. Thanks! Also, it looks like a bunch of my posts got deleted. Guess I was too whiny?
[Nexus 7 (2013) Android Development] Scott:
Uhhhh... Yeah, the thread got way out of control. So I shut it down until mods could clean it.

I asked them to do a deep scrub and only leave the posts pertaining to development.
[Nexus 7 (2013) Android Development] DsturbD:
good deal, yeah word is "in the coming weeks" lol we all know how that goes. hopefully it will be sooner rather than later

in the mean time i did do a build with your guide and it worked fine. wish the camera did to. im having the same poblem on my S3 with 4.3
[Nexus 7 (2013) Android Development] jakdillard:
Scott I'm giving up on the camera, I got the drivers to build but the interface only popped up for me once ... only once. I think that "KitKat" was a little rushed for the release of the Nexus5 because it seems like only the phones have a somewhat complete source I built two roms for the Nexus4 yesterday and both have not had any issues at all with the camera or the browser. So its looking to me like where android says they are trying to do away with fragmentation they are about to do it all over again or a 4.4.1 release is in the works, sad thing is the worst fragmentation I've seen on android has been with the 4.3 release of jellybean hell really jellybean period because there are some devices still running 4.1.2 but anyways I hope we don't get a 4.4 release for the n4 and 5 and a 4.4.1 release for n7 like what went on with the n7 and 4.3 vs the older devices.

Fellow developers I have noticed that since this guide has become available there have been a number of "clean" or "pure" AOSP roms hitting the board, honestly I get excited when a new dev pops up but its disappointing to see that its the same repetitive "clean" built from source thing that another developer did just hours before. I know we all get ecstatic when we build something for the first time and we want to share thats fine, BUT if you know that all you did was sync the source, typed "make otapackage", and wait the time it took to compile that is the easy part that everybody can do. Development is ever growing, it never stops, however it slows to a handicapped crawl when we start re-inventing the wheel over and over again. I mean come on we have androids not Iphones everthing is not supposed to be the same across the board. I'm not try to down everybody I'm just saying if Scrosler comes out with a pure build and shares it and he says "here's a pure build but x doesn't work" should I come out with the same thing or should I say "well you made a pure build where x is broke its broke for me too but I'll worry about fixing x instead of pushing something out so now we are both working on it to get a finished project". Again not trying to start a deep discussion or fight just trying to push everyone to develop.
[Nexus 7 (2013) Android Development] p-slim:
I'm pretty sure the N7 image will drop this week, we can definitely go a couple of days without the camera. thanks for all the hard work guys its greatly appreciated
[Nexus 7 (2013) Android Development] iamnotkurtcobain:
Think so too. Hopefully the system is smoother/faster after that..

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) Android Development] horst0815:
with the corresponding binaries related to 4.4 and not to 4.3, it will :)
[Nexus 7 (2013) Android Development] iamnotkurtcobain:
You mean OpenGL 2.0 stuff and this kinda things?

Gesendet von meinem AOSP on Flo mit Tapatalk 2
[Nexus 7 (2013) Android Development] Scott:
I have a feeling thats how it is. Just like I predicted. Another rushed build to sell a mediocre phone.

Even the Flo and Deb are at different versions... Flos is techincally at 4.3 and Deb is techincally at 4.3.1.

But I agree with your sentiment.

I never even noticed. I just enter the forums with my subscription link and go to my threads. :o

I hope you are right man! It would be nice.

I really like the "look" of the white and white overscroll. Its really what I have always asked theme developers to make for me.
[Nexus 7 (2013) Android Development] jakdillard:
That's what I was talking about the flo and deb technically all the devices had changes with 4.3.1 but Google didn't release that for Flo or anything else ... and as far as those factory images don't hold your breath lol it look like the mako may be the first to get updated before anything else judging from source but I could be and hope that I am wrong.
[Nexus 7 (2013) Android Development] p-slim:
Does anyone know how to get the stock 4.3 launcher? Sorry if this is off topic
[Nexus 7 (2013) Android Development] Scott:
It builds with the same launcher from 4.3.
[Nexus 7 (2013) Android Development] dre1187:
build errors

Hey all,

Can someone please tell me what I am doing wrong here?

I performed the following:

$ repo sync

$ . build/envsetup.sh

$ lunch aosp_flo-userdebug

$ ./extract-asus-flo.sh

$ ./extract-broadcom-flo.sh

$ ./extract-qcom-flo.sh

$ make clobber

$ make -j12 otapackage

however I get this error: http://pastebin.com/1PQmtVci

I have added the keymaster files as per Scotts vendor folder, as well as I have changed the ota_release_tools file as per Scotts file as well.

thanks in advance!

Edit 1: I have deleted all chromium folders under the 'external' directory and reissued a 'repo sync' to grab back the files/folders I previously removed. I then ran 'make clean' and 'make otapackage' ...will keep posted if issue gets resolved.

Edit 2: still having the same error as above after resyncing sources...any insight on how to fix will be greatly appreciated
[Nexus 7 (2013) Android Development] PR0XiMA:
Are anybody interested in my KitKat Linaro build for the N7 2013 WiFi (flo) and the Nexus 4 (mako)?

If there is enough interest, I might open a thread. :)
[Nexus 7 (2013) Android Development] droidroidz:
Did you try and reinstall all the required packages again? Are you on Ubu 13.10?

---------- Post added at 04:16 PM ---------- Previous post was at 04:14 PM ----------

Id be interested to know what you edited to compile with Linaro and any errors you had to overcome? Please share ;)
[Nexus 7 (2013) Android Development] Scott:
I have honestly never seen that error before.

The only thing I know how to do to fix issues is dump the local repo and re-sync :(
[Nexus 7 (2013) Android Development] Grizzly420:
Figured it out bash was not restarted. As soon as i did that it corrected the issue of dumping the files into my home folder. Now i need to root my device using Ubuntu. Never have used fastboot so get that done and build downloading source now.

When you use fastboot you have to use as root correct? You also because of being in root you don't need sudo correct? How do i initiate root while in adb shell?
[Nexus 7 (2013) Android Development] Dj8218521:
EDIT: so,

make clean

repo sync

add extracted files

. build/envsetup.sh

lunch

(choose your build)

make otapackage -j12

*just my thoughts, i'm not a pro at this*

Thought I could, maybe help.
[Nexus 7 (2013) Android Development] dre1187:
:( that makes me a sad panda...i was hoping to not have to resync the repo

I'll give this a shot before resyncing all sources, maybe it'll save me time
[Nexus 7 (2013) Android Development] droidroidz:
Scott-

The vendor.zip is no longer available from goo.im...any chance you have a mirror or where can i get the security keys to add?
[Nexus 7 (2013) Android Development] Grizzly420:
I found this awesome tutorial on fastboot and he also has one adb. With this thread teaching compiling and building your own rom this might teach and answer some questions for some people.

http://xdaforums.com/showthread.php?t=2277112
[Nexus 7 (2013) Android Development] Scott:
Last time I synced, (a couple days ago) it took me like 30 to 45 minutes. How long does it take you?

Yes, I updated the link in the Op.
[Nexus 7 (2013) Android Development] dre1187:
I ended up reverting to a snapshot and synced the repo again. On my 50meg pipe it took about 45 mins. So now I am back to square one watching it compile...seems to be taking longer then before which must be a good thing ;)
[Nexus 7 (2013) Android Development] Scott:
Let me know if the Camera shows up.

I just synced tonight and its not there any more.
[Nexus 7 (2013) Android Development] PR0XiMA:
The only thing I did was to replace the toolchain with Linaro Toolchain 4.8, and modify the envsetup.sh. That was it.

No errors whatsoever. :)

Sent from my Silm 2013 N7
[Nexus 7 (2013) Android Development] dre1187:
Soo I managed to get a build out and flashed this morning and there is no camera there. The funny part is that I watched it compile the camera and camera2
[Nexus 7 (2013) Android Development] DJLamontagneIII:
Its kinda like how grouper is theres just no launcher if you install the N7 camera launcher or you can set the activity from apex/nova. Problem is it just won't initialize. Can't wait for the official drop :p
[Nexus 7 (2013) Android Development] Prophet968:
Popup bug

If you find a fix for the Keyboard popup bug, please post it somewhere! I'm sure many people would love to see one, I know I've been searching all over for one.
[Nexus 7 (2013) Android Development] dobbs3x:
Trust me if someone finds a fix to the keyboard or the camera it will become well known on these these forums real quick. It will be pretty big deal and the person who finds the solution is going to be getting lots of props.
[Nexus 7 (2013) Android Development] Gorgtech:
Thanks for the thread ;) Though I prefer stock based ROMs, I like the build tutorial :good: I guess I´ll have to try it out soon enough :D
[Nexus 7 (2013) Android Development] nbehary:
I've been digging around in Launcher3 and figured out a hack to make landscape "work". It does it by changing the device's icon size which isn't right, but it's a start. (figuring out where that's set, and that it's set and not calculated for the N7 is useful) There's an APK here: http://xdaforums.com/showthread.php?t=2514426

and a diff of the change here: (EDIT: posting this made me realize that maybe defining the "Nexus 7" isn't necessary. It's not, and results in a more correct version. Deleting the line changed in the diff accomplishes that.)

diff --git a/src/com/android/launcher3/DynamicGrid.java b/src/com/android/launcher3/DynamicGrid.java
index 4776c86..0df7803 100644
--- a/src/com/android/launcher3/DynamicGrid.java
+++ b/src/com/android/launcher3/DynamicGrid.java
@@ -523,7 +523,7 @@ public class DynamicGrid {
// The tablet profile is odd in that the landscape orientation
// also includes the nav bar on the side
deviceProfiles.add(new DeviceProfile("Nexus 7",
- 575, 904, 6, 6, 72, 14.4f, 7, 60));
+ 575, 904, 6, 6, 55, 13, 7, 60));
// Larger tablet profiles always have system bars on the top & bottom
deviceProfiles.add(new DeviceProfile("Nexus 10",
727, 1207, 5, 8, 80, 14.4f, 9, 64));
[Nexus 7 (2013) Android Development] Scott:
Yes, its there but it stopped showing up in the launcher. Not sure if its a change to the launcher or the camera but I see it come in go on nightly builds. Actually it only was there for one or two nights.

I think they are still working on it for the Nexus 7. I think Google is just as lost.

I havent done this yet, but I figured out the keymaster issues by doing a Side by Side compare with the Stock Rooted ROM.

I am wondering if doing the same would allow us to find if a file is missing or some other easy fix...

However, I have a strong feeling we are going to need updated Binaries.
[Nexus 7 (2013) Android Development] PR0XiMA:
If anyone wanted to test my build, here you go.

ROM: https://mega.co.nz/#!MsIymbRa!sBktjhb0Om1X_pLGSZDwAl7--h66VjDDnQYSVcP_xdE

GApps: https://mega.co.nz/#!g45gyJAT!oVN08x99AJnIa774xlhzv4GO6uB79cdoq1wdKBCGtH4

The usual bugs are still there, the only difference the pure AOSP build and this is that I've compiled with Linaro.

Happy flashing! :D

Sent from my Silm 2013 N7
[Nexus 7 (2013) Android Development] Scott:
Cool I will check it out when I get home!

Is there any speed differences in compiling and would you mind explaining how to compile with Linaro toolchain? For newbs like myself? Just download toolchain and edit path?
[Nexus 7 (2013) Android Development] PR0XiMA:
No problem!

I have not tested the build myself yet, so I am not sure about the speed differences.

Anyway I downloaded the Linaro Toolchain 4.8 from here: http://releases.linaro.org/13.10/co...ndroid-toolchain-eabi-4.8-2013.10-x86.tar.bz2

Extract the package, I bet you know how to do that... ;)

Move the folder to the correct location, I don't remember the location in my head right now.

Made a backup of envsetup.sh.

Replaced the path to the ARM toolchain, and you're done.

Took around an hour compiling on an i5 2500K (3.7GHz), with make otapackage -j8.

I'll try to give you the exact path tomorrow morning GMT +1. :)

Right now it is 12:43am, so I better go to sleep. ;)

Sent from my Silm 2013 N7
[Nexus 7 (2013) Android Development] Scott:
I understand from here. No worries. I will give it a try tonight and let you know... (Well it would morning for you).
[Nexus 7 (2013) Android Development] dre1187:
I've got mine compiling with linaro 4.7 haven't noticed any crazy speed differences but I'm sure that will change when kernel source is dropped and the actual kernel gets compiled with the toolchain. I'm going to attempt to use the -O3 cflags to see what happens with performance then.

The path to drop linaro in is: prebuilts/gcc/linux-x86/arm/

I named my extracted linaro folder linaro-4.7

I changed lines 133 and 151 in build/envsetup.sh to have toolchaindir = arm/linaro-4.7/bin

Good luck!
[Nexus 7 (2013) Android Development] Scott:
Perfect thats exactly what I was guessing.

I just repo synced and see some changes so I compiled with standard toolchain. About to flash now... Maybe working camera :fingers-crossed:
[Nexus 7 (2013) Android Development] Scott:
Nope, no camera again :(
[Nexus 7 (2013) Android Development] PR0XiMA:
I guess we need the binaries. :(
[Nexus 7 (2013) Android Development] Scott:
Well the thing is... Its there in the app drawer then just disappears like the AOSP keyboard does. Its strange!
[Nexus 7 (2013) Android Development] Scott:
I also seen rumors they are talking about 4.4.1. I forget where but I bet we dont see anything new until 4.4.1.
[Nexus 7 (2013) Android Development] jakdillard:
to build a true linaro build there are several changes that have to be made in frameworks, skia, dalvik, bionic, build, and so on most people get tricked by the envsetup lines but thats only one of the changes you need . Don't believe me to test in build/core/combo/TARGET_linux-arm.mk change line 38 from TARGET_GCC_VERSION := 4.7 to TARGET_GCC_VERSION := 4.8 and line 116 from ifneq ($(filter 4.6 4.6.% 4.7 4.7.%, $(TARGET_GCC_VERSION)),) to ifneq ($(filter 4.6 4.6.% 4.7 4.7.% 4.8 4.8.%, $(TARGET_GCC_VERSION)),) with no other changes anywhere else and watch how many errors you get .........
[Nexus 7 (2013) Android Development] dre1187:
Oh yeah I forgot to mention that file, I've changed line 116 to support 4.8 and 4.9... [MENTION=632469]jakdillard[/MENTION] where would I find a list of the changes needed to be true linaro? I've only seen guides that only deal with the envsetup.sh file
[Nexus 7 (2013) Android Development] jakdillard:
its been a while since I tried to build a linaro android rom but I remember that I found most of what I needed here in the nexus4 section look for linaro CM and you will find the guide to build linaro AOSP
[Nexus 7 (2013) Android Development] DJLamontagneIII:
You can do something like this its nice because it allows you to set your target toolchains for both kernel and ROM in your device tree https://github.com/DJL10-2/android_build/commit/a254046103d5f53cf9d0dc5c8ffc839cc682a420.. But that will only utilizes the toolchains. Most of the optimizations and actual performance increases come from the flag optimization you use like Strict Aliasing. You can go full -O3 which can be unstable and cause the ROM to be larger https://github.com/DJL10-2/android_build/commit/62d68b5e7159439a5abd5f91568e7028c5f45ba8 or use something lower like -Os that uses all the flags up to -O2 but optimizes for size then hand pick some stable flags that would only be enabled threw -O3 like https://github.com/DJL10-2/android_build/commit/3aeb94293808d85c280ceb78afc015f850cb1a44.. You can find some info about flag optimizations here http://www.linaro.org/linaro-blog/2...aro-android-2011-10-and-future-optimizations/... And here http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html... With that being said with strict Aliasing enabled it will require you to add patches to many android projects to fix build errors caused by some android code breaking strict Aliasing rules luckily it will tell you the project that errord out and you would just need to do some git diving to find a fix most if not all can be found https://github.com/DJL10-2, https://github.com/SaberMod, and https://github.com/IAmTheOneTheyCallNeo.
[Nexus 7 (2013) Android Development] dre1187:
Thank you for all of the tips it was very informative...now time to start looking at all the links posted..

Let the build errors begin!!

Cool thanks will poke around a bit more to see what others are doing. Thanks again!
[Nexus 7 (2013) Android Development] PR0XiMA:
Thank you so much! :D

Was looking all over the place for this, thank you so much! Really appreciated!
[Nexus 7 (2013) Android Development] dre1187:
[MENTION=426561]scrosler[/MENTION]

with regards to tapping into the vendor folder to add files can I create a folder called "stuff" in /vendor and put the files/apks I want in there, then it will automagically copy over? Or do I need to add a folder reference to "stuff" in /vendor/asus/flo/device-vendor.mk like this

$(call inherit-product-if-exists, vendor/stuff/$(LOCAL_STEM))

and then add in the files i want to copy in makefile "/vendor/asus/flo/device-partial.mk" like what is done here:

PRODUCT_COPY_FILES := \
vendor/asus/flo/proprietary/libAKM.so:system/lib/libAKM.so:asus \
vendor/asus/flo/proprietary/libacdbdata.so:system/lib/libacdbdata.so:asus \

thanks in advance!
[Nexus 7 (2013) Android Development] Scott:
Yeah, that is good info!

Thanks!!!

You need to do the latter of the two...

However, when I tried that it wouldnt work, I dont know if my syntax was off so thats when I just tapped into the asus folder and dropped the files and added the lines.

IM sure someone can explain better way without editing the original vendor files (like I did) or without doing your own entire device (thats a bit more advanced for me right now).
[Nexus 7 (2013) Android Development] dre1187:
From my googling of errors when trying to attempt this I believe there are two files you need to change:

1). if you are trying to copy over prebuilt files like an apk you need to comment this section in the following file build/core/Makefile

define check-product-copy-files
$(if $(filter %.apk, $(1)),$(error \
Prebuilt apk found in PRODUCT_COPY_FILES: $(1), use BUILD_PREBUILT instead!))
endef

2). you need to comment out the lines in this file build/core/tasks/vendor_module_check.mk referenced in this post: https://bitbucket.org/ayysir/android_build/commits/058d6336e412756428844af50777915fcf3d4409?at=test this file has a whitelist of acceptable vendors so I assume you can add the name of your folder in this list.

from here you should be able to add your own folder in the vendor directory... *I think*...someone please tell me if I am wrong or on the right track.
[Nexus 7 (2013) Android Development] jakdillard:
I'm tired long day at work so just look at my build folder to compare changes

https://github.com/jakdillard/platform_build/commit/a6de50bb09caeca416b1e7d8879fad2f5e366e83

https://github.com/jakdillard/platform_build/commit/44a4a8713633112ef0ace1e8044c9027e197fe7f
[Nexus 7 (2013) Android Development] dre1187:
Again [MENTION=632469]jakdillard[/MENTION] thank you for all the information!! You and Scott have both been very helpful :thumbup:
[Nexus 7 (2013) Android Development] themikem:
Dumb question:

I'm trying to build an AOSP userdebug variant with lunch.

But "make otapackage" appears to be an invalid build target. Further, flashing the kernel file + ramdisk.img as raw and then manually flashing the rest (userdata.img, system.img, and cache.img) leaves me with something that boots into an un-mountable file system. (adb shell comes back with "/system/bin/sh not found")

So, how does one make an OTA package from AOSP? Or is that even the right question?

Thanks,

Mike
[Nexus 7 (2013) Android Development] Scott:
Did you do this: source build/envsetup.sh

Then this: lunch (choose 9?).

then run the make otapackage?

I would hazard that you did not and that you built for the emulator.