yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Ryther:
Yeah, I saw it too just now... damned afh, I tried multiple time and it hangs at 100% while "updating database"...

EDIT: using chrome did the trick, now it's up
[Android Builders Collective] Yank555:
Hmm ... just tested, works on my end. It's a file that's on github, same place as where my sources are ...

https://github.com/YAOSP/manifest#changelog

Where are you from ? I read some countries like to block github, I hope that's not the case for you...

Anyway not much I can do about it, I'm afraid.

JP.
[Android Builders Collective] swat4samp:
Hey yank, when i tried your previous build for hammerhead, i found that volume rocker wake feature is missing. Did you add it in recent build? Its very useful as i got used to it :D

PS: That link to github works, but the changelog link in that manifest shows 404 error.
[Android Builders Collective] Yank555:
Not yet for volume rocker wake.

Ah, kay, that I didn't check, gonna have a look, thanks ;)

JP.

Edit: Changelog link is fixed ;)
[Android Builders Collective] Smallsmx3:
So I installed the latest YAOSP. And I was having issues with making phone calls. I prefer the Google dialer and contacts but they did not work.....is, I could select to call someone but the call screen would not appear do I would not know i was calling someone unless I listened in the earpiece. I had the same issue in the dialer. My favorites wouldn't call anyone. I switched back to the aosp apps and they did the same thing...
[Android Builders Collective] Yank555:
Can't comment on google dialer, stock one works perfectly fine, plus you'll miss on options that are in stock dialer and not in google dialer. Maybe that's causing your issues.

I'd recommend to flash the rom again, in case you broke stuff adding google counterparts.

In general, if you mod stuff and it doesn't work, first test on a clean flash if you can reproduce the error, reverting back may not be good enough.

JP.
[Android Builders Collective] setiawanjimmy:
Go to settings, apps, settings icon top right, default apps, choose your phone app
[Android Builders Collective] Smallsmx3:
I might reflash today, I had to switch Roms because I needed my phone to work. It's odd I've never had that happen any other Rom because I prefer to use Google apps over the aosp counter part
[Android Builders Collective] mslatter:
Sorry for my Shamu being tardy. I did build this on the same day after I saw Ezio's post, but AFH wouldn't let me upload it - I tried 3 times and it would get to 100% and read "updating database" and would just sit there. Then yesterday was Cinco and some tequila was had, and I successfully uploaded it today. As always, all credit to Pure Nexus team and Ezio for his custom mods :good:

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

I'm still trying to build Slim6 thanks to Yank555's help. Still a newbie at this and I have been struggling with the local manifest. Finally realized last night I was calling for the mm tag (like pure nexus) instead of the mm6.0 ...duh! Now everything appears to by syncing properly, but when I breakfast, lunch or brunch, I'm getting errors...including permission denied errors. I 'suspect' it's because I'm trying to build Slim on a separate mounted hard drive (I'm out of space in my build environment) and it's a permissions issue..... Going to try to load Ubuntu 16.4 on the separate mounted drive, so that I can boot into it directly and create a new build environment on it. Have to copy everything off the external drive first...that's going to be the big challenge, but I'll get it done. Currently dual booting, but now will be triple booting :)
[Android Builders Collective] Yank555:
You will have less features doing that. Why exactly do you prefer Google apps ?

You will miss on stuff like proxy speaker, flip to mute ringer etc. and they are fully and properly themable without modding anything, reverse lookup etc is in...

Check the changelog and let me know what you miss in the aosp one, maybe I can add it.

JP.
[Android Builders Collective] a g bell:
[MENTION=636871]ezio[/MENTION] all seems fixed for me on latest hh nice work? no need for a song?
[Android Builders Collective] Garrykd:
I was bored (;)) and I see Ezio has made some changes. So, if you are bored here's an updated build :D

purenexus-mod-6.0.1-20160506

Changelog:

- Angler kernel: merge branch 'android-msm-angler-3.10-marshmallow-dr1.6' of aosp

- From stock PN source:

* Add a lot of new languages translations

* Update webview 51.0.2704.36(arm/arm64)

Angler download : https://www.androidfilehost.com/?a=show&w=files&flid=52030

.
[Android Builders Collective] Smallsmx3:
What does the different kernel branch offer?
[Android Builders Collective] mslatter:
Not sure if it's related but "Ok Google" didn't work for me on YOASP. Wasn't sure if it was related to GAPPS or not, until I used the same GAPPS on Pure Nexus and it works fine. That stuff is all over my head and it wasn't a big deal to me so didn't mention it. But when I saw the other Google issues, thought I'd mention it in case it helps. You have done a fantastic job on YAOSP....seriously :good:
[Android Builders Collective] Yank555:
Odd .. all of what you mention has workes since day 1 for me ...

