yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] sykopompos:
Easiest way would be to go into your vendor folder, make a folder called lge, then CD into that and then clone it. When that is done you will have a folder called vendor_lge_hammerhead there, just rename it to hammerhead and you are good to go.

I'll cover how to modify the manifest at some point to show how to have it fetch when you repo sync.

If you have any existing vendor files extracted though for hammerhead, especially the ones from the nexus binaries page, you will want to remove them since it will try to pull from both sets for hammerhead and they will conflict and u will get build errors
[Nexus 7 (2013) Android Development] JamFan05:
Thanks for the help. I did exactly what you said and it built. But when I flashed it I got com.Qualcomm.timeservice fc and camera fc.
[Nexus 7 (2013) Android Development] sykopompos:
I reverted those changes I made with the updated binaries, they were causing those issues because they are for the master branch with a bionic commit that we don't have in 5.1
[Nexus 7 (2013) Android Development] 7786:
Hey everyone,

I followed this guide and was able to successfully compile an AOSP 5.1 ROM for my nexus 7, was even able to include some cherry picked features in there. My problem is, the tablet keeps rebooting every 15 minutes throwing this error:

E/Sensors ( 1573): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1573): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1573): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6f959d0
W/Sensors ( 1573): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1573): sns_debug_main.c(565):Debug Config File missing in EFS!
E/ ( 184): invalid crash request of size 4 (from pid=1573 uid=0)
E/Sensors ( 1602): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1602): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1602): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6f1b9d0
W/Sensors ( 1602): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1602): sns_debug_main.c(565):Debug Config File missing in EFS!
E/ ( 184): invalid crash request of size 4 (from pid=1602 uid=0)
E/Sensors ( 1612): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1612): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1612): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6fe59d0
W/Sensors ( 1612): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1612): sns_debug_main.c(565):Debug Config File missing in EFS!
E/ ( 184): invalid crash request of size 4 (from pid=1612 uid=0)
E/Sensors ( 1621): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1621): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1621): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6fb89d0
W/Sensors ( 1621): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1621): sns_debug_main.c(565):Debug Config File missing in EFS!

This problem seems to go away if I flash a different kernel, however I didn't even touch the stock kernel. All I did was add a few settings features, included the 5.0.2 blobs from googles website, and that was it. Tried searching but only found few people with this issue and no one seemed to have a solid solution. Anyone run into this one before?
[Nexus 7 (2013) Android Development] BreckZeBoulay:
This topic is sleeping :p

Can someone explain me this error when I try to sync the new AOSP 6.0.0_r1 :

pierre@salon:~/Android/AOSP$ repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
fatal: Couldn't find remote ref refs/heads/android-6.0.0_r1
Unexpected end of command stream
fatal: cannot obtain manifest https://android.googlesource.com/platform/manifest

All is fine when I sync 5.1.1_r24
[Nexus 7 (2013) Android Development] GROGG88:
Its not released yet. Trust me, I'm watching:

https://android.googlesource.com/platform/manifest/
[Nexus 7 (2013) Android Development] BreckZeBoulay:
https://android.googlesource.com/device/lge/hammerhead/+/android-6.0.0_r1

and

https://android.googlesource.com/device/lge/hammerhead/

I wait ^^
[Nexus 7 (2013) Android Development] GROGG88:
Its up now
[Nexus 7 (2013) Android Development] Methanoid:
Cool. Pity you closed your Rom thread as it was a useful way to follow new rom news. Now we have to keep checking all threads to see your name next to a 6.0 Rom....
[Nexus 7 (2013) Android Development] Scott:
I have updated the build guide to 6.0.0.

No ROM is posted at this time. Im not a fan of 6.0.0 (yet).

If you build a ROM and want to share feel free to do so...
[Nexus 7 (2013) Android Development] sykopompos:
But I'm a fan of 6.0.0 though
[Nexus 7 (2013) Android Development] Scott:
Meh. I just dont like all the SELinux stuff. Otherwise its a nice update. Should have been 5.2.0 though.
[Nexus 7 (2013) Android Development] sykopompos:
Yeah, it really wasn't a huge update from lollipop.

