yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] themikem:
I did do those, yes. I've built Cyanogen and custom kernels frequently, but I've never bothered with AOSP (mostly because I didn't own a Nexus device until a few days ago...) I did lunch, picked the deb build, and ran make -j32 otapackage.

I'm not really sure what the problem was, but I deleted the tree and did a fresh repo clone and it makes ota zips now. Maybe just a bad download or something? Anyway, sorry for wasting your time. Keep up the great work. I'll be following this looking for camera and keyboard fixes :)
[Nexus 7 (2013) Android Development] Scott:
Dont feel bad, I couldnt build for the last two days. Crazy errors.

Finally wiped my repo and re-sync'ed. :mad:
[Nexus 7 (2013) Android Development] Scott:
Can anyone explain if there is a way to "go back" to Android 4.3.1?

I specified the 4.3.1 manifest in my repo init command.

I just did a fresh install of ubuntu and am trying to sync 4.3.1_r1 and it seems to be working but as it scrolls up the screen I see references to 4.4.

Any one have any input / thoughts on that.
[Nexus 7 (2013) Android Development] Scott:
Well I answered my question...

You can repo sync an older repo
[Nexus 7 (2013) Android Development] jakdillard:
its only listing the branches ie: "new tag android-4.4_r1"

Why are you going back to 4.3.1
[Nexus 7 (2013) Android Development] Scott:
More so a test to see if it could be done.

Just experimenting is all
[Nexus 7 (2013) Android Development] Scott:
Just an FYI. I posted my Weekly Saturday night build. No major changes. Camera is still broken.

I fixed a couple issue with my gapps though that was causing the Google Keyboard to not work as well as resolved some file duplication.
[Nexus 7 (2013) Android Development] Warbs816:
Can anyone tell me if screen recording works or not?
[Nexus 7 (2013) Android Development] nbehary:
Yes, it does. I've noticed you asking in another thread. Any 4.4 ROM really should. I can't imagine that's easy to break.

Unless you are asking about it working right.... It does fail at full resolution and fallback to 720x1280. I think it may do that on any ROM though. It has every time I've tried it.
[Nexus 7 (2013) Android Development] Alucardis666:
Thanks for this!
[Nexus 7 (2013) Android Development] bajasur:
4.4 ota is going live tonight for nexus 7
[Nexus 7 (2013) Android Development] duryard:
Is that a question or a statement and where does is say so if the latter?
[Nexus 7 (2013) Android Development] Scott:
I have not looked at the CM Repo yet.

What I mean by the statement of keymaster is that I pulled the files from the Google image. I then put them in the AOSP ROM.
[Nexus 7 (2013) Android Development] Scott:
Here are the missing files if this helps you understand better...

Its flashable so you can flash it over top your own AOSP build to fix the issue with the settings...
[Nexus 7 (2013) Android Development] TheDarkDefender:
Sweet. Thanks. If you're able to push those changes to your Github as a commit, that'd be nice.

Btw,took care of the troll ;)

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] Scott:
I dont have a Git hub. This was my first ever AOSP ROM. I just built it to see what all the fanfare was about.

I have no intent on a Git hub at this time.

Not sure if you saw but I posted the keymaster files in flashable format for you just 2 posts back.

And thanks for de-trolling. There are too many young children on XDA these days, lol :silly:
[Nexus 7 (2013) Android Development] Scott:
Did that fix the problem on his ROM?
[Nexus 7 (2013) Android Development] vibranze:
Sorry for the noob questions,

- Will we get the update notification as in Google stock ROM by building our own ROM based on Google AOSP base?

- What is the different between Google stock ROM and building own ROM based on Google AOSP base? What is the differentiators?

I'm setting up my Raring's VM now to kick start the build so pardon me the questions if the answer is too obvious hehe.

Thanks.
[Nexus 7 (2013) Android Development] vibranze:
Doing a repo sync right now :)

Btw, I'm not sure what should I put when I did "repo init -u https://android.googlesource.com/a/platform/manifest -b ??" so I just use without -b parameter.

Also it's worth to mention that you have to setup your git first with the following command:

git config --global user.email "you@example.com"

git config --global user.name "Your Name"

and create a ~/.netrc which consist of your git password.

:)

Update:

Syncing work tree: 90% (343/381) fatal: cannot create directory at 'arm-linux-androideabi/lib': No space left on device

Traceback (most recent call last):

File "/home/hanlint/android/.repo/repo/main.py", line 418, in <module>

_Main(sys.argv[1:])

File "/home/hanlint/android/.repo/repo/main.py", line 394, in _Main

result = repo._Run(argv) or 0