JP.
[Android Builders Collective] mslatter:
You've probably mentioned it before but what GAPPS are you using? I used Dankoman's 4/29 mini - which I use exclusively really because they're always awesome. I use his zero on my tablet since I use my tablet for other things than playing :)
[Android Builders Collective] Yank555:
I use opengapps nano on my daily and purenexus on my test devices.

JP.
[Android Builders Collective] a g bell:
Oops spoke to soon hh is slowing down again apps taking ages to open etc
[Android Builders Collective] efan3719:
Since I cannot have [MENTION=2640853]Garrykd[/MENTION] have a build out more up to date than mine, here's the Flo version :p - https://www.androidfilehost.com/?fid=24533100289590186
[Android Builders Collective] ezio84:
https://github.com/ezio84/purenexus...mmit/c0edb9d0e39b35a4993e22e5f93bef82b8086f94

Nothing special i think

Damn it, really weird...

Did you wipe dalvik/cache/system too?

Try also removing all layers.

I'd try also to flash latest PN gapps if using any different package.
[Android Builders Collective] csolanol:
Good news for xiaomi users. Slim base is working fine with Mi 4c. Just missing hardware buttons settings and usual slim features but it can be added any time. Any help about hardware keys commits to backport from SlimLP would be really appreciated.
[Android Builders Collective] Ryther:
After more 11 hours of compiling, here it come: UBER-Phasma-eclipsActive-YAOSP-1.20!

Catch it here

You will get YAOSP with:

- Built with UBERTC 4.9 (ROM/kernel)
- Phasma built inline
- Tweaked interactive gov for battery AND performance

I've tried to compile the kernel with UTC 7.0 but failed :( will try again Monday ;)

Try to install it and don't play around with kernel, at least for cpu and i/o ;)
[Android Builders Collective] Smallsmx3:
What is phasma?
[Android Builders Collective] Ryther:
A kernel made by DespairFactor ;)

http://xdaforums.com/nexus-5x/orig-development/kernel-phasma-kernel-r1-t3245112
[Android Builders Collective] kantjer:
If you want to build Phasma kernel with Uber 7 you need to use a recent aarch64-linux-android-7.0-kernel TC. The pre-build from Bitbucket isn't building. The issue is fixed in the Uber source but no pre-build is uploaded yet.

I build Twisted with Phasma inline using my own Uber 7 TC build, thats' building just fine.
[Android Builders Collective] Ryther:
Thanks for the tip! Can you point me to a good guide to build a TC on my own? Cannot find a decent one :rolleyes:
[Android Builders Collective] kantjer:
https://github.com/UBERTC/uber-manifest

Or use my build

https://www.dropbox.com/sh/i7r0ogow2lame78/AAByDReObwqfBYPtYU6s6u7oa?dl=0
[Android Builders Collective] VictorLapin:
As [MENTION=4575569]Ryther[/MENTION] has gone experimental, I'll just leave this here:

YAOSP 1.20 MTC19T for bullhead : https://www.androidfilehost.com/?fid=24533103863137440

Included:

