yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] endomatic:
[MENTION=2888538]letmedanz[/MENTION]

Yes I figured it out. If I selected my wallpaper with the Gallery app the navbar was not transparent even with the setting selected in Nova. If I choose the same wallpaper with "Nova Wallpapers" the navbar would be transparent. Don't know what happened as I have always used the gallery app. Maybe the latest Nova update changed things.

Best
[Android Builders Collective] ezio84:
Do the following.

Delete your local android_build folder on the disk.

Then remove the slim android_build and add your forked android_build into localmanifest as i told in previous posts.

Then repo sync, so git will download your forked android_build to your disk again.

Then:

git checkout kk4.4

Now you are on a local kk4.4 branch.

So do:

git remote add slimroms https://github.com/SlimRoms/android_build
git fetch slimroms
git merge slimroms/kk4.4

If it says "Already up to date", nothing to do.

If it find updates on the slimroms project, it will merge them on your local forked project. So do:

git push https://github.com/SUroot/android_build kk4.4

Don't use "slimroms/kk4.4" but just "kk4.4" when pushing, so git will find the existing "kk4.4" branch on your github.

"slimroms/kk4.4" is the remote project you fetched to find new Slim updates, "kk4.4" is your local branch where you add commits or merge slim updates and is also the remote branch of your forked project.

Lol :D

It's just the first time you read those steps, next time will be better ;D
[Android Builders Collective] ezio84:
I didn't know that, thanks boss! :D
[Android Builders Collective] reS28raM:
Thanks. This technique is really cool!

Rebasing succeeded by the way, now that commit is back to what the author intended. :D
[Android Builders Collective] danarama:
Nexus L binaries landed

https://developers.google.com/android/nexus/drivers
[Android Builders Collective] aow1980:
After some big mistakes on my part and deleting my github forks.

I'm gonna step back for a few and get a fresh start with LP.

Keep the builds rolling guys.
[Android Builders Collective] Minux31:
My first LP build, if someone want to test, my wife don't want me to test on her N5 ...

https://s.basketbuild.com/filedl/de...ad-5.0.alpha.0.2-UNOFFICIAL-20141113-2223.zip

No modifications for now ...
[Android Builders Collective] Hopper8:
I doubt that flashes properly, my SlimLP builds don't anyway. Something to do with the updater-script according to Robbie.

To flash this:

1. Enter recovery, wipe system, data, cache, and dalvik

2. Flash ROM - it will fail

3. Reboot recovery

4. Flash ROM with no more wipes - it'll work now

5. Flash LP gapps and superSU or you won't be able to add a google account.

Although, are we even meant to be sharing SlimLP builds for now? I don't know, has slim team commented whether to share or not? :confused:
[Android Builders Collective] Minux31:
Thanks for the tips, and for thinking about sharing LP builds, I think because sources are available, why don't sharing builds ?
[Android Builders Collective] ralpheboyo:
New Ultra SlimRom bacon up... Lots and lots of kernel changes from [MENTION=1228651]fusionjack[/MENTION].... Pls check OP for download link....
[Android Builders Collective] fusionjack:
those are cm commits, so i don't take the credits :p
[Android Builders Collective] kantjer:
You should take some credit for it. You are the one with the vision to try and test them on KK :highfive:
[Android Builders Collective] DroidIt!:
Thanks for the ROM update notification ezio :)
[Android Builders Collective] DroidIt!:
Tapatalk's being goofy again :)
[Android Builders Collective] ezio84:
New build is up :p

Nothing special, i've removed the floating mode to avoid issues with Chrome 39 (see [MENTION=5193466]DroidIt![/MENTION] screen :D) and now the "Account" icon has the correct size.

If you don't use Chrome (or don't want to update it) and like the floating mode, stick with the previous build.

Slimkat Mod 8.12.2

Mako & Hammeread download: https://s.basketbuild.com/devs/ezio84-xda

Changelog:

Project name: frameworks_base

*ezio84-xda - Revert Floating mode

Project name: vendor_slim

*ezio84-xda - Bump to 8.12.2 (no more floating mode due to Chrome issues)

Project name: packages_apps_Settings

*ezio84-xda - Fix account icon size thanks to [MENTION=472125]track909[/MENTION] and add missing ones
[Android Builders Collective] DroidIt!:
I've been trying to figure out what's been going on with Chrome :)