File "/home/hanlint/android/.repo/repo/main.py", line 142, in _Run

result = cmd.Execute(copts, cargs)

File "/home/hanlint/android/.repo/repo/subcmds/sync.py", line 657, in Execute

project.Sync_LocalHalf(syncbuf)

File "/home/hanlint/android/.repo/repo/project.py", line 1080, in Sync_LocalHalf

self._InitWorkTree()

File "/home/hanlint/android/.repo/repo/project.py", line 2059, in _InitWorkTree

raise GitError("cannot initialize work tree")

error.GitError: cannot initialize work tree

!!@$#!@#$@!#$%@#%#@%@#$#$^#$% make sure you dedicate a big hard disk space for it else you will suffer the errors above, you have been warned! :D
[Nexus 7 (2013) Android Development] Scott:
Yeah, I was going to say....

1. You are downloading every version of Android when you prolly only want the 4.3_r3.1 base so put that for the repo sync

2. Uncomrpessed that rep is about 18 gigs.
[Nexus 7 (2013) Android Development] vibranze:
LOL, so I should use 'repo init -u https://android.googlesource.com/a/platform/manifest -b 4.3_r3.1' instead?

I will attempt one more time, wish me luck!

:cowboy:
[Nexus 7 (2013) Android Development] Scott:
Yep. unless you want older. But even then I cant say for sure it would really pull the old stuff.

I just repo'ed the latest and that was 4.3_r3.1
[Nexus 7 (2013) Android Development] snachez:
Whats the best way to get TabletUI on this ? Would love to switch from AOKP to AOSP :)
[Nexus 7 (2013) Android Development] Scott:
IMHO, ask someone who has built a tablet UI from scratch, see if they will share the code, and then rebuild it against those changes.

But I dont think that is what you mean... However that is how I would like to learn how to do it.
[Nexus 7 (2013) Android Development] vibranze:
Is it normal to see the following lines:

Now I stucked on this for quite sometimes, the receiving objects is keep running but not sure how long I should wait for it to finish.

Can I ignore the 'Connection reset by peer' message? Seems the download is not complete and reset by the server, will it causing issue during the build?

Thanks.
[Nexus 7 (2013) Android Development] Scott:
Just sync it again. I think google had server issues earlier today. I saw random reports of the play store being offline and other little odditites.

I just did a repo sync for my next nightly (5 mintues ago) and I am not sure if I am reading it right but it likes like 4.3.1_R1 just got pushed to AOSP.

Building it now... But too tired... Will be in bed soon.
[Nexus 7 (2013) Android Development] vibranze:
Thanks Scott. It's quite a tiring process, have to wait and wait without knowing when the sync will be done.

Btw, can I ask the repo sync to only sync Nexus 7 2013 and not all the devices?

Have a good rest.

Cheers.
[Nexus 7 (2013) Android Development] Scott:
That's above my head. Remember, I only started doing this 48 hours ago, lol.

Im only two days ahead of you in knowledge :eek:
[Nexus 7 (2013) Android Development] Scott:
It built but its still only JLS36G
[Nexus 7 (2013) Android Development] vibranze:
Not sure how many times I have to keep trying. :(

Update: building now. :)
[Nexus 7 (2013) Android Development] IXChicharitoXI:
Is this only for the LTE Nexus 7?
[Nexus 7 (2013) Android Development] TheDarkDefender:
No. Only for the wifi variant.

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] Scott:
Ive read it on a few sites myself...

Just playing the waiting game now...

Checking Repo...
[Nexus 7 (2013) Android Development] Scott:
Nothin...
[Nexus 7 (2013) Android Development] GTMoraes:
Well um, I already have. Flashed the stock 4.3 and then flashed the OTA I got somewhere. Idk if it's the same on the first post.

Works nice, but it's lame that there is no mod =\
[Nexus 7 (2013) Android Development] Scott:
Now that we have the OTA I am hoping google will post the images and the binaries tonight!

Hoping....
[Nexus 7 (2013) Android Development] Scott:
Not sure if anyone saw, but I posted the official KitKat OTA here:

[ROM][11/13/13][Flo] - {Official} - Stock Rooted 4.4 - KRT16O - KitKat!
[Nexus 7 (2013) Android Development] DJLamontagneIII:
That would be nice maybe even the kernel source :P
[Nexus 7 (2013) Android Development] Scott:
Indeed!

If not though... We can still use the vendor folder and libraries in our AOSP builds so we atleast got something to mess with while we wait for official source :good:
[Nexus 7 (2013) Android Development] Scott:
Looks like you were right :highfive:
[Nexus 7 (2013) Android Development] GTMoraes:
The 4.4 Kit Kat. I've flashed the 4.3 then upgraded with the 4.4 OTA zip.