Pure YAOSP with status bar icons color inversion fix by [MENTION=2033478]Yank555[/MENTION] (guess it didn't make its way into "official" 1.20)

PureNexus device and kernel repos (because I'm not a device/kernel guy :p)

Bugs found:

AOSP Gallery refuses to work no matter what. I personally don't use it, so meh.
[Android Builders Collective] Ryther:
Gallery working here, and I use it. Have you tried to clean data and cache of the app?
[Android Builders Collective] VictorLapin:
Sure, first thing to do
[Android Builders Collective] Ryther:
I asked because sometimes we forget about the most basic things (happens to me :D )

Which commit did you add for the fix?
[Android Builders Collective] VictorLapin:
Well, I didn't :) Gallery is one of the apps got purged by my cleaning script. As I said, I don't use it.
[Android Builders Collective] Ryther:
I mean the fix for the status bar's icons color fix :D
[Android Builders Collective] VictorLapin:
Oh, that... :D just resync, it should be up in the sources
[Android Builders Collective] a g bell:
[MENTION=636871]ezio[/MENTION] well wiped caches and reboot all is good again ?

will let you know if it happens again but all has been good now for nearly 12hrs?
[Android Builders Collective] Yank555:
Yup, exactly, it's merged in the respective base commits ;)

JP.
[Android Builders Collective] jisoo:
You have a 32-bit SoC (i.e. not bullhead or angler)?

It seems to me that Gallery only FCs in 64-bit systems due to misplaced libs, but I'm still trying to figure out why this happens in Gallery only.
[Android Builders Collective] Ryther:
I have a bullhead, so I think it's a 64-bit SoC, or am I wrong?
[Android Builders Collective] kantjer:
No you're correct, Angler and Bullhead are 64 bit

Sent from my Nexus 6P
[Android Builders Collective] jisoo:
That's not it then. I saw Gallery was looking for a file in lib/arm directory, but 64-bit systems use lib/arm64 soi thought that was causing the FC. Must be something else in the build systems...
[Android Builders Collective] ezio84:
I'm having issues with SuperSU and the Settings-Apps menu after dirty flashing the new dr1.6 aosp branch of the Angler kernel, the only way to get it working again is to flash the previous kernel back.

I think it's time to remove the built-in system mode supersu from the rom, and let the user install the official zip (also to keep compatibility with Android Pay installing the systemless version).

Great, is it still rocking? :D
[Android Builders Collective] Smallsmx3:
Just flashed this ROM, seemed like a win win. Is the kernel stock PN?
[Android Builders Collective] ezio84:
Yes, with a few additions (exfat/ntfs and multirom support).

PN kernel (it's more or less the aosp one) works very well on Angler ;)
[Android Builders Collective] Smallsmx3:
So just flash over with a custom kernel if wanted?
[Android Builders Collective] ezio84:
Yes :good:
[Android Builders Collective] TJKV:
Hey [MENTION=2033478]Yank555[/MENTION]!

So I just switched to yaosp after a long time on stock (Since Marshmallow first came out), feels good to be back!

There seems to be one issue on hammerhead though, that is google camera is reported as incompatible on play store with opengapps (micro) and on slimgapps (mini). Downloading the apk off of apkmirror and adb installing works fine though. Anyone else experience this?
[Android Builders Collective] kantjer:
Try clearing Google Play app's cache/data and reboot.
[Android Builders Collective] ezio84:
---------- Post added at 03:30 PM ---------- Previous post was at 03:00 PM ----------

Ok, PN new translations are up for hammerhead too :D

PureNexus mod 6.0.1-20160508

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

Changelog:

- From stock PN source:

* Add a lot of new languages translations

* Update webview 51.0.2704.36(arm/arm64)

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.

Are you using a custom dpi value?

Try to set it to stock 480.

EDIT: try Kantjer's hint before the dpi trick.
[Android Builders Collective] mslatter:
I'm running into issues trying to build Slim6 for Shamu because Slim references motorola directories/files, where as the proprietary vendor files from PureNexus reference moto files/directories ...so it crashes at the end of the build with:

" No rule to make target `vendor/moto/shamu/proprietary/lib/hw/audio.primary.msm8084.so"

I tried editing my local_manifest to point to the vendor/motorola directory with no luck. I thought I could maybe just fork the Pure Nexus proprietary_vendor_moto repo to my own and edit all the moto references to motorola, but there are a lot of them....

Am I going about this the right way, or wasting my time? I figured after as many hours as I've spent on this, trying this / researching / trying that, I'd make some progress at some point, but no luck yet.... Any direction is appreciated. You could tell me to give up, and I'd be happy to LOL

---------- Post added at 11:55 ---------- Previous post was at 11:05 ----------
[Android Builders Collective] TJKV:
Found some info on the interwebs about this problem. Looks like the problem isn't in either the ROM or the gapps, it's Google's fault ;) (probably)

https://www.reddit.com/r/androidapps/comments/4897ke/google_camera_app_disappeared_from_play_store/

I uninstalled the sideloaded one from apkmirror, went to the app's play store link directly on my computer, clicked install. That did the trick, downloaded and installed on the phone :)

Even searching for it on play store website on the computer doesn't bring it up, only the above direct link :laugh:
[Android Builders Collective] DroidIt!:
Huh, that's interesting. I went to reinstall Adobe Photoshop back on my tab last night and it was nowhere to be seen. Wonder what's going on? I'll have to give that a try and see what happens...if I can figure the direct link :)
[Android Builders Collective] kantjer:
I had a similar issue last week with KLWP not showing up in Google Play.

The fix I posted above solved it for me, cleared the apps cache and data, and a reboot and app was back in GPlay
[Android Builders Collective] TJKV:
Yeah lots of things can influence the compatibility of various apps on the play store, including DPI, sometimes the ROM you use, your current location (via the reported network/carrier), any funny changes the company listing the app makes in their play store dashboard, and the random incompatibility gremlins running around in our phones that corrupt play store data at times.

I think the camera one is the second last one, since interweb reports say that even stock nexus devices (5, 5X, etc) have this issue. Photoshop is also Adobe's shenanigans I believe, I've always had difficulty installing their tablet/phone Photoshop app(s?).
[Android Builders Collective] Yank555:
Working for me ... but indeed not to be found in playstore. Maybe the dpi setting is the issue...

Still in Holland, will be back home tomorrow evening ;)

JP.
[Android Builders Collective] Jonnyredcorn:
Maybe they are updating the Google Camera App and are adding a 60fps 1080p video recording for the Nexus 6P....ahh one can dream...

Seriously though, I still don't understand why the 6P does not support 60fps video recording...its way more than capable from a hardware point of view.
[Android Builders Collective] NHNXDA:
Rom looking awesome Yank, the nav bar customisation is back or better as I can add torch properly & screenshot, just need that volume button wake control now mate.

Also noticed my phone is a bit quicker, whatsapp slightly quicker, but I think what slows it down is the missus message page as its got 2 plus years of chat logs & thousands of images lol, think I may have to get the N5X running now, damn as I love my N5.

I think the Nav Bar customisation options shouldn't be under Language & Input, I would move to System UI as it took me ages to find it lol, tbh I think all display settings options should be under System UI, but hey its not my rom :)
[Android Builders Collective] Ryther:
Here it comes: UBER-Phasma_UTC7.0-eclipsActive-YAOSP-1.20!

Catch it here

You will get YAOSP with:

- Built with UBERTC 4.9 (ROM) - UBERTC 7.0 (kernel)
- Phasma built inline
- Tweaked interactive gov for battery AND performance

thanks to [MENTION=3306843]kantjer[/MENTION] for the help with UBERTC 7.0, compiled it on my own (damned aclocal1.14 :silly: ) and now the ROM is here :D

Try to install it and don't play around with kernel, at least for cpu and i/o ;)

[MENTION=6262409]Mrcactuseater[/MENTION] this is what you wanted, try it if you want and report back plz ;)
[Android Builders Collective] ptr_hamilton:
Hi Hopper8, Have you changed anything after building the rom? I've built it 3 times, and flashed it as you wrote, but it won't boot behind Google logo. Tried different kernel too, no success.

Thanks Pete
[Android Builders Collective] Hopper8:
My guess? You're missing proprietary device blobs. Did you and any lines in local manifest from TheLoonyBin github? If not, that's why it won't boot :) simple fix, you need to add vendor_broadcom and vendor_qcom and device_lge_hammerhead from that github to local manifest for it to boot :)

If that doesn't work, or you're not sure what that means, PM me, I think we're not meant to post links to TheLoonyBin for legal reasons... Someone correct me if I'm wrong :)
[Android Builders Collective] ptr_hamilton:
You have done a fantastic guess :) I heard about looneybin but I thought it was only needed in some cases. In the past I've been able to build without. Whatever I included them and a fresh build is in the oven. Thanks a lot for that precise suggestion, that'll done my issue :good:

Cheers Pete
[Android Builders Collective] Hopper8:
No worries! Glad to help :)
[Android Builders Collective] DroidIt!:
Hey Ezio. Just noticed something kind of goofy/strange in your 11/14 build. It doesn't affect functionality at all, but kind of strange. You'll see in the pic even though I have my phone set to vibrate, up in the status bar it still shows the phone icon. Are you seeing this too or did I hit a setting somewhere?
[Android Builders Collective] DroidIt!:
Oops. Tapatalk being goofy again :)
[Android Builders Collective] ezio84:
All fine here:

But i don't remember when the status bar shows that icon, maybe it's related to quiet hours.
[Android Builders Collective] ralpheboyo:
might be a bit quiet from my side...starting to focus on bacon LP...so no more builds for the time being for KK....(RIP KK)...lol...
[Android Builders Collective] DroidIt!:
OK. Busy day at work today. Will take a look at it a bit later today. I usually keep quiet hours completely off though, I'm on call for work :) I'll take a look later though and let ya know what I figure out. ;)
[Android Builders Collective] csolanol:
Hi all,

trying to build lp5.0 using brunch hammerhead. I am getting this error:

hardware/qcom/keymaster/keymaster_qcom.cpp: In function 'int32_t qcom_km_ION_memalloc(qcom_km_ion_info_t*, uint32_t)':

hardware/qcom/keymaster/keymaster_qcom.h:29:23: error: 'struct ion_allocation_data' has no member named 'heap_id_mask'

#define ION_HEAP_MASK heap_id_mask

^

