yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] mslatter:
Hey guys,

I got Slim to build for the Lg G3 the other day, but with no data. There was a fix built for it, that some folks help me find, and I substituted the proprietary line with the existing LoonyBin (sp?) one. Then rebuilt, and since then have had nothing but problems. The first time it built fine, but when I tried to install, I didn't even get to the boot animation, just sat at the splash screen and after 10 minutes I pulled the battery. So have started the build process from scratch several times, including this Data Fix and constant errors. I"ve been reading everything above.....and it's generated a new question...

When you guys link to cherry picks or fixes, are you guys actually editing the code in the files of the cherry picks, or are you simply adding the github links in the manifest? Maybe I missed an important note in all my reading / learning! Last night I thought I'd be clever.... I compared the Data fix files to the LoonyBin ones.... copied the stuff that was in the Fix and not in Loony, and pasted it into the Loony files themselves (not the links but the actual mk files on my computer). Then tried to build again, but it stopped an hour in with an error related to the some of the changes I made...so I'm at a loss. I am not at home so can't Maybe I should start building ROMs that are in active development and don't need all these tweaks to get them to work.

The good news out of all this was that if Data wasn't important, I got Slim 5.1 built for the G3! LOL
[Android Builders Collective] danarama:
Maybe I'm mistaken - I'm going to restore chroma and check, I was convinced that wasn't the behaviour, but Dan said this:

" That patch not only prevents invert if the boolean is set to false, but also prevents doze from interacting at all with colors. Normally, it's set to invert AND apply grayscale. I can do separate boolean for grayscale too if need be...?"
[Android Builders Collective] Riddlah:
When I get home from work I can do a repo sync and pull my old repos and test if your still having issues.
[Android Builders Collective] danarama:
[MENTION=2033478]Yank555[/MENTION]

Unfortunately, I wasn't mistaken. Restored Chroma and tested ambient display with my blue theme.

Then restored back to slim.
[Android Builders Collective] reS28raM:
It seems it doesn't work on 5.0 which is strange but I don't know selinux stuff at all. Moreover, if the two commits does stuff which is incompatible each other the build process spot the error, there are security checks. I got no errors but the code do not work for me. Tomorrow I'll take a logcat, now it is too late. :)

A someone's else 5.0 test build would be a good idea though.
[Android Builders Collective] Riddlah:
The only other thing I can see it's if there is another avc denial that comes up on 5.0 that isn't there on 5.1 (don't have much background myself on selinux, but I've been doing some reading). One other thing I noticed earlier today on slim's gerrit, there's a commit to remove mediaserver.te. Not quite sure why or if it will cause issues with future stuff that might be implemented.
[Android Builders Collective] Yank555:
Good, that means I may be missing a commit afterall :D

I mustn't have noticed as I use midnight theme, that's almost black... Thanx for pointing that out !

I saw ezio pushed RRO 2.1 to gerrit, might as well revert all RRO on my end and apply his...

But just uploading a build right now with fixed proxy speaker on bluetooth, will look at this tomorrow if that's ok, a bit tired (11pm already here, long day at work) :angel:

JP.
[Android Builders Collective] reS28raM:
I saw that in Chroma rom mediaserver.te was initially missing, probably there is more then one mode to accomplish the same task and each rom dev simply choose the one which fit better for him, it is unavoidable that sometimes we must change stuff due to upstream changes. God bless Slim devs who always update five secs after I am done with a build eheheh
[Android Builders Collective] Yank555:
New shamu 5.1.1 build available in my OP

Fixed speakerphone while connected to BT ... and some tiny show&shine in about phone ;)

- Slim Logo in Settings

- Fixed proximity speaker with bt audio​

Download links can be found in my OP here on post 14.

JP.

PS: devhost & AFH done uploading, filename = "Slim-shamu-5.1.1.alpha.0.1-UNOFFICIAL-20150505-2226.zip".

-------

Edit : I'll redo RRO 2.1 tomorrow if I can.
[Android Builders Collective] danarama:
No rush dude.
[Android Builders Collective] angelcalibur:
New build with last slim source (05/05/2015)

Download the Rom :

For the moment, With stock (CM) kernel build with Uber Toolchain:

SlimLP-5.1.1--20150505-OPTIMIZED-jfltexx.zip

Download the gapps :

Official Slim GApps & Custom GApps

Beware about downloading the good Gapps, for 5.1 ROM!

Download SuperSU :

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

Stock fonts :