The selinux stuff was there, Google was just slow to merge it in though
[Nexus 7 (2013) Android Development] Scott:
You know, they could have added a "clear all recents" That would have been the biggest improvement for me.
[Nexus 7 (2013) Android Development] sykopompos:
Meh, recent are supposed to be for easy recall since there isn't a memory leak in marshmallow, it is how it is supposed to be
[Nexus 7 (2013) Android Development] Scott:
Yeah, but I am OCD. Its more aesthetics for me.
[Nexus 7 (2013) Android Development] sykopompos:
I'm a slacker so it fulfills my laziness seeing it all full ?
[Nexus 7 (2013) Android Development] Scott:
Hahaha!
[Nexus 7 (2013) Android Development] Woody:
Fyi, they did include it. Just buried in the code.

http://gerrit.dirtyunicorns.com/#/c/21048

Hey Scott, Are you going to update the flashable Bootloader in the OP from 404 to 405? Saw someone on CR with a possible BL issue and then saw yours in the OP of this thread. Might be a good idea if people are needing it to flash updated M-ROMs. :highfive:
[Nexus 7 (2013) Android Development] Scott:
Yeah, good idea, I will update the op with the correct bootloader for M.

In my thread, that guy is using MultiROM. See my response there.
[Nexus 7 (2013) Android Development] sykopompos:
I know it is there and like so many other good things, all the good stuff Google pulls last minute out and make us all cry ?
[Nexus 7 (2013) Android Development] blambo:
I know!

But really, you can just install '[root] Recently' by Chainfire. It enables the same exact thing and uses less resources. Xlnt app. Secret... You can enable all of the Pro features by going into settings and checking 'Freeloader' mode.
[Nexus 7 (2013) Android Development] Scott:
Yes but you should support Devs... Trust me when I say we put a lot of time into this. I donate to [MENTION=631273]Chainfire[/MENTION] and buy all his paid apps. Granted most of us do this for fun :)
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Hi !

What's the difference between "userdebug_fp" and "userdebug" when we choose for for lunch ? (it's only for hammerhead)
[Nexus 7 (2013) Android Development] Scott:
Not sure myself. Maybe someone else can answer.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
A new repo command ( 1.22) is available.
... You should upgrade soon:

cp /home/pierre/Android/AOSP/.repo/repo/repo /home/pierre/Android/bin/repo

I have this remark when I sync 6.0_r26

How to upgrade to 1.22 ?

And another question... Is it possible to sync for only one specific device (only for Flo for example) ?
[Nexus 7 (2013) Android Development] sykopompos:
You answered your own question there since it tells you exactly what to do in what you linked, copy the new file to your bin/repo.

You can modify the manifest after you init and remove the devices you don't want to sync
[Nexus 7 (2013) Android Development] Scott:
Thats good info! I did not realize you could do that.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
And another noob question ! :D

How to know which version to take for a specific device ?

Again the example of Flo : https://android.googlesource.com/device/asus/flo

_r1, _r2, _r...... ?
[Nexus 7 (2013) Android Development] oops_mr_gumby:
Thanks for the build guide Scott! I haven't flashed it yet, but I did an apparently successful build of 6.0.1_r11 for flo last night. With your post and a few other tips from the official guide, it was really easy. You are awesome!

[MENTION=4913921]BreckZeBoulay[/MENTION], I suspect you've already figured this out (as the reason I just built AOSP myself for my tablet was due to my recently flashing your UntouchedAOSP build for hammerhead on my phone), but for anyone else, I figured out the correct build/tag to provide in the repo init step by consulting this[1] page on android.com.

as a new user I can't post clickable links:

[1] https: / / source.android.com/source/build-numbers.html#source-code-tags-and-builds
[Nexus 7 (2013) Android Development] ocarinaz64:
I have built lots of ROMs before, but I'm new to the Nexus 5, and also to full AOSP. Previously, I always executed "lunch...brunch..." and then flashed the output.zip. But you instruct to do "lunch... make -j6 otapackage". So then is the aosp_hammerhead-ota-eng.zip the one that you flash?

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

I didn't provide any build/tag for my Nexus 5. I just synced to the newest branch, which was android-6.0.1_r16. Now that I see that list, it doesn't list Nexus 5 next to r16. So does that mean that I need to build it with r11 instead?
[Nexus 7 (2013) Android Development] Scott:
Ok, its got about 7 minutes on the upload. Luckily I didint do a make clean before I rebuilt... And its the same file size as the Flo version. For the life of me I couldnt guess why the Deb version would be 20 megs smaller... Then when the bootloop issue occured I realized I forgot the binary files :(

Eitherway... Be back in a few minutes...
[Nexus 7 (2013) Android Development] Scott:
I just posted a new version that may or may not fix this. You may also note that it says "Untested" which means it may not work right because it hasnt been tested.

Also, just 6 posts above yours it was discussed in detail as to why this is happening. Before posting you should skim over the last few pages of any thread. You may save yourself some time and effort.

Please try the new version ASAP and report back. The future of Android depends on what YOU do right NOW ;).
[Nexus 7 (2013) Android Development] Scott:
New build for DEB is up...