Been deleting exposed modules, uninstalling and reinstalling Chrome. Tried wiping data and force closing Chrome. Tried installing Chrome beta. Tried rebooting. Needless to say I'm glad to know what the problem is. I'll update tonight. ;)
[Android Builders Collective] DroidIt!:
Hey Ezio, just wanted to report back. All seems well now and everything's running really good. No more midget Chrome now. :)
[Android Builders Collective] ezio84:
A quick script to add the new slim lp5.0 branch (as [MENTION=842211]Grondinm[/MENTION] explained) to your local and remote forks:

https://github.com/ezio84/scripts/blob/lp5.0/add_lp5.0_branch.sh

Edit it according to your needs.

Ps: i put the whole http address instead of "origin" because someone doesn't set it.

Nice, thanks for the report (i didn't update Chrome yet :D).
[Android Builders Collective] acultr:
I don't understand this. :

I'm ezio84 last build
[Android Builders Collective] ezio84:
It's the pocket mode. Normal behaviour if you enable it ;)
[Android Builders Collective] acultr:
ok. thanks.

?
[Android Builders Collective] Yank555:
Log is always good, I don't use stock gallery, actually I uninstall it by a cleanup zip.

Might also be linked to a gapps issue, don't remember having iasues on my dev device using PureNexus gapps, maybe not linked, though...

As for icon, likely a thheme issue, themed fine on Magpie...

JP.
[Android Builders Collective] davidwilson83:
My good man, there is not an update to Hangouts at all. Check the version in the Play Store that it's asking you to update to, and then check the version that you have installed after flashing the Theme Ready Google Apps zip. Both 8.0? Funny that. If you fix your dpi to be about 480 (aren't you a long time Slim fan? Surely this dpi is blasphemy!) then you will see that the update vanishes. It has to do with arm vs arm64, but it's the exact same version as in Theme Ready, just different libs and one different version code file.

#whiteuimustdie #themesmatter
[Android Builders Collective] Natakranta:
Thanks for quick response.

I replaced the Gallery app with some AOSP Gallery2 app with libs I had saved from an OPO ROM I don't remember, reboot and it works now fine. I'll see if FCs come back after YASOP update to new May security patch, wink, wink

;)

Thanks you your screen I realised you have navbar customisation options including the one I wanted to ask you for, the keyboard cursor arrows. Fantastic!

Is the sRGB colour option in Developers Settings working? I think I can see the colours getting bit pale after enabling, but I am more interested in correcting white, it looks so yellowish on my screen (non-amoled screens user for over two years, since Galaxy). Are there colour calibration options? Karnel Adiutor or something else. I'd like to run your built in karnel for some time to have a feeling before I try ElementalX.

I see Dave is replying regarding the theme, let's see.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] Yank555:
You can calibrate colors with stock kernel, KCAL commits are in the kernel ;)

JP.
[Android Builders Collective] Natakranta:
Hello :D

I'm still setting up the ROM. Still o stock 560DPI. That's play store just for sake of knowledge, but you know I'm not a "latest version number junky"

Can you check that SuperSU icon in settings not themed? Please :D

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] davidwilson83:
It depends on how Yank has made that SuperSU icon and how it is named. Send me your Settings.apk in our Telegram chat and I'll look at it when I get a minute. Consider it your Xmas present. ???

#whiteuimustdie #themesmatter
[Android Builders Collective] Natakranta:
Last Christmas or next Christmas?

[emoji16]

Done!

You're my Santa [emoji8]

Yank will confirm if he has it as an icon or that drawable thingy.

Edit

Dave, you were of course right, not that I doubted it, I changed DPI from 560 to 500 and that Hangouts update is now gone from Play.

Edit 2

Crank me sideways, it feels so good to be back on Nexus! It's really Christmas [emoji3]

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] jisoo:
I hope this isn't too much off-topic, but since Google now pushed out the May security patches, where/when do we actually get these commits to merge into the our own AOSP-based trees?

Will there be a new release tag? Looking at Google's own explanation of the tags, there has not been an update for the Nexus 5X or 6P since r24. Will there be a new build number and corresponding tag in the AOSP trees released, or should we just merge from the master branch?

This is the first time I am building from AOSP (since I used to have non-Nexus devices and had to rely on CM sources), and I still have not fully understood the logic behind AOSP branch and tag systems.

[edit:] Never mind, just saw r43 has been released. Time to update AOSP trees!
[Android Builders Collective] indian84:
Hey JP,