https://www.androidfilehost.com/?fid=95897840722642369
[Android Builders Collective] ralpheboyo:
New CM Build on the way

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

https://github.com/ralpheeee88/cm_a...mmit/8536e710895c80242c368f64a1877028c63eb74a

https://github.com/ralpheeee88/cm_a...mmit/5e3e1c0980854ad4e67483cc0e5899a4b09274dc

https://github.com/ralpheeee88/cm_a...mmit/64fb0ab4128a21f85f363ff6e23f3e21f7fd4bae

https://github.com/ralpheeee88/cm_a...mmit/cdead087185c40522c537f237e86e9bc7f17e993

https://github.com/ralpheeee88/cm_a...mmit/2870d05e43076a104439d22be37ae011f09dc3aa

https://github.com/ralpheeee88/cm_a...mmit/ccb0515c2abd6574627663cd57b8a3c7a0251e2b
[Android Builders Collective] likonvampire:
No HH love again ?... [emoji19] . the last time I heard about HH was that it doesn't boot , any update on that guys ?
[Android Builders Collective] hooliganx:
last 2 pages have all information we got... till now. [emoji6]

n5blisspop.v3.2.ngtly_may.03themedslim.gapps.may.01

elementalx.2.11rd.2.25v4a.2.3.4twrp2.8.6.1

-------------------------------------------------------
[Android Builders Collective] DroidIt!:
Hey [MENTION=2033478]Yank555[/MENTION] :) I've been a busy dude but got around to flashing your build from the 4th I think it is. It's running really good so far. Really smooth, great battery, good responsiveness...all around just good. I hope the built in messenger thing gets fixed sooner rather than later, but I've not really seen any issues at all. Awesome work and thanks for the builds. Working really good overall ;)

...Oh and one question, is anybody planning on doing any flo builds? Still use my tab about as much as I do my N6 so just curious ;)
[Android Builders Collective] Yank555:
For now I could offer you my YAOSP for Flo ;) But it's not public atm as I'm in the middle of something (navbar is in, but needs polishing and navrings don't work yet), and no time to both push YAOSP and SlimLP ... and my Shamu reallllly needed some love as I had put it in the drawer due to lack of usable 5.1.1, before SlimLP base was ready and AOSP is derped (THANX MOTO for crappy support on a Nexus flagship device and Google for not even checking what you upload to your Nexus website !).

If you want this intermediate state, let me know, I'll upload it for you.

JP.
[Android Builders Collective] theesotericone:
I thought the N6 was a tablet.
[Android Builders Collective] danarama:
D'oh, just realised the SMS issue also breaks pushbullet responses to SMS too :(

Really bad news
[Android Builders Collective] Yank555:
Using a 3rd party SMS app doe work just fine for me, sent and received a dozen SMSes today (using Textra).

Hangouts is also reported to work.

Pushbullet I can't say, don't use it.

JP.
[Android Builders Collective] acultr:
I would appreciate a nexus 5 build.

thank you very much.
[Android Builders Collective] DroidIt!:
YAOSP....I like it :) Sure I'll take the N7 build and test it for you. I always use pie anyways, so I wouldn't be bothered too much by navbar stuffs. So sure, whenever you get a minute if you wouldn't mind uploading it that would be awesome :)
[Android Builders Collective] SteveMurphy:
Check [MENTION=4097221]bokbokan[/MENTION]'s thread here: http://xdaforums.com/showthread.php?p=57422209

He just posted a 5.1 Slim ROM for us Hammerhead users.
[Android Builders Collective] Yank555:
You've got a PM.

JP.
[Android Builders Collective] Fastrite:
That's a bitter pill to swallow ;)
[Android Builders Collective] Yank555:
OK, so I've redone the RRO from scratch using the official LayersTeam repo.

It does indeed not use colors anymore, but the main line of my Notes Traveler Mail notificaiton was black text, while the second was indeed white ?!

Not what I see in your screenshots ...

Are the LayersTeam missing a Layers commit ? :angel:

JP.

Edit : Also, settings icons are gone ... I may want to revert some of the newer (after 2.1 LayersTeam commits) I guess...
[Android Builders Collective] danarama:
There lies another problem. Some notification text is controlled by systemui / framework and some by the individual apps.. So for example gmail and inbox, control their own notification text, so I had to build little layers for those apps too.

So it depends what apps you're using.. I find for testing, push bullet works best

---------- Post added at 09:15 PM ---------- Previous post was at 09:05 PM ----------