Having a hard time with GPS here, it used to work on 4.3, but now it's taking too long to get a lock, and it's just getting a lock with one or two sattelites (even though it could find 7).

Used to lock with 20 from 25 sattelites. Now this is just ridiculous.
[Nexus 7 (2013) Android Development] tiny4579:
Since we have the ota we have the binaries. Just pull the files from an updated device that match the filenames of the 4.3 binaries.
[Nexus 7 (2013) Android Development] LoopDoGG79:
Just checked myself. Locked very quickly (I'd say even quicker then normal!? O_o ) GPS status looks normal. This is while indoors
[Nexus 7 (2013) Android Development] HD87:
Hmm.. doesn't look like much changed.. I was looking forward to the bottom bar being transparent, from what I understood they changed the app launcher to have only apps, this launcher still has apps and widgets. Long pressing should bring up wallpaper, widgets and settings. This one doesn't. In home screen should be able to just say "Hello Google" to go into voice search but that's not working. Are these features unique to Nexus 5 launcher? Can we get that apk?
[Nexus 7 (2013) Android Development] LoopDoGG79:
Check out this link.

http://www.android.com/versions/kit-kat-4-4/

Where it mentions touchless voice control there is an asterisk. Go to the bottom, you will see " Currently only available on Nexus 5"

As far as the launcher apk, there is a thread out there with it and instructions in how to install it. Unfortunately, it's pulled from the Nexus 5. Does not work well in landscape mode.
[Nexus 7 (2013) Android Development] GTMoraes:
Indoors I can leave it trying to find a lock for hours (literally) and it won't. Outdoors sometimes it have a hard time, but eventually does get.

I think I got a faulty device. First one ever.

Had to occur to me someday, I had several devices which could have had serious problems and didn't suffer anything -- until now =(

had to have a rotten one someday.

Sadly I can't return this, as I've imported it. Oh boy.

At least the touchscreen works fine
[Nexus 7 (2013) Android Development] HD87:
It looks like that's referring to KitKat being currently only available on Nexus 5.

I found the launcher apk at this site http://www.droid-life.com/2013/10/3...om-the-nexus-5-dump-search-launcher-and-more/

It has the "Ok Google" voice feature. It works, it makes the top/bottom bar transparent. The bugs I see are going from portrait to landscape or going home from apps launcher the keyboard will pop up and in landscape the text do not display properly.
[Nexus 7 (2013) Android Development] GTMoraes:
Well, you can use the Ok Google on Google Now screen, which is readily open by holding Home and swiping up to the little Google that appears
[Nexus 7 (2013) Android Development] nbehary:
The latest Search App update fixes just about all of the issues with the GEL on the Nexus 7. The only thing left is it won't size widgets right in Landscape, but adjusting them in Landscape sticks. The Search Bar is also a bit annoying in Landscape as it covers the top row of things. I assume that's not by design.
[Nexus 7 (2013) Android Development] LoopDoGG79:
It doesn't work well in landscape because it's made for the Nexus 5 screen size.
[Nexus 7 (2013) Android Development] Scott:
I think you guys are in the wrong thread. This is a thread about building Android from source. I think you want the other KitKat thread that I have or even the General forums.

Yeah, but thats no fun. I want what is rightfully ours :fingers-crossed:
[Nexus 7 (2013) Android Development] TheDarkDefender:
Factory images and Binaries are out !!! :D :D yaayy!!
[Nexus 7 (2013) Android Development] Scott:
SWEEEEEEET!

Let the AOSP'ing begin!
[Nexus 7 (2013) Android Development] TheDarkDefender:
GET WITH IT ALREADY!

https://developers.google.com/android/nexus/drivers#razorkrt16o :P
[Nexus 7 (2013) Android Development] Scott:
Dude...

I just built a rom earlier today to see if they updated...

and then I sw your post and re-synced...

We are not officialy at 4.4_R1.1!!!!!!!!!!!!!!!!!

YES!

Re-Syncing New ROM Soon!
[Nexus 7 (2013) Android Development] nbehary:
I built 4.4_r1.1 and a few notes. (well 2). It doesn't appear to need the vendor keyfiles anymore. I didn't actually think to look for them, built a fresh tree had a completely unrelated bootloop* that included a dialog about a keymaster problem, so I added them and built again. Settings->security works fine on the one built without.

The location fix is still required. (I'm guessing that's always the case. Still new to this) Still actually rebuilding after doing that, but everything else I checked seemed fine. (Camera, Wifi, ran some apps) Now was really broken and it didn't do that before w/o working location, but it may be related. Or I have the problem that's been floating around on the N5 with Now which would be awesome!

*- didn't factory reset coming from Stock. I know better.
[Nexus 7 (2013) Android Development] Scott:
Yeah, I was just going to say that about the keymaster files. Finally they fixed it, lol :good:

I think you will always need the location addition in the framework.
[Nexus 7 (2013) Android Development] nbehary:
Yeah, I figure it makes sense that AOSP would not ever have Play Services as a Location Source. The Now problem apparently was Location not working. Like I said that's odd because on 4.4r_1 w/o location working it still did everything that didn't need location. Oh well.
[Nexus 7 (2013) Android Development] Scott:
It can still gather some location data from the AOSP location service. But on earlier builds I noted the same thing you did.
[Nexus 7 (2013) Android Development] nbehary:
Yeah, it did seem less broken w/o the Play Services Location than before. (except for Now) I didn't really play around with that much though. Once I was sure it wasn't completely working, I went to fix it.
[Nexus 7 (2013) Android Development] Scott:
Damn, I got it rebuilt again but I forgot to add the line to mount as MTP.

persist.sys.usb.config=mtp,adb

Other than that it came out great!

EDIT: I know fully understood what Jack meant when he said prepare to bang head against wall many times. :o :good:
[Nexus 7 (2013) Android Development] nbehary:
Where does that go? I had no idea about it. (And wondered about that defaulting to off, but never enough to try and change it.)
[Nexus 7 (2013) Android Development] Scott:
I just put it in the device's default prop although it really should be in the boot.img.

However, I dont know how to add it to boot.img so I just add it to default prop underneath the only other line there (network something).
[Nexus 7 (2013) Android Development] Scott:
Posted PureROM-11-14-2013

Changes

Updated to KRT16O

Camera and all other features seem to work

Removed my personal Build folder as they seemed to have fixed the issue with AOSP

Removed my Gapps and linked to PA GApps until I have more time to make my own.

Everything "seems" good!

Edited Build Guide to reflect most current Repo
[Nexus 7 (2013) Android Development] MRobbo80:
Have a question where do i place the Proprietary binaries? and also can I cherry pick things like ROM control from aokp into aosp and so on. Manny thanks MRobbo
[Nexus 7 (2013) Android Development] Vaykadji:
Java6 is outdated, I recommend to install oracle-java7-installer to get the latest update (u45 at the time).

the command "java -version" is pretty useless since it will only show what version of java you are running.
[Nexus 7 (2013) Android Development] Reginald476:
Extract the .sh files to the root of your AOSP and then do a ./vendor-file.sh, as long as AOKP has updated the framework for 4.4 you should be able to no problem, if not it might get messy with changes. Personally I learned a lot from watching Rascarlo's GIT

Have you tested a build with java7? I think the command is more to verify that java was installed properly and the path was set.
[Nexus 7 (2013) Android Development] Scott:
Thanks but last time I tried AOSP wont build with Java 7.

Thanks though!

Yep! Exactly!
[Nexus 7 (2013) Android Development] Reginald476:
Scott, thank you so much for this, between you, Jak and others I was able to build for the first time and now I am trying to get that hang of GIT now.
[Nexus 7 (2013) Android Development] Scott:
If you learn git, let me know. I cant understand it.
[Nexus 7 (2013) Android Development] Reginald476:
I am stuggling pretty hard with it right now but [MENTION=3544509]eagleeyetom[/MENTION] has a great set of posts. The part I am having the most trouble with is merging other users changes into my pure build enviroment. I am sure Jak or DJ have a much better handle on it as I am using their githubs as templates.
[Nexus 7 (2013) Android Development] jakdillard:
Git learning is easy it only requires patience and vodka .... honestly until you are comfortable build and manipulating the source on your own I wouldn't worry about learning how to "cherry-pick" because "picking" out of someone else's source may cause conflicts which require basic knowledge of java and C to correct, but anyway I posted a few pages back the links to the "How-to's" I used to learn Git and Github. It may be time for someone to have their rom separated from the learning guide .....................................
[Nexus 7 (2013) Android Development] Scott:
Yeah, I am pretty happy just building and making a working ROM for :highfive:
[Nexus 7 (2013) Android Development] TheDarkDefender:
This is a great place to start and where I started. :)