What theme??
[Android Builders Collective] Yank555:
Well it's the same as it was in SlimLP, here's the commit :

https://github.com/YAOSP/packages_apps_Settings/commit/c2951f33602065fbcb236b1085a333887df92c83

It's a question of hours, days at worst. Factory images always drop ahead of sources.

Magpie, but can't remember the details I selected as I backed it up and kept restoring it in layers manager.

JP.
[Android Builders Collective] ezio84:
Track this thread on Google Groups:

https://groups.google.com/forum/m/?hl=it#!topic/android-building/31YK54N_SJo

There the Google devs post about new aosp tags and related devices.

Ps: new tag already pushed :D
[Android Builders Collective] Yank555:
But 1h ago they were not there yet :D

Well .... MTC19T is what I'm waiting for lol

JP.
[Android Builders Collective] ezio84:
I bet they'll also push some crappy tags as usual :D
[Android Builders Collective] VictorLapin:
Guys who build and use YAOSP for bullhead, a couple of questions:

1. Does fingerprint scanner work?

2. What needs to be changed in JP's manifest to build bullhead? Or is it good "out of the box"?
[Android Builders Collective] Yank555:
Reg. 2, vendor is ok, device and kernel are stock AOSP, so you would need to check what's to be done on that end.

I keep vendor updated for bullhead as well.

I don't mind adding those 2 "missing" repos on my github, if I get pull reqs. for them on a bullhead bringup, I'll take them in.

JP.

EDIT : device repo is added on YAOSP github, kernel is cloning to my dev-box, manifest is updated, but don't sync just yet ;)
[Android Builders Collective] angelcalibur:
Hi!

i have a conflicts when i lunch a build:

build/core/base_rules.mk:157: *** packages/apps/FMRadio/jni/fmr: MODULE.TARGET.SHARED_LIBRARIES.libfmjni already defined by hardware/qcom/fm/libfm_jni. Arrêt.

wich one i have to save? if i remove the fm folder in hardware/qcom, build run fine but i don't know if it's really the best way... maybee i will loose something after durig the build...
[Android Builders Collective] limjh16:
And we're on page 1000!
[Android Builders Collective] angelcalibur:
And nearly #10000 post :p
[Android Builders Collective] indian84:
Let's see who is honoured to be the 10,000th poster. :P
[Android Builders Collective] angelcalibur:
Ezio i think! or JP maybee!!! :p
[Android Builders Collective] limjh16:
I'll just post this filler. Ezio/JP/victorlapin you guys have the honours for 10000 post. Hopefully no one else takes it :)
[Android Builders Collective] ( V ):
1000 ?
[Android Builders Collective] limjh16:
AAAND you got the 10000 post. And hi 1001 page okay I shld stop spamming this thread sorry mods
[Android Builders Collective] ezio84:
It's not something i can eat, so i don't care :D [emoji14]

I'd keep the most updated one (if not the same version).

CM devs update their qcom fm tree: http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_hardware_qcom_fm

But you also need to check if all commits are good for your fm hardware.
[Android Builders Collective] angelcalibur:
Thx Ezio! :)

i'am gonna watch it! ;)

but the two folder came from slim github :

<project path="hardware/qcom/fm" name="SlimRoms/hardware_qcom_fm" remote="github" revision="mm6.0" />

and from slim manifest <project path="packages/apps/FMRadio" name="platform/packages/apps/FMRadio" groups="pdk-fs" />

and we have conflicts... don't know if i'am alone...
[Android Builders Collective] angelcalibur:
Oups!!! i' forgot Garry!!! :silly::silly::silly:
[Android Builders Collective] limjh16:
Oh crap same for me.
[Android Builders Collective] ezio84:
I was waiting for the gif lol :D

It means the slim trees still need some polish as Yank said :)
[Android Builders Collective] angelcalibur:
i removed the fm folder in harware/qcom repository! ;)

build in progress!
[Android Builders Collective] ezio84:
Meanwhile i'm checking now the new aosp tags, r43

https://github.com/android/platform_build/commits/android-6.0.1_r43

is MOB30J, for "razor".

MTC19T is not up yet.
[Android Builders Collective] Yank555:
As usual, the one we want doesn't come ... LOL

JP.
[Android Builders Collective] adm1jtg:
You know when your waiting you could look at those interactive profiles I linked you to earlier :D