Yes I can send and receive using the app Tylog recommended... What I do like is when I receive a text at work, a pop up from push bullet comes up on my work computer and I work from there instead of phone.. But that isn't working.

From a logcat using Google messenger, it looked like a database problem (column missing or something) which maybe explains why pushbullet doesn't work... Also the app Tylog recommended doesn't see texts that came in in the standard /data/data/com.android.providers.telephony/databases/mmssms.db so I wonder if the app has its own db, which reinforces that possibility.

Anyway, unfortunately sms is 50% of my phone use, so had to go back.
[Android Builders Collective] Yank555:
Strange is that the very same app will produce proper white text without layers...

Make perfect sense.

I restored my SMS DB via TB and my app saw the SMSs right away.

Should get sortet soon anyway I suppose.

Have removed some of the 2.1+ commits, will see how that goes.

JP.
[Android Builders Collective] danarama:
1. Standard rom - black notification text on light background. Ambient display Inverts all notifications to white text on black background even if original black text is hard coded in app.

2.Dark Themes (layers or otherwise) generally are written where light background colour reference is changed to dark and dark text colour reference is changed to light colours..

3. Problem here is standard notification is light text on dark background but ambient display inverts that putting dark text on light background (the opposite of what we want)..we have black text on white background on ambient display.

So commit was invented for layers to not invert on ambient display so we keep light text on dark in both standard notification and ambient display.. Of course we only want to do this on dark themes. Otherwise we have same problem if we do not invert light theme as seen in 3 (we would have dark text on white in ambient display) so to only avoid invert dark themes, dark themes must contain custom boolean in systemui (5.0) or framework (5.1) layers.. But of course this boolean only affects notifications that are coloured by systemui or framework and not apps that are hardcoded.

For me, I have a layer for inbox and gmail that invert a that notification text specifically to white so it works properly. Not sure if [MENTION=1277872]dankoman[/MENTION] can come up with some magic, to let us use the same boolean in these apps instead of having to locate the notification text for each app.

Yep, hope. So.
[Android Builders Collective] Yank555:
Yup, that I knew, thus I was wondering why it didn't work on my end ... and in fact my issue was that stupid me was still using an older version of midnight :silly: So it didn't make use of invert yes/no ... updated to latest, and well what can I say, looking as it should :D

I reverted settings icons tint commits (so I'm at rro 2.1, not above) and now all is just fine in the settings as well, all icons shown and accounted for ;)

I've also added Navbar to my build (needs some polishing and Navring targets don't work at all yet) so I don't know if anyone wants me to push this stage or you rather wait until I get this sorted out. It's good enough to be on my daily device ...

Just let me know if I should push.

JP.
[Android Builders Collective] mslatter:
I'll test it too if you'd like more testers :)
[Android Builders Collective] Yank555:
You've got PM ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.

---------- Post added at 07:34 AM ---------- Previous post was at 06:50 AM ----------

New shamu 5.1.1 build available in my OP

Full RRO 2.1 support (lockscreen notifications fine now) plus tiny fix on the proxy speaker with bt fix ;)

- Tiny update on proximity speaker with bt audio fix

- RRO Type 2.1 layers support (reverted type 2 and redone 2.1)​

Download links can be found in my OP here on post 14.

JP.