http://xdaforums.com/showthread.php?t=1877040

Btw, the newest build is running great, a google now update now solved the launcher-keyboard pop up issue. I've been playing for a while and have found zero issues. KRT16O is a winner :D
[Nexus 7 (2013) Android Development] duryard:
[MENTION=426561]scrosler[/MENTION] Hi Scott. Are you going to update clean rom to kit kat. :)
[Nexus 7 (2013) Android Development] LoopDoGG79:
Here's a little XDA non written rule,

Dont ask for ETA's!
[Nexus 7 (2013) Android Development] Scott:
I am but I dont know when. I work all this weekend.
[Nexus 7 (2013) Android Development] duryard:
No rush. Your work is worth waiting for :0)
[Nexus 7 (2013) Android Development] madhartigan:
sorry for the basic questions:

1) do I select aosp_flo-userdebug when using the "lunch" command?

2) now that I can build, where can I find advice on tweaking my build.prop, etc. I know I could google this information, but I'd prefer suggestions from the respondents of this thread so I'm "on the same page" with you guys.

Huge thanks for this scrosler!! Great basic guide!!
[Nexus 7 (2013) Android Development] Reginald476:
1) Yep, that is the one I used to great effect.

2) I am not sure what you are looking to do to your build.prop but I would say look at Rascarlos, Jak or DJL's GIT, they are kind enough to label all of their commits. That's what I am doing right now.