Hint hint
[Android Builders Collective] kantjer:
Figuring out what you want/need is even a nightmare :(
[Android Builders Collective] Yank555:
Hehe :D Well still at work and been busy on Slim6 an redoing my home network (Ubuntu server as dhcp, dns, pptp, l2tp, openvpn server and such), no much time to look into that so far...

Think I'll rather hit hard and get going on intellimm port to Linux 3.10.y :D

Well and also rebasing ... if ... Google pushes what we need eventually ;)

I slowly am getting to know my way around Google chaos, but they keep making it a challenge LOL

JP.
[Android Builders Collective] VictorLapin:
Intellimm FTW
[Android Builders Collective] Ryther:
If you want you can try my local_manifest here:

https://github.com/Ryther/YAOSP_local_manifests

I've built YAOSP, for the first time, with PN device and kernel repo without problems (master branch); if you want to experiment you can try my UBERTC-4.9_ElementalX_eclipsActive branch, one user reported it is good ;)

EDIT: and yes, fpscanner is working as intended :thumbup:
[Android Builders Collective] VictorLapin:
I am still considering whether I should get a bullhead
[Android Builders Collective] Ryther:
If you can get it at discounted price, it's really worth, I've found it at 269€ instead of 479€ (32gb).

I'm coming from the hammeehead, at first I thought it was garbage, but it's really a good upgrade for 269€, but at 479€ I don't think so
[Android Builders Collective] csolanol:
Mi 4c is coming ?

PureNexus built. We will see if it boots hehehe.
[Android Builders Collective] mslatter:
Hey JP, may I ask where you're getting the Slim6 "proprietary_vendor_motorola" stuff? I assume they must exist somewhere (slimified) but they've been quite elusive... :p
[Android Builders Collective] VictorLapin:
My case exactly
[Android Builders Collective] pkelly517:
I have no regrets coming from my beloved hammerhead.

I immediately unlocked and ROM'ed with PN, so I rarely saw any of the lag issues. At least, there was nothing opening slower than I saw with HH.

The camera is great, as is the fingerprint reader. The only thing I thought I would REALLY miss was the wireless charging. Now I generally only charge during my commute (as opposed to wireless at night), and the rapid charging is awesome.
[Android Builders Collective] Yank555:
I use Nathan's (PureNexus) ... they're sourced from factory images.

JP.
[Android Builders Collective] VictorLapin:
[MENTION=4575569]Ryther[/MENTION] tomorrow I'll start bombarding you with stupid questions :D
[Android Builders Collective] Yank555:
It is, I just totally missed it LOL

It's r25 ... damn Google ?! :silly:

JP.
[Android Builders Collective] Mrcactuseater:
I got a bullhead 32gb at £200! Would recommend Victor?

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Android Builders Collective] ezio84:
They've pushed it a while ago, it was not there when i checked their git. Damned trolls! :D

Thanks for the heads up ;)
[Android Builders Collective] diegocr:
Package Complete: /files/pure/out/target/product/libra/pure_nexus_libra-6.0.1-20160503.zip

Will boot :confused:

Need to remove hardwarekeys.

Does any purenexus supported devices have hw buttons?

Thanks.
[Android Builders Collective] Ryther:
Ahahahaha no problem :cool: I have set up some scripts to help setting things up, I will explain to you how to use them, they are a little tricky because I tailored them mostly for myself while still trying to make them compatible with everyone ;)
[Android Builders Collective] adm1jtg:
I remember seeing in here a few yasop builders and think I recall one even building for shamu but with like a pure nexus kernel. My question is this... Would that build, assuming the dev whose it is will share, allow me to run elite kernel on yasop for shamu? Remember I posted a while ago elite says it will not run on yasop reliably due to its "heavily modified ramdisk" I LOVE yasop but would really prefer the flexibility to change kernels as well.

Course that said yank555 will likely put out intellmm and I will end up going back to his build then anyway....

But just though I would ask in the interrum
[Android Builders Collective] Yank555:
Well no, that will make no diff ... the ramfs will setup the kernel expecting it to be my kernel, as such flashing a different kernel you have 2 things that can happen :

1) kernel uses anykernel -> you keep specific stuff for ROM, good, but also kernel config on boot, bad

2) kernel brings own ramfs -> you lose specific stuff for ROM, bad, but you get rid of kernel config on boot, good

It's kind of a lose - lose situation.