hardware/qcom/keymaster/keymaster_qcom.cpp:227:19: note: in expansion of macro 'ION_HEAP_MASK'

ion_alloc_data.ION_HEAP_MASK = ION_HEAP(ION_QSECOM_HEAP_ID);

^

hardware/qcom/keymaster/keymaster_qcom.cpp: In function 'int qcom_km_open(const hw_module_t*, const char*, hw_device_t**)':

hardware/qcom/keymaster/keymaster_qcom.cpp:760:75: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]

"/vendor/firmware/keymaster", "keymaster", 4096*2);

^

hardware/qcom/keymaster/keymaster_qcom.cpp:760:75: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]

make: *** [/home/csolanol/slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/keystore.msm8974_intermediates/keymaster_qcom.o] Error 1

make: *** Se espera a que terminen otras tareas....

Any help?

Ty.
[Android Builders Collective] Garrykd:
I have the same issue.It's probably these two commits:

https://gerrit.slimroms.net/#/c/16796/

https://gerrit.slimroms.net/#/c/16795/

You could revert them (maybe) and see if it builds, or wait for [MENTION=3877985]prbassplayer[/MENTION] to fix it :D
[Android Builders Collective] DroidIt!:
Make sure you really thank Garry for the response. I was told while he was writing that, he was floating down a river, white water rafting, saving a drowning child, catching a large mouth bass, and fending off a grizzly bear with his bare hands all at the same time....just amazing! :)
[Android Builders Collective] Garrykd:
Well, that's a little far fetched.....it wasn't with my bare hands, It was with a loose-leaf notebook. :p

[YOUTUBE]Tt33zqib2qk[/YOUTUBE]
[Android Builders Collective] :
Let's say I compile and flash the whole thing now: does everything work or are there bugs?
[Android Builders Collective] DroidIt!:
Hey ezio. Had a chance to look at my wierdedness earlier. Just rebooting solved it. Just a little weird but solved all the same ;)
[Android Builders Collective] hooliganx:
Guys... this 'bug' is related to speaker mode.

occur to me too.

I only enter in dialer, kill and.. gone.

but sometimes shows again.

no big problem for me.

I prefer the future, even with this esthetic issue [emoji6]

n5sk8.8.aow10.26artgapps367

codeblue.r450rd2.21v4atwrp2.8.0.1

------------------------------------------------------------------------

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Android Builders Collective] :
I will remove my build until an official alpha is released

Features

includ ElementalX compiled with Sabermod 4.9

Removed a lot of packages

Calendar

CellBroadcastReceive

Camera

Email

Exchange

Gallery

Mms

Music

MusicFX

SpeechRecorder

SoundRecorder

SpareParts

Browser

VoiceDialer

CalendarProvider

DashClock

DSPManager

Removed Wallpapers

Galaxy4

HoloSpiral

MagicSmoke

MusicVisualization

NoiseField

PhaseBeam

removed "system update check" in the about screen
[Android Builders Collective] dorqus:
Any chance for a slim lp build for mako? Please?:)
[Android Builders Collective] ezio84:
The rom can be compiled but: http://xdaforums.com/showpost.php?p=56830797&postcount=28826

It's better to wait till Slim devs complete their magic :)

Good to know, on mako the feature is not available :p :D

See the link above, Slim devs are improving their recipe :laugh:
[Android Builders Collective] dorqus:
OK thanks :)
[Android Builders Collective] VictorLapin:
[MENTION=4575569]Ryther[/MENTION] any advice for the balanced bullhead kernel? Using ElX right now
[Android Builders Collective] Ryther:
Do you mean my interactive tweaking?
[Android Builders Collective] VictorLapin:
I mean, you made some builds with different kernels, which one is the most performance/battery balanced? I'm interested in tweaking too, though
[Android Builders Collective] Ryther:
I'm using EleX atm, so I cannot say what's better; now that I have successfully compiled the Phasma version with UTC 7.0 I will try with it a couple of days and report back.

Here you can find the thread I used for the interactive values [GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!, I've used the eclipse values.

Here you can find how I've implemented the values in my version of YAOSP Ryther/device_lge_bullhead
[Android Builders Collective] Smallsmx3:
This would be awesome and make things easier. I don't use Android pay but I would like to be able to if I needed it.
[Android Builders Collective] DroidIt!:
Question for the big brains around here :) The infos you guys are talking about conflicts a little bit with info I've gotten from other sources. I've had some people tell me that systemless did work with pay but then Goog made or is making an update to pay so that it won't work with systemless anymore for security sake. So is pay still currently working with systemless su? I've not used pay because I was told it doesn't work with systemless anymore. Any thoughts? :)