yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Ryther:
[MENTION=2033478]Yank555[/MENTION] Hi Yank, I've tried to compile your sources for hammerhead, first time the build failed at the end (forgot to save the error, stupid me), then I tried to build again right away and the process completed without error; sent the zip to my phone, flashed the rom after a full wipe, but the phone remain stuck at the google logo.

I tried to build for hammerhead to check if everything was fine because I want to build for bullhead and here my real question: I saw in your manifest that you have the repos for device and kernel and I want to ask you if it's safe to build or I need some modification or other repos; I want, also, to build your kernel for bullhead, it's that possible? Or I need too much knowledge to port it? I'm a total newbye, trying to learn something :D

Now I'm in the process to re-download (again :silly: ) all the sources to try again with hammerhead.

Thanks in advance!
[Android Builders Collective] Yank555:
Building hammerhead should work out of the box on a repo sync. I suppose you have an updated bootloader ?

Maybe try to "make clean" and rebuild to run into the error again and post it here (the last few pages of the output).

If you want to build for bullhead, you will have to do a few things :

- complete device_lge_bullhead (it's stock AOSP, haven't done anytning since I don't have a 5x to play with)

- add the kernel repo for bullhead

- vendor for bullhead may as well be missing or not be uptodate

If you want my kernel, that'll be a way more complicated task, you'd need to port the kernel, which will not be easy, I expect bullhead to be Linux 3.10.y where hammerhead is 3.4.y. That will be a huge amount of stuff to adapt... plus for CPU related stuff, 5x is a big.little device, and stuff from hh needs to be adapted to that, too.

JP.
[Android Builders Collective] Ryther:
Yeah, I updated bootloader and radio before installing the rom (I'm on kitkat, LP and above eat at my battery twice as fast).

Tonight I tried to build for both hammerhead and bullhead, hammerhead managed to build (I redirected stderror to a file with 2> and it's a whopping 1,9mb file) but bullhead stopped right away with this error:

build/core/tasks/vendor_module_check.mk:63: *** Error: vendor PRODUCT_COPY_FILES file "vendor/lge/bullhead/proprietary/bin/ATFWD-daemon:system/bin/ATFWD-daemon" has unknown owner. Arresto.

I did a make installclean before building for both device, is the same?

Now i will try to modify my local_manifest with this and retry:

<remove-project name="device/lge/bullhead" />
<remove-project name="device/lge/bullhead-kernel" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" />
<project name="flar2/bullhead" path="kernel/lge/bullhead" remote="github" />

but I think it will stop because vendor/lge is already present, there is a way to remove only the vendor/lge/bullhead (your sources already have it) and add only the bullhead from TheMuppets instead of all the devices?

I've tried without success.

Thank you very much for you support, is very appreciated! :highfive:
[Android Builders Collective] Yank555:
Not really ... I could update vendor lge for bullhead if you want, or you could pull vendor lge from PureNexusProject.

I'm also not sure using CM will work, rather use PureNexusProject device and kernel repo, those are AOSP, I expect CM to be CAF and loaded with CM stuff that may cause more bad than good.

JP.
[Android Builders Collective] Ryther:
You don't have to do it if you don't maintain the device, I will use PureNexusProject as you suggested.

As I know CM is not using CAF anymore for standards build, but I'm not a fan of CM so if I can avoid their repo I'm more than glad :D

I've modified local_manifest like this:

<remove-project name="YAOSP/vendor_lge" />
<remove-project name="device/lge/bullhead" />
<remove-project name="device/lge/bullhead-kernel" />

<project name="PureNexusProject/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="mm" />
<project name="PureNexusProject/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" revision="mm" />
<project name="flar2/bullhead" path="kernel/lge/bullhead" remote="github" revision="ElementalX-2.00" />

My only concern is that in this way I lose your vendor/lge/hammerhead or it's not a problem?

Now I'm synching, I hope everything will go as planned :o
[Android Builders Collective] Yank555:
Nope, it's PureNexus sourced anyway ;)

If you use a different kernel, you may need to update device repo to point to the correct defconfig, and you should be good ;)

I'll keep bullhead in vendor lge in the future, even if I don't use it, it's no additional work, just need to remember lol

JP.
[Android Builders Collective] Ryther:
For "pointing to the correct defconfig" you mean I need to modify device/lge/bullhead/BoardConfig.mk and set TARGET_KERNEL_SOURCE to the directory of my custom kernel?

Before your reply I tried to build again after the repo sync and got the same error as before:

build/core/tasks/vendor_module_check.mk:63: *** Error: vendor PRODUCT_COPY_FILES file "vendor/lge/bullhead/proprietary/bin/ATFWD-daemon:system/bin/ATFWD-daemon" has unknown owner. Arresto.

I've tried to google about it but cannot find a proper solution. Maybe I don't search the right thing, I'm still new in this line of work :silly:

EDIT: found a workaround, trying it: set PRODUCT_RESTRICT_VENDOR_FILES to false in device/lge/bullhead/aosp_bullhead.mk
[Android Builders Collective] Yank555:
Kernel, the folder should be fine as you pushed it to kernel/lge/bullhead in your manifest I suppose. It's the defconfig that may need changing, here's the line in my angler repo :

https://github.com/YAOSP/device_huawei_angler/blob/YAOSP-MM-6.0.1_r24/BoardConfig.mk#L42

As for the other error, that's because the owner isn't indicated in the vendor scripts, you'd need to add it there like this :

https://github.com/YAOSP/vendor_htc/commit/7c9c4f28fd53b042893c881596523c9d869b1b68

JP.

EDIT :

I just checked, my lge repo is uptodate, I've just added the missing owenership stuff for bullhead and pushed the commit.

So if you want, you can use YAOSP_vendor_lge and that should be good ;)

--> https://github.com/YAOSP/vendor_lge/commit/54bf99e613ccabd52a791b42545bce7f8ffc8883
[Android Builders Collective] Ryther:
Thank you for your help and dedication! defcoinfig was already ok, i just rendamed " " to ":lge " in the bullhead_vendor_blobs.mk :fingers-crossed:

Now off to build, hope I get to compile completely without problems before my new bullhead arrives ;)