AS I stated before...

Untested...

Let me know how it works... Or doesnt...
[Nexus 7 (2013) Android Development] Scott:
Anyone on Deb test yet? I see its been downloaded a few times.
[Nexus 7 (2013) Android Development] Rouz.:
Its trying to boot, wait for a minute

Edit: Up and running! Cool give me a few minutes and I report what works and what does not

Edit 2: Wifi and LTE works ... more testing ...
[Nexus 7 (2013) Android Development] Scott:
IM gonna once I find out the if the Deb version boots.
[Nexus 7 (2013) Android Development] Blagoja D.:
Camera app. Is not present and no navbar transparency
[Nexus 7 (2013) Android Development] Rouz.:
Wifi, LTE, Bluetooth, GPS, Sound, Microphone, everything's working! except for the camera! but thanks man, its awesome!
[Nexus 7 (2013) Android Development] Scott:
Ok, im going to bed....

Dont say I never did anything for you either! :highfive: ;) :p
[Nexus 7 (2013) Android Development] Scott:
No harm no foul. But it really is good practice to skim the last couple posts.

Deb version is up and confirmed working....

Enjoy!

I have a theory on cam app, I didn't check myself... However...

Because the binary / Nexus driver files are for 4.3 (they have not posted them for 4.4 yet) this may be the cause.

Lets see what JakDillard says as he as much more experience than I with AOSP.

Thanks and you too!

Peace out yall!
[Nexus 7 (2013) Android Development] TheDarkDefender:
Root and titanium restore working fine here. Thanks Scott!! ?

Sent from my Nexus 7²
[Nexus 7 (2013) Android Development] netespl:
Navbar transparency is included in Google Home Launcher which is not a part of AOSP ROM.
[Nexus 7 (2013) Android Development] jakdillard:
I Hate AOSP 4.4

I really am not liking the halfed-assness of this AOSP release Scott HUHHHHH ... but I can confirm that I've built a rom with working root and I am working on the camera issue also the browser force closes when entering AOSP's take on the incognito tab, so gotta fix that too, and Launcher3 works but half-assed thats the launcher with the transparent system bar, gotta fix it for flo though because landscape is ****ty at best so look like my weekend will be tied up but I will let you know when everything is fixed and how to fix them.
[Nexus 7 (2013) Android Development] pietropizzi:
DEB here:

Calendar opens but ForceCloses on Sync, cannot be synced via google-account settings, too.

Camera no display

Gallery --> Settings no display

and the most sad thing for me: Magnetic Cover still cannot wake up my N7 when opened :( :( - I really hoped they fix it in KK...
[Nexus 7 (2013) Android Development] lcmazza:
So far, multi touch is fixed!

Thanks! :D
[Nexus 7 (2013) Android Development] nrage23:
He is building with the 4.3 binaries so until Google releases the 4.4 binaries for the Nexus 7.2 it will be a little wonky but it is not his fault.
[Nexus 7 (2013) Android Development] iamnotkurtcobain:
So can we use those binaries for the S4 too? As it has the same Hardware .

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Nexus 7 (2013) Android Development] nrage23:
Is not the same hardware so no. Similar hardware but not the same. You cannot use a rom built for one device on a completely different device. Samsung does very strange things with their wifi drivers anyhow. The 4.4 binaries should be out in a few days so we can have a fully functional build for the new Nexus 7.
[Nexus 7 (2013) Android Development] ghost02:
Some apps including launcher pulled from Nexus 5

http://www.droid-life.com/2013/10/3...om-the-nexus-5-dump-search-launcher-and-more/
[Nexus 7 (2013) Android Development] jackxlj:
you can use the sideload wonder machine to install apks to 4.4 until the devs get the problem fixed
[Nexus 7 (2013) Android Development] oops_mr_gumby:
That's correct.

As I understand it, yes. Some of those rXX versions are just for device-specific updates.
[Nexus 7 (2013) Android Development] fhem:
As long as it built and flashed OK you should be good at r16 ---- r12 , r13, and r16 just added some stuff for nexus 9, nexus player and pixel c. You can check the changelogs here.
[Nexus 7 (2013) Android Development] oops_mr_gumby:
To see the changes from r11 to r16 you can apparently try running:

repo forall -pc 'git log --no-merges --oneline android-6.0.1_r11..android-6.0.1_r16

But I just installed a fresh OS and I don't haven't setup a build environment yet so I don't know what format the output comes in, or how useful it might be to you in this case.

I'm no expert but I have read at least one report of problems, I think it was the phone didn't work on a nexus 5 with the pixel c update rXX version installed. I suspect some combinations will work and other won't.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Hello everybody !

I change my OS from Ubuntu 14.04 to Debian Stretch.

When I start compiling, I've got this error :

You are attempting to build with the incorrect version
of java.

Your version is: openjdk version "1.8.0_91" OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-2-b14) OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode).
The required version is: "1.7.x"