I'd need to reuse a script that checks for my kernel and only sets it up if my kernel is found (as I did on SlimLP), if only 6.x SELinux wouldn't have cost me a bunch of hours already without success back then. If I would make that change, it would allow kernels with anykernel to work fine, as in a win - win, while kernels with own ramfs would still end up in the category 2) above (as is the case in ANY ROM with a kernel that's not using that ROM's ramfs to make the boot.img).

But the issue at hand is, that doing that will use up time, and time is rare, while I'd try to figure our new SELinux challenges, I'll not be working on something else...

Other option is :

Sync YAOSP sources, sync the wanted kernel's sources, revert the kernel config commits in device repo, compile ...

JP.
[Android Builders Collective] adm1jtg:
Never easy is it? Well at least I am learning. Going to go with plan B and wait for intellimm and if its as good as you say then there should be no need to ever change kernels... right? :)

Course you know me just bored to death with to much time and yasop is just so stable.... Well hopefully with the rebase on hold till source drop maybe you will have enough time for intellimm. No pressure and not asking for timeframes just anxious as everything you have released is subperb.
[Android Builders Collective] jisoo:
This is so confusing... I see that there's also a new branch called "marshmallow-dr1.6-release". Is it better practice to merge the tag or the branch? Which one is a more future-proof way to handle monthly updates from Google?
[Android Builders Collective] endomatic:
[MENTION=5790246]VictorLapin[/MENTION] Go for it! I bought a bullhead coming from hammerhead. My initial thoughts were good, but then I broke the finger print sensor and had to send it back for repair. I went back to my hammerhead with yasop on it for two weeks..... Couldn't wait to get back to the bullhead. Calls are better, battery, GPS etc. Not that hammerhead is bad, bullhead just works better. Best
[Android Builders Collective] Yank555:
Hehe ;)

Well sources dropped ~12h ago and are sync'ed... just got up time to get going for a workday, then rebase, v1.20 should be ready in about 16h from now, well first device, then it's compiling marathon for the 5 devices ;)

Those branches are in kernel repos, r25 is ROM side branch.

Personally I rebase, as it's mechanical work and rebasing takes me about 1-2h (more, if there's heavy change, which is not to be expectes on a security patch drop).

But merge or rebase is more of a personal preference decision.

JP.
[Android Builders Collective] Natakranta:
[MENTION=2033478]Yank555[/MENTION], last YAOSP works great on my N6P.

The only thing I can't sort out is that it doesn't connect to my work WiFi. It says "obtaining IP address" than "saved" and nothing. I tried with your built in karnel and with EX today. Still no luck. What could be the reason? What should I check?

It works perfectly fine with my home WiFi network.

I checked with auto WiFi frequency, with forced 2.4 and with forced 5 GHz.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] Yank555:
I might be due to the fact that our friends at Google seem to consider that appying US restrictions on WiFi channels world wide is the way to go :silly:

What channels do your work WiFi networks use ?

We have 2 more 2.4GHz channels and a sh*tload of 5GHz channels more that are legally OK to be used, but no luck with the 6p unfortunately.

I managed to fix that on HH (ROM) and shamu (kernel) back then, but so for no luck with angler (and I've spent quite a few hours on this)...

Just a quick Google :

https://code.google.com/p/android/issues/detail?id=59502

https://code.google.com/p/android/issues/detail?id=197106

https://code.google.com/p/android/issues/detail?id=22474

and there are more ...

And I have the official EU directive on the matter, which very clearly statest that there are far more allowed to be used :(

JP.
[Android Builders Collective] Natakranta:
Thanks for reply. I'm surprised because on Friday it was connecting fine to work WiFi when it was still on stock ROM. I'd thought that stock is more restrictive in this case. I checked with IT manager and nothing changed in work network settings over the weekend.

I'll restore stock nandroid just to check it again.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] Yank555:
Interesting ;)

If you can and it's no trouble for you, could you check or ask your IT guy what channels you use ?

I'd be over happy to finally get that working right, that's been bugging me ever since I got my angler ... it's the only thing that's not "perfect" on that device to me LOL

JP.
[Android Builders Collective] Mikulec:
Just a suggestion, I had also problems with wifi at work. What helped was turning on "Use legacy DHCP client" setting in Developer options.
[Android Builders Collective] Yank555:
Correct, I always forget about that new implementation :good:

Absolutely worth a shot !

JP.