Will report back, if it's needed I will host the build for anyone who's intrested, if it's not a problem for you!

EDIT: [MENTION=2033478]Yank555[/MENTION] the commit is missing the framework/Android.mk with the proper owner ;)
[Android Builders Collective] Yank555:
Aha, thanx, missed that one ;)

I've added it and repushed.

JP.
[Android Builders Collective] Ryther:
Good news, the hammerhead build is rocking on my phone ;)

Now bullhead compiling without problem! Thank you for all the help! :highfive:
[Android Builders Collective] Mrcactuseater:
Bullhead YAOSP? O boy!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Android Builders Collective] Ryther:
Sorry to let you down, but the compilation failed, I think because of the kernel. After I tried to sync using vendor from Yank and kernel/device from PureNexusProject, I had problem on bullhead not pulling files; now I'm in the process to download again all the sources, I hope to get rid of this problem.

[MENTION=2033478]Yank555[/MENTION] here the errors log, if you don't mind to point out the problem :good:

build_bullhead_stderr
[Android Builders Collective] mslatter:
PureNexus Mod for shamu, all thanks to PureNexus Team and Ezio's mods.... none of my enjoyment for building (which I hardly do, just syncing and running a command) would be possible with out them, so thanks so much to all.

https://www.androidfilehost.com/?fid=24459283995316731

I flashed ROM, Slim Mini Gapps 04/08 and SuperSu 2.17. Running smoothly based on all their fantastic work.
[Android Builders Collective] Yank555:
Looks like linker couldn't find some of the references while compiling kernel ... this is odd ... esp. it looks like it expects stuff that's not in a stock kernel :