However, Google recommends to install openjdk8.

Also here : https://source.android.com/source/building.html#wrong-java-version , it's written :

What's the PATH ?

I'm a "bit" lost. :(
[Nexus 7 (2013) Android Development] fhem:
Just comment out or delete these lines and it will build fine with Open 8. You will still get the warning message but it will complete the build and all will be good. The java 8 is for the master branch and N --- but MM 6.XXXXXXX will build fine with Open 8.

FYI ----> Look at lines 176 and 177

Java Development Kit (JDK)

Please note, since there are no available supported OpenJDK 8 packages for Ubuntu 14.04, the Ubuntu 15.04 packages must be installed manually. See JDK for Ubuntu LTS 14.04 for precise instructions.

The master branch of Android in AOSP: Ubuntu - OpenJDK 8, Mac OS - jdk 8u45 or newer
Android 5.x (Lollipop) - Android 6.0 (Marshmallow): Ubuntu - OpenJDK 7, Mac OS - jdk-7u71-macosx-x64.dmg
Android 2.3.x (Gingerbread) - Android 4.4.x (KitKat): Ubuntu - Java JDK 6, Mac OS - Java JDK 6
Android 1.5 (Cupcake) - Android 2.2.x (Froyo): Ubuntu - Java JDK 5
[Nexus 7 (2013) Android Development] BreckZeBoulay:
I delete the red lines and add the green lines ? (Sorry this noob question)
[Nexus 7 (2013) Android Development] fhem:
The red - is the old and the green + is the new so ...................... so you can see I simply added # at the beginning of lines 171, 192, 203 , and 219. Adding the # simply comments out that line ---> same as deleting. So you could also delete lines 171, 192, 203, and 219 and get the same result.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Ok, I test your solution in a few hours when I come back home.

Thank you !!! :)

EDIT :

[MENTION=5526655]fhem[/MENTION] : compiling in progress, thank you !
[Nexus 7 (2013) Android Development] BreckZeBoulay:
external/guava/guava/src/com/google/common/reflect/Types.java:317: error: TypeVariableImpl is not abstract and does not override abstract method getAnnotatedBounds() in TypeVariable
private static final class TypeVariableImpl<D extends GenericDeclaration>
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
1 warning
build/core/host_java_library.mk:91*: la recette pour la cible «*out/host/common/obj/JAVA_LIBRARIES/guavalib_intermediates/javalib.jar*» a échouée
make: *** [out/host/common/obj/JAVA_LIBRARIES/guavalib_intermediates/javalib.jar] Erreur 41
make: *** Attente des tâches non terminées....

#### make failed to build some targets (17:52 (mm:ss)) ####

Any idea ?
[Nexus 7 (2013) Android Development] fhem:
I haven't seen that error but it looks like a problem w/ your java.

Run each of the following from your linux terminal and post results.

java -version

sudo update-alternatives --config java

sudo update-alternatives --config javac
[Nexus 7 (2013) Android Development] BreckZeBoulay:
root@salon:/home/pierre# java --version
Unrecognized option: --version
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
root@salon:/home/pierre# update-alternatives --config java
Il n'existe qu'une «*alternative*» dans le groupe de liens java (qui fournit /usr/bin/java)*:*/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
Rien à configurer.
root@salon:/home/pierre# update-alternatives --config javac
Il n'existe qu'une «*alternative*» dans le groupe de liens javac (qui fournit /usr/bin/javac)*:*/usr/lib/jvm/java-8-openjdk-amd64/bin/javac
Rien à configurer.