PS: devhost & AFH done uploading, filename = "Slim-shamu-5.1.1.alpha.0.1-UNOFFICIAL-20150507-0703.zip".
[Android Builders Collective] Promez:
i know that feel :( the same thing's happened to my beloved N4

Come in the bacon team! :p
[Android Builders Collective] Yank555:
New shamu 5.1.1 build available in my OP

Customizable navbar and navring targets, the navbar is still WIP, there are a few tiny visual glitches to fix, but it's absolutely good enough to be usable.

Changelog over previous version :

- Customizable navigation bar (this is WIP, some tiny visual glitches in navbar left to fix​

Download links and full changelog can be found in my OP here on post 14.

JP.

PS: devhost & AFH uploading, filename = "Slim-shamu-5.1.1.alpha.0.1-UNOFFICIAL-20150507-2102.zip".
[Android Builders Collective] GartimusPrime:
Layers 2.1

I have been learning how to build slimLP and a few other ROMs and was curious if anyone knows how I would go about adding Layers 2.1 to my builds. Is it as simple as cherry picking some commits or is it more complex than that?
[Android Builders Collective] ezio84:
Here's a squashed commit for the DocumentsUI mod to let it act as a full file manager: https://github.com/ezio84/frameworks_base/commit/0984942d51a903335cd3b555f966aee77e7acd44

So no need to add a 3rd party one (it' also useful for the user to manually install an apk like titanium after the first boot).

Some days ago i pushed the needed commits in the rro2.1 tag on the Slim gerrit: https://review.slimroms.eu/#/q/topic:rro2.1

Just pick them.

Maybe [MENTION=2033478]Yank555[/MENTION] has tested them, i'm still without a phone (should get a nexus5 today :D).

PS: this is the original LayersTeam github: https://github.com/LayersTeam
[Android Builders Collective] acultr:
When we get you a new build?

?
[Android Builders Collective] Yank555:
[MENTION=4825640]GartimusPrime[/MENTION]

I picked from the LayersTeam repo. But you need to leave out the newer commits for settings (icon tint) else you'll lose the settings icons, just pick the 2.1 squashed commit and the FC commit for Settings and you should be good.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Android Builders Collective] ezio84:
I hope soon :D

Indeed, with the settings icon tint commit the theme needs to be updated. Branden has already figured it out with Sublime :good:
[Android Builders Collective] Yank555:
But tbh I don't like it when new "updates" break previous stuff, it should try to extend stuff...

I'll for now stick to Layers 2.1. And it does what I need with the current themes.

JP.
[Android Builders Collective] ezio84:
That's a good point of view, considering that without the commit we don't lose features at the moment. :good:

---------- Post added at 01:12 PM ---------- Previous post was at 01:05 PM ----------

PS: this one https://review.slimroms.eu/#/c/2613/ shouldn't break the compatibility with old layers, but it allows the layer dev to add a customized background image:

https://plus.google.com/101729058057775926785/posts/WWTsJ11VR2N
[Android Builders Collective] Yank555:
New shamu 5.1.1 build available in my OP

I had changed the behaviour of the power key on the navbar so it also shows on lockscreen PIN and SIM-PIN entry just like the back key, as I find it handy and easier to reach than a double-tap on the statusbar when using the device with one hand ... but ... I slightly screwed it up as the power key sometimes wasn't showing on the navbar in landscape mode ... and that is fixed now.

So if you use the power key on your navbar, it's well worth updating, else you can leave it be, would be wasted time ;)

Changelog over previous version :

- Fixed power button sometimes not showing in landscape navbar​

Download links and full changelog can be found in my OP here on post 14.

JP.

PS: devhost & AFH uploaded, filename = "Slim-shamu-5.1.1.alpha.0.1-UNOFFICIAL-20150508-1210.zip".
[Android Builders Collective] acultr:
I think I need to buy a nexus 6.??
[Android Builders Collective] likonvampire:
+1 waiting on HH .. [emoji20]
[Android Builders Collective] hooliganx:
anyone here have a Shamu to sell me? [emoji41]

JK!

n5blisspop.v3.2.ngtly_may.03themedslim.gapps.may.01

elementalx.2.11rd.2.25v4a.2.3.4twrp2.8.6.1

-------------------------------------------------------
[Android Builders Collective] gladi8r:
Will you continue to build for the N4?

I've been using your builds exclusively since you started, so thanks for everything so far. :fingers-crossed::D
[Android Builders Collective] Nucleonic:
I've been able to successfully build a Slim-5.1.1.alpha.0.1-UNOFFICIAL-20150508-2148.zip from source. Strange thing now. After flashing, and rebooting, I get stuck on the Google screen. Just sits there until I put the phone back into recovery mode. Is there a commit I'm missing that is necessary for the build to boot?
[Android Builders Collective] setiawanjimmy:
Guess you were talking about the "no icons leave behind" commits by aosip?

Basically it is a good one but not all roms support it. For themers, they only need to add 1 color code and all the settings icons are tinted. Even the roms custom icons. Therefore we dont need to pull all those roms custom icons and add it to the themes.

But yeah, if the themes dont have that line of code all the settings icons will be in stock color. And its only good for themes that just change the icons tint. For themes that do custom icons, they still need to add the pngs in their theme.
[Android Builders Collective] Yank555:
Well with those in, I ended up with NO icons except the ROM specific ones ... so in my case, I only had icons for "Interface" and "SuperSU", the rest was empty (that was with rootSU's material settings icon overlay, though, didn't try without themes).

That was with these commits in :

https://github.com/LayersTeam/platf...mmit/f84f50e8e4c96713bed75f49f7fb093f67714f4f

https://github.com/LayersTeam/platf...mmit/1370059856cd306bac147f443a77c974adda75e4

https://github.com/LayersTeam/platf...mmit/eda091cc0044727bf6ed12aa6d4f021d60cb39be

I must admit I reverted the three of them (since settings icon related), and I was good again, so I kept it that way and didn't look any further.

Sure the theme might need an update. At least so far I'll keep it this way, whenever most themes are "ready", it'll be easy to pick the rest...

JP.
[Android Builders Collective] setiawanjimmy:
Yup those are the commits.

I understand mate. That is what i always get when asking rom devs about the commits. Most of them want to wait until more roms have that commits and/or themes updated.

For themes with custom icons like rootsu, they need to add _exposed behind the icons pngs. Like ic_settings_supersu_exposed.png

Basically the regular themers have the code in. We are trying to spread the words.

That being said, any n5 build with layers commit? ;)
[Android Builders Collective] Yank555:
The funny thing was, I did have the color circle icon backgrounds, and SuperSU (and Interface) were the only icons showing, all others were gone...

Will give it a shot without a theme as soon as I get some time, but this WE will be real life, big internation car club event to organize, so very computer-less busy days ahead ;)

Your midnight is compatible with this ?

Not yet, unfortunately, but as soon as the device repo is good, spin the same ROM as I have for N6.

JP.
[Android Builders Collective] setiawanjimmy:
Yup my themes are updated, i think only scarlett thats missing the code..

Nice, cars like fast and furious? With girls and booze? :D have fun mate..
[Android Builders Collective] skidaway:
broke my N4 screen today :(

I was dreading this day, because now I have to decide what to replace it with. I wish I would have ordered a N5 while the play store still had them. I really don't want to go the used route for a new phone and I want something with an unlocked bootloader that will run Slim/ROMs. I guess I'm stuck with a used N5 or a new one plus. bleh.
[Android Builders Collective] ezio84:
N5? The updated code isn't pushed yet to the Gerrit, to have a not bootlooping rom you need to use these trees by Robbie:

https://github.com/RobbieL811/kernel_lge_hammerhead

https://github.com/RobbieL811/device_lge_hammerhead (IMPORTANT: the lp5.1-test branch)

Also set TheMuppets repo instead of TheLoonyBin for your vendor blobs, the latter isn't updated yet.

Welcome in the party :crying:

I got a nexus 5 yesterday, and i'm already very satisfied about it: the phone size is quite similar to the n4, so it's a very good choice for people used to the that size (now let's wait for the "that's what she said" post :D )..

Yes, mako is still an amazing phone and it needs love :D
[Android Builders Collective] RobbieL811:
We post CM builds here???
[Android Builders Collective] ralpheboyo:
lmao....figure this is more of forum on "how to" and general help/building roms....

in anycase I can cease and desist

depends what Slim want and community
[Android Builders Collective] kantjer:
LOL, change the forum title to "AOSP/CM Builders collective" and you are good to go ;)
[Android Builders Collective] ralpheboyo:
see thats the creative thinking we love about you biki....(general slimroms discussion....how we by pass that one?)...lol...
[Android Builders Collective] Yank555:
Kind of, Subaru Impreza meeting, but no booze (we're serious ;) ), and girls ... well ... yeah some ;) But movies are movies, not reality :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Android Builders Collective] Nucleonic:
I have a Nexus 6. Only mod I made was to add the LoonyBin files to the local manifest, changing lp5.0 to lp5.1. Are there similar commits necessary to make the Nexus 6 boot?
[Android Builders Collective] Yank555:
Nope, should be good as is. Do you run into issues ??

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Android Builders Collective] Nucleonic:
The source builds fine. I flash it and reboot but the phone gets stuck on the boot screen with the Google logo and doesn't stop unless I force back into recovery.

If the Gerrit source tree is working now, including manifests, for the Nexus 6, would it make a difference that I flashed from a CM12.1 home-built nightly? I reflashed back to stock. Haven't tried the procedure again. Might this have been my problem?
[Android Builders Collective] rignfool:
Cars?

Pretty please... Take pictures?

I like cars... (turtles smell funny)
[Android Builders Collective] RobbieL811:
Lol. Shut up! You know I didn't mean it that way!
[Android Builders Collective] Yank555:
Well you need to wipe before going from CM to Slim, but other than that, it should work, I sync'ed on april 30th.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

Will be end of month, now is just preparation ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.