drivers/built-in.o: In function `wake_presspwr':
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:62: undefined reference to `pwrkey_pressed'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:62: undefined reference to `pwrkey_pressed' drivers/built-in.o: In function `fb_notifier_callback':
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:179: undefined reference to `pwrkey_pressed'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:179: undefined reference to `pwrkey_pressed' drivers/built-in.o: In function `wakefunc_rtc_start':
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `dt2w_switch'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `dt2w_switch'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `s2w_switch'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `s2w_switch'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `camera_switch'
/home/ryther/android/YAOSP/out/target/product/bullhead/obj/KERNEL_OBJ/../../../../../../kernel/lge/bullhead/drivers/input/touchscreen/wake_timeout.c:81: undefined reference to `camera_switch'
make[2]: *** [vmlinux] Errore 1 make[1]: *** [sub-make] Errore 2
make: *** [TARGET_KERNEL_BINARIES] Errore 2
make: *** Attesa per i processi non terminati....

This looks like wake gestures, which I do not think would be in PN kernel (I may be wrong here), but would be in flar2's kernel.

I have a feeling the defconfig you point to is not the correct one.

Just odd it wouldn't compile with stock defconfig, #ifdef's in the kernel code should avoid such issues... but well. that's not the topic here ;)

I'd really use device and kernel repo from PureNexus 1:1 as is at first, and once that works give a custom kernel a go, taking one step at a time.

JP.
[Android Builders Collective] Ryther:
Thank you Yank for the tip, tonight I have resynched the sources from scratch using PN kernel, let's see what happens ;) will look more in depth about defconfig :highfive:

EDIT: [MENTION=2033478]Yank555[/MENTION] I'm trying to figure out the defconfig error, looking at your angler examples I can see that you put angler_defconfig in TARGET_KERNEL_CONFIG with kernel/huawei/angler as TARGET_KERNEL_SOURCE; in my last building (the one with flar2 kernel) I had the same but for bullhead but still got that error. When i try to look at the source tree I see that no defconfig is present, but I can see it in the arch/arm64/configs subdirectory; I think this subdirectory is automatically referenced to when the kernel is compiled? Now I'm compiling with PN kernel, defconfig is correct (I've already synced it in kernel/lge/bullhead), let's see what happen! Thank you very much for all the help you are giving to me :highfive:
[Android Builders Collective] Yank555:
When I look back when I made kernels, I would always add ny own defconfig, I would call it yank555_defconfig or sth, so maybe it's the same for flar2.

JP.
[Android Builders Collective] Ryther:
Yeah, found it! I'm learning a lot thanks to you!

Next time I will try again with a custom kernel to see how it goes!

Now I'm in the process to learn how to add features, I want to add volume wake, at least for hammerhead (since the 5x have the fingerprint scanner) :good:

EDIT: bullhead built correctly! But my cellphone will be delivered tomorrow instead of today :( so I have to wait before testing the ROM out.

EDIT2: now I'm in the process of trying to build with SaberMod 4.9 + custom kernel (ThugLife) just to see if I can, this is the simplest mod I can try at the moment. Wanted to try JustArchi optimizations but it's a little too hard for now :silly:

EDIT3: [MENTION=2033478]Yank555[/MENTION] build failed with this errors build_bullhead_stderr

I checked online but on mobile is hard. I found that is probably an error with defconfig, but this time I have correctly set the defconfig, both source and file (synced the custom kernel in another directory and pointed TARGET_KERNEL_SOURCE to it, also changed the TARGET_KERNEL_CONFIG to thug_defconfig). If you have time, can you enlighten me? I restarted the make dist command without a clean and now is compiling. After the error I checked and the out/target/product/bullhead/obj/KERNEL_OBJ directory was there.
[Android Builders Collective] coolek33:
Hey [MENTION=2095315]ezio84[/MENTION]. How things going? Where's my freaking 2g/3g toggle? ;) just kidding of course. But maybe you accomplished something in that matter? Luv your last build BTW. Thanks.
[Android Builders Collective] Yank555:
I won't be of much help on toolchains, last time I played with alternatives was a few years ago when 'linaro' was THE thing ;)

My conclusion was that playing with toolchains wasn't worth my time, no real life benefit (to me) and added hassle to get it to compile (back then I only compiled kernels)... changing toolchain may imply to have to adapt things in the code to get it to compile.

So given my conclusion, I shut that book and never looked back ;)

JP.
[Android Builders Collective] DroidIt!:
Heya fellas, just wanted to pop in and see how everybodies doing. :) All good I hope. :)
[Android Builders Collective] Ryther:
I think I did the step longer than my leg ;) I try to remove the toolchain and see if the problem is the kernel and report back.

I'm just trying different stuffs just out of curiosity :fingers-crossed:
[Android Builders Collective] formicae:
[MENTION=2033478]Yank555[/MENTION] I'm curious about the charging rates displayed on the lockscreen, are they 'canned' with a handful of presets, like USB/wireless/'fast'? The reason I ask is that I've only ever seen 1024mAh and 700mAh (or thereabouts, I see that one when I charge wirelessly), no matter which chargers I use, some of which are 2A+ chargers (though I think Hammerhead can only charge up to 1.5? 1.7?).

Also, hope YxY pattern lock is still on the to-do. :)
[Android Builders Collective] efan3719:
all is good here. :good:
[Android Builders Collective] indian84:
All good. Thanks for breaking 24 hours of silence in the thread.
[Android Builders Collective] ezio84:
All fine here too, enjoying sunny days after a lot of rain :D

I didn't take a look at the tile yet[emoji14]
[Android Builders Collective] Yank555:
The rate is when the kernel negociates with the charger and expexts to be able to pull.

Now if you have a hh, and you use my kernel, you'll have my fasrcharge in, which will allow for more.

The result hence will depend on the combo device/cable/charger.

hh should be able to pull more than 1024 indeed.

The rating of a charger just tells you how much it can give, but how much is drawn is decided by the device, so charger rating should always be more or equal to device expectations.

And then there are the various fast charge / quicl charger etc. by various OEMs / qualcomm ... making it harder, where rating is not enough to have it charge faster ;)

JP.
[Android Builders Collective] DroidIt!:
Same exact thing here too [MENTION=2095315]ezio84[/MENTION] :) Rained for about a week and a half, literally and finally started getting some sunshine yesterday. My dogs have been REALLY restless. I'm taking a 5 day road trip with them starting tomorrow :)
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION] did you see MOB30D is released on google factory images?
[Android Builders Collective] Ryther:
Built YAOSP hammerhead with UBERTC without errors andò working great on my phone :fingers-crossed:

The previous error was due to the kernel.

Bullhead is building now, finally the phone arrived, later this evening I will flash it and finally I will test if my project really works :highfive:
[Android Builders Collective] Mrcactuseater:
If you need a tester I'm here for ya man!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Android Builders Collective] Yank555:
Yep ... even sync'ed the source, but eventually it's not interesting ... it's an evolution of r17 (MMB29V) which lies behind codewise to MHC19Q ... even if versioning may seem otherwise.

I don't understand what Google is doing, pushing forward 3 branches, one for this year's Nexus'es, one for older Nexus'es and one for Pixel C !?

Only benefits we can take from this would be kernels for older Nexus'es and possibly vendor stuff.

JP.
[Android Builders Collective] adm1jtg:
Well the one takeaway I saw from this build was that it includes an updated modem... course its appears to be the same modem as included in N preview.... but even so haven't seen a new modem in a while.
[Android Builders Collective] Yank555:
Interesting, MHC19x brought the N preview modem to MM for angler (bullhead ?)...

I wouldn't be surprised if that modem worked fine with MHC ROMs.

JP.
[Android Builders Collective] adm1jtg:
Well since i have the new 34 modem loaded and am running it so far with no issues on yasop 110 i would agree :D
[Android Builders Collective] Ryther:
Get ready to party ;) I've installed successfully the ROM on my bullhead, now I'm rocking on YAOSP :highfive: and soon the UBERTC compiled version will be done, I will try and upload that one, if [MENTION=2033478]Yank555[/MENTION] have no problem with that ;)

After this I will try with a SaberMod version, just to try. Now I want to add [MENTION=2095315]ezio84[/MENTION] 's build if my virtual machine space is still enough :D

Obviously a very big big big thank you to Yank, who assisted me on the process to start again in the android compilation world! :good:
[Android Builders Collective] Yank555:
Glad I could help ;)

And sure, no problem at all with pushing builds, that's the whole point of open source :good: ;)

JP.
[Android Builders Collective] theesotericone:
That's pretty how everyone feels about it at this point. I wonder if Google even knows what it's doing with android anymore? lol
[Android Builders Collective] omaralkha99:
wheres the nexus 6 builds?
[Android Builders Collective] dorqus:
If you are willing to share your bullhead build, I would love to give it a go! Thanks.
[Android Builders Collective] adm1jtg:
Yank555 explained earlier that the build base for his 1.10 yasop is actually newer code then the new nexus build that just dropped (MOB30D) at least in the case of shamu (nexus 6)
[Android Builders Collective] Yank555:
r31 aka. yet another new tag M5C14J, is latest Pixel C branch and just dropped. It'd be almost funny if it wasn't misleading ;)

JP.
[Android Builders Collective] Ryther:
[MENTION=6262409]Mrcactuseater[/MENTION]

ROM compiled and is booting on my bullhead. Now I'm uploading it on Google Drive while I wait for a developer account on androidfilehost :fingers-crossed:

You will get it here when it's uploaded: https://goo.gl/RZPZnX

I live in Italy and not in a big city, so my connection is a crappy one. I'm dedicating 20 Kb/s for the upload, so expect it at least in 5hrs :silly:

What you get: simply a YAOSP 1.10 for bullhead with PureNexusProject kernel, both compiled with UBERTC 4.9.3 :good:

Also, someone care to explain to me how the vendor partition works?
[Android Builders Collective] Mrcactuseater:
Excellent news [MENTION=814632]ryh[/MENTION]ter, I'm ready and waiting!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Android Builders Collective] Ryther:
[MENTION=2911026]dorqus[/MENTION]

Rom it's up!

As usual, I'm not responsible for damaged devices, lost work, third world war and bla bla bla :D

Download both ROM and md5 here, check it, make a backup and clean flash! :thumbup:
[Android Builders Collective] Mrcactuseater:
Excellent stuff!

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Android Builders Collective] dorqus:
Thank you - I'm downloading now - will try and flash tonight! - It's still early afternoon here in the US :)
[Android Builders Collective] ezio84:
PureNexus mod 6.0.1-20160413 :D

Download for Hammerhead: https://www.androidfilehost.com/?w=files&flid=50100

Changelog:

Add manual pause/resume downloads (tap on the download notification to open the download manager, then tap on the entry in the manager to pause/resume it)

QS Customization improvements by [MENTION=4527723]gmillz[/MENTION] (in the QS customizer, drag main tiles down on the 2nd row to disable the first main tiles row - drag again a tile into the first row to enable the main tiles row - up to 3 tiles in the main row - QS code cleanup and fixes)

Add explanation for customizing apps under PNSettings->Display->Notification light->Apps when no apps are added yet

Don't play sound effects if stream is muted (stop turning on the audio hardware and playing silence)

Code cleanup in the framework

From last PN source:

HeadsUp snooze function (swipe up the app heads up to snooze it for that app)

PureAmbient: cleanup for non pickup sensor

Update chromium-webview arm/arm64 to 49.0.2623.105

hammerhead: update blobs for 6.0.1 (MOB30D)

Installation, tips, info: check the 6th post of this thread: http://xdaforums.com/showpost.php?p=55121776&postcount=6

PS: if you have problems, call A-team or clean flash.

Here's a good post by JBQ:

https://plus.google.com/+JeanBaptisteQueru/posts/akHWypRNEn3

The drawback is you have to flash a vendor img that matches your build version, to avoid a mismatch error at boot (furthermore you can have issues with apps like Google Camera due to old vendor blobs).
[Android Builders Collective] Garrykd:
...and the Angler version ;) https://www.androidfilehost.com/?a=show&w=files&flid=52030

.
[Android Builders Collective] efan3719:
and my axe... i mean here's the flo version. :silly: https://www.androidfilehost.com/?fid=24499762635999339
[Android Builders Collective] Ryther:
Thank you ezio, sorry but I saw only now that you quoted me :silly: I will read right now!

I have another problem, nandroid backups are massive, over 8gb! In TWRP I see "system" (1gb) and "system image" (3gb), I really need to backup both? :eek:
[Android Builders Collective] adm1jtg:
Sounds like you need to turn compression on for backups
[Android Builders Collective] Phazmos:
As mentioned, use compression, and no need to bu "images".

You'll be less than half that - with 65 apps, I'm under 2 gigs.
[Android Builders Collective] Ryther:
Thank you, coming from hammerhead and never saw the image partitions :silly: I had a clue about them, but I wanted to be sure ;)

Now is done, 2.4gb down from 4.5gb :highfive:
[Android Builders Collective] NHNXDA:
May I ask, does your rom have volume button wake option selectable, yanks rom is great but I rely on that option often.

I'm finding my N5 rather sluggish with the latest 1..10 yank rom, is there an app to track this down or built in service thats shows whats eating cpu/memory to make it so sluggish.

TIA.
[Android Builders Collective] indian84:
PN mod has the Volume Wake Option for 6P. I'm sure Hammerhead build should have this option too.