First result seems not good...
[Nexus 7 (2013) Android Development] fhem:
I was wrong sorry should be------> java -version

and you look to be good with the others not sure sorry
[Nexus 7 (2013) Android Development] BreckZeBoulay:
pierre@salon:~$ java -version
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-2-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)

And yes the others are good, sorry I'm a french noob :p
[Nexus 7 (2013) Android Development] fhem:
No problem Your English is much better then my French LOL -----> I'm really not sure about that error. Which aosp branch/tag are you trying to build and for which device?? I am currently building aosp 6.0.1_r25 for N6, N6P, and N9 using java 8 w/o any issues.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
android-6.0.1_r41 for hammerhead.

before to install debian stretch I was on ubuntu 14.04 and no issue
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Attach my modded manifest, may be I delete a line......

But I done this before, and no issue
[Nexus 7 (2013) Android Development] fhem:
Hate to say it but it sounds like the problem may be with Stretch. I know there people having problems w/ Ubuntu 16.04 also. I don't plan on updating to 16.04 base until I'm sure they get all the bugs out.

Sounds like Stretch is still very new and bound to have issues.

Good luck with getting it figured out. Sorry I can't do more to help.
[Nexus 7 (2013) Android Development] BreckZeBoulay:
I plan to reisntall ubuntu 14.04 just for compiling. I hope when N will be out, issues will be solved.

Thank to take time for me ! :)
[Nexus 7 (2013) Android Development] BreckZeBoulay:
Just for information, no problem with Debian Jessie.
[Nexus 7 (2013) Android Development] Suici Doga:
I have a laptop which has AMD A8-4500M.When compiling AOSP with `-j4` it compiles really fast but it heats up to 98C and I quickly stop it?.About 2 months ago the thermal paste has been applied and the fan is clean.

when compiling on a single core the temperature is about 88C but it is slooow.

Any suggestions?

UPDATE : Reapplied thermal paste and undervolted (see https://gist.github.com/SuicSoft/ea59b5e7856bafdb6972406c4dae331d) and now it doesn't go above 80C even when compiling with 4 cores.And how can I get it to boost for longer since it doesn't overheat but still reduces speed to 1.9Ghz after 2 minutes.
[Nexus 7 (2013) Android Development] spajdr:
Thanks for making this :)

I'm sure it will be perfect in newer releases.

I tried DEB version, first problem was that BACK button does nothing when pressed.

Second was that landscape orientation have cutoff names and position of icons was wrong.

Third was most problematic, after some time, keyboard stopped from showing up.
[Nexus 7 (2013) Android Development] PR0XiMA:
Build :D

I was about to make a build for you guys here on XDA, but [MENTION=426561]scrosler[/MENTION] was earlier out. :D

But anyway, thanks for the vendor files!
[Nexus 7 (2013) Android Development] bogii4:
Security in Settings FC's so no way of installing non-market apps :/ NOT COOL :<
[Nexus 7 (2013) Android Development] Ambious:
Deb built works perfectly for me.

Back button working.

Data working.

Excellent! :D
[Nexus 7 (2013) Android Development] pandacookie:
It doesn't FC for me. Odd.
[Nexus 7 (2013) Android Development] jordirpz:
Some vídeo player that doesnt force closed please?

Enviado desde mi AOSP on Flo mediante Tapatalk
[Nexus 7 (2013) Android Development] paaaulo:
Is there any way to disable keyboard popup on the home screen (after pressing home button)?
[Nexus 7 (2013) Android Development] pandacookie:
I just flashed SuperSu. Bam. Root.

http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------

What launcher are you using?
[Nexus 7 (2013) Android Development] penguin449:
4.4 launcher, Google home one, I had the same problem... x
[Nexus 7 (2013) Android Development] pandacookie:
Oh. Because I don't have this problem with the default launcher, but I did with Google Home.
[Nexus 7 (2013) Android Development] paaaulo:
Stock.
[Nexus 7 (2013) Android Development] pandacookie:
Hmmm. Because that happened to me on Google Home. Not stock.
[Nexus 7 (2013) Android Development] ellisbodds:
Has anyone tried running a virtual machine on a Windows host with 8 gigs of RAM? I know Google say you need at least 16, but I'm wondering if that's just them trying to stay on the safe side. I could probably allocate 6GB or so to the VM.

Sent from my Galaxy Nexus