[MENTION=632469]jakdillard[/MENTION] That's what I did for my first build I guess I will just keep doing it for now and push my changes so I can use them. I will have to go back and take a look at your post about GIT.

The thing I am still struggling with is including SuperSU in my build, I put the APK in /system/apps and that worked just fine but the su in /system/bin didn't, I ended up having to flash the ZIP. Note that I add the files to the completed ota.zip manually.
[Nexus 7 (2013) Android Development] madhartigan:
Thank you for the quick reply!!

I guess I'm just looking to customize my ROM. Such a general statement. I know. I guess my question should be . . .

"Now that I can build my own AOSP ROM, what are my next steps for further advancement of my understanding." (again, a broad question, but my competence of this stuff is only at the beginning stages and I'm not 100% sure what I should even ask)

I had very little difficulty following the guide in post #2. Every step made sense to me. I'm looking for a more in-depth understanding than "makes sense".

I'm looking forward to growing my understanding as I progress. I've tried multiple build guides and would often run into challenges. This was the first that has been maintained properly enough to get me through it without a hitch. (thank you scrosler)

Thank you again for the reply.

ADD: I'll check that "set of posts" to get a better understanding of how Git may help. I'll take a look at the "How to"'s linked by [MENTION=632469]jakdillard[/MENTION] as well.
[Nexus 7 (2013) Android Development] jakdillard:
or you use this example:

PRODUCT_COPY_FILES := \

vendor/jd/common/proprietary/Superuser.apk:system/app/Superuser.apk \

vendor/jd/common/proprietary/sysinit:system/bin/sysinit \

vendor/jd/common/proprietary/00tools:system/etc/init.d/00tools \

vendor/jd/common/proprietary/01su:system/etc/init.d/01su \

vendor/jd/common/proprietary/install-recovery.sh:system/etc/install-recovery.sh \

vendor/jd/common/proprietary/.has_su_daemon:system/etc/.has_su_daemon \

vendor/jd/common/proprietary/.installed_su_daemon:system/etc/.installed_su_daemon \

vendor/jd/common/proprietary/busybox:system/xbin/busybox \

vendor/jd/common/proprietary/daemonsu:system/xbin/daemonsu \

vendor/jd/common/proprietary/su:system/xbin/su \
[Nexus 7 (2013) Android Development] Reginald476:
What I did was look through Jak's and Rascarlos Githubs and edited the files in the same way they had, it allowed me to understand the structure of the source and what files do what. I am not sure if there is a better/easier way. I was able to add the Advance Power Menu and I am working on flipping the toggles interaction (so it is on/off with a press and settings with a long press)

Awesome, thank you so much! I am still going through and trying to figure out how Github and the source match up.
[Nexus 7 (2013) Android Development] madhartigan:
This seems to be my hurdle. I've got github up and running and I've got my id_rsa key linked, etc.

I'm just unsure what to even *start* looking at for comparison. You've already done more than expected with pointing me in the right direction. I'm definitely in the category of "knows enough to do some damage", but it stops there. Damage is really all I can do ATM. I need to reign in my learning and get some solid fundamentals.

I'm just unsure of what "back to basics" guide would be a good launchpad.

Is there a benefit to working with an IDE or should I just stick with using vi and the terminal?

Is the "repo sync" command similar to "git clone"? Is the difference that they're pulling code from different sources, but essentially the commands serve the same purpose?

Another challenge is the ubiquitous nature of the Android Kitchen in all of the guides I'm finding.

Not really looking to learn this with a crutch.