yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] dankoman:
timeout setting is always in effect, regardless of the schedule.

---------- Post added at 10:52 AM ---------- Previous post was at 10:50 AM ----------

his non-caf branch has the out of date version.

the caf branch has the updated one.
[Android Builders Collective] DroidIt!:
Ah OK, thx for the answer Danko. Should have figured you were ahead of me :)
[Android Builders Collective] SOLheel:
Thank you

Popping in to say Thanks to everyone for keeping new builds of Slim rolling out while the team is sorting stuff out.
[Android Builders Collective] kagwind:
[MENTION=2033478]Yank555[/MENTION]

I saw your commit of enabling all Wi-Fi channels for hammerhead.

If I use this commit, does that mean I don't need your other three commits of WiFi country code in this post?
[Android Builders Collective] Yank555:
That is correct, not on HH, that one commit will enable all channels, so no need to override country.

JP.
[Android Builders Collective] dankoman:
aww, you created an xda account just to say that? that's so sweet :D :angel: :good:
[Android Builders Collective] kagwind:
Thanks a lot. :)

I think I'm on the final tweaks of my rom, trying to build Code_Blue kernel into the rom, but can't get its kernel settings.:eek:

Hope I can figure it out tomorrow.
[Android Builders Collective] Yank555:
Yank555.lu SlimLP Update

Tiny update with latest Doze settings by [MENTION=1277872]dankoman[/MENTION] ;)

- updated Doze options (dankoman)

- updated Slim Logo png to offcial SlimROMS banner (Yank555.lu)

Download links as usual on Post 14.

JP.

PS: Shamu & Hammerhead up, flo uploading on dev-host, all uploading on androidfilehost (very slow today)...
[Android Builders Collective] jtwlbz:
never mind.. still uploading right?
[Android Builders Collective] Yank555:
Depends on what device you need, shamu is up on both, hammerhead and flo are only up on dev-host, afh didn't upload (error, reuploading).

JP.
[Android Builders Collective] likonvampire:
Is the update getting pushed through slim center or maybe in the future ??/
[Android Builders Collective] aow1980:
You need to change the ramdisk to code blue version. I installed code blue and zipped the res, sbin folder and all files not in

in a folder (like fstab and so on). Then tracked down and replaced all the files in slim with the ones from code blue. It is time consuming

but if you want it built in worth the effort. Be sure to ask the developer before publishing it in the build. I asked him before and didn't like people

doing that. But things always change. :)
[Android Builders Collective] kagwind:
Thanks. I was actually doing that before I went to sleep, hmm, about 4 hours ago...

Guess from where I got the clue? It's your GitHub! :p (and I stealed several commits on the way.:cool:)

And thanks for the heads up, I will ask engstk's permission before I publish it.
[Android Builders Collective] aow1980:
Not a problem. I was doing it before and then just started doing personal sabermod builds of code blue to try out.

---------- Post added at 02:35 AM ---------- Previous post was at 02:33 AM ----------

@reS28raM If you get time i've got questions about the profiles commits on your github. I've been trying to add them but keep getting

SystemUI FC right at boot up. Using multirom so each install is clean to make sure for testing.
[Android Builders Collective] kagwind:
Too much mess I created... :(

I stuck on the file_context, saying what I added is invalid context.

I think I'll just leave it what it is for now. Flashing an additional zip won't kill me, I guess.

=================

OK. I started from scratch and picked some commits from cm.

I think this time should be working.
[Android Builders Collective] reS28raM:
Your rom being more heavily modded them mine I guess some kind of incompatibility is always possible, your friend is catlog if you find a manner to get the logcat at boot, this assuming you applyed commits in the right order seen each one is based on the previous. Also the first commit is independent, it is a full implementation of Profiles on its own, I would try to apply it and test, then apply the second and test etc. But with a logcat would be very easy to find the culprit of this. Let me know.
[Android Builders Collective] Yank555:
Don't think so, no clue how to make that work, but I expect that would only work on official builds, as it would require infrastructure to push OTAs, I guess.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] acultr:
who is a slim actions?

☺
[Android Builders Collective] ezio84:
A Slimkat feature, you can add on the home (or in other system settings screens where you can configure a shortcut or an app to launch) a "Slim actions" shortcut that will toggle a feature like the Torch or the Screenshots one.
[Android Builders Collective] acultr:
what you mean?

this? I don't have here.

I'm on your last build.
[Android Builders Collective] Yank555:
If you're using a different kernel than the one compiled with the ROM it might be a SELinux issue (vendor commit), check if the torch service is included in your used ramfs (/service_contexts).

For other shortcuts, could also need services to be added.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] ezio84:
It isn't in my last build, I'm trying to add it today so the torch can be set as a left/right quick lockscreen shortcut [emoji14]

I'm with the stock Slim kernel (mako and hammerhead), and I also picked the torch vendor commit that adds the service_contexts line.

Thanks for the reply!
[Android Builders Collective] acultr:
hmmm!

sorry.

?

I am waiting.
[Android Builders Collective] kagwind:
Mine is working according to my last test.

(But I am bootlooping because of another reason. :silly:)
[Android Builders Collective] ezio84:
So I'm probably missing something in Systemui :silly:
[Android Builders Collective] lovejoy777:
Just finished the layers theme wrapper. Means themers can now publish there themes on the playstore. Will release the code shortly. :)
[Android Builders Collective] aow1980:
I was able to adb logcat and finally found that keyguard was the problem. Fixed it but now if I go to profiles or sound in settings it FC's and if set a secure lock it freezes. I'll start

back trying to add it tomorrow.
[Android Builders Collective] reS28raM:
I think it is a good idea, git has an attitude to add code that was not intended to be added. When I applied those commits I checked the code line by line, it can be longer but surely it is safer. :)
[Android Builders Collective] donnabelmartie:
Do I just have to choose which slim build to download? Or any recommended dev?
[Android Builders Collective] Yank555:
Yep, it is and it is, a good idea and longer ;)

... but cettainly worth the trouble ! :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] SteveMurphy:
You have to try them all, that's a rule of this thread.
[Android Builders Collective] DroidIt!:
I've yet to come across a build for really any device that doesn't work good honestly. I do like trying all the different builds from the different builders to see what each person has put into his ROM, how they run and test them out. These guys all work pretty hard to put out good builds and contribute to the official slim too. Usually I just load up whoever has the most recent build out for whatever device I'm updating on any given day ;)
[Android Builders Collective] aow1980:
Profiles has been the bane in my side for awhile now. At first it wouldn't build due to the tablet stuff in it.

Now it builds but fc. LOl the joys of builidng.
[Android Builders Collective] Yank555:
Yep ... and so the evenings fly one after the other ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] nandagopal.r:
[MENTION=2095315]ezio84[/MENTION], I was looking for the option to turn off vol sound while waking up the device using vol rockers. I believe I've seen that in your builds, but haven't seen it in latest build. Removed?
[Android Builders Collective] kagwind:
I recommend you build it yourself. It has to be the most suitable one. ;)

=======================

[MENTION=2095315]ezio84[/MENTION]

It seems that my Screenshot shortcut also causes SystemUi FC, but only Screenshot shortcut.
[Android Builders Collective] reS28raM:
You and me building for Nexus 5 only don't need that tablet stuff - in fact I omitted it entirely, that's why now it builds ;)

Of course if I'll push Profiles to Gerrit when it'll come back (lol) I'll use git blame to see which commit is missing and I'll add it back.
[Android Builders Collective] aow1980:
With work being the way it has been lately, I've done a lot of rush things. Think I may go through and start cleaning things up again. I've tested the add ins and now know which ones I want to keep. [emoji1]

Are the navbar customization working in your build? I added them but never worked right for me.
[Android Builders Collective] ezio84:
No, the build doesn't provide that feature.

To avoid the sound while waking up the device i do this:

- enable vol rocker wake;

- enable the multimedia control for vol rockers under Settings-Audio-Advanced_settings, so the rockers will handle only the multimedia volume;

- add the Notifications tile in the Quick Settings panel, and use this tile to change the system volume;

When you will wake up the phone with the rockers, it won't play any sound.

So i'm not alone, i'm also surprised that CM doesn't provide a Torch activity or quick shortcut yet (afaik, maybe i'm wrong).
[Android Builders Collective] reS28raM:
I tried updating to latest Danko commits from RobbieL811 repo but nothing changed: the torch is on lockscreen and works, you can turn it on or off, but if you run Settings and try to access the shortcuts screen again it FCs.
[Android Builders Collective] kagwind:
Could you elaborate? My torch seems to work.

I could add it as lockscreen shortcut, or use launcher to lauch it as a shortcut or via Activities->SystemUI->Torch.
[Android Builders Collective] reS28raM:
It is well described by an user here:

http://xdaforums.com/showthread.php?p=59169700

A silly thing to fix probably, now I don't have access to PC but tomorrow i'll post the logcat.

Edit: I reread that post, after updating to latest Danko the torch is now working. I still have a commit to update, crossing fingers.
[Android Builders Collective] SOLheel:
Yes.

The slim community is really something special and no other ROM can come close to comparing to slim.

Even though the slim team is going trough some tough times it is still my favorite ROM compared to anything else.

I really can't say enough good things about the slim team and the builders collective.

I've used slimroms on many devices and it had always been the best compared to everything else for me. Reliability, performance, and features. Everything I have wanted in a ROM is there.

Now the sub community of the builders collective had many slightly different versions of slim providing some nice cherry picks and add-ons that can provide some additional features people might be looking for.

Even though we are not getting official updates every Sunday, I could not care any less, as I have big hopes for work taking place behind the scenes. Even if there is no changes pushed - it still does not worry me the least because if they don't have a bunch of stuff cooking behind the scenes I would suspect they will return with a reinvigorated mindset and make progress quick.

I'm on a build from this thread and do not desire anymore currently.

Biggest thing I'm waiting and excited for now is Android 5.1

Like anything else - Goods things take time
[Android Builders Collective] ( V ):
Truly spoke from my heart ;)

Slim4evah!
[Android Builders Collective] SOLheel:
Random Android bug

I know this is not the place to post this, but I do not know where, or how to report this bug the correct way. If someone can do that, or advise me on how to do that; I would greatly appreciate it.

I've noticed this bug when changing the device hostname in developer settings for a few versions of Android now.

I often change the hostname to "nexus5" but right after you type "nexus5" it changes automatically to "nexusnexus5".

I've had this bug on stock Android builds, and every custom ROM I have ever used.

Here is a video showing what I'm talking about.

https://vid.me/wtuw
[Android Builders Collective] ezio84:
Added your rebinding/torch/shortcuts commits and now the torch shortcut works (just the icon need some fixes, it's too big), thanks a lot Paolo!! :laugh::highfive:
[Android Builders Collective] docck:
[MENTION=2095315]ezio84[/MENTION] we wanna prove :)
[Android Builders Collective] Juzman:
Does anyone know if private number blocking will be added again?

Edit: Using Xposed at the moment to do blocking.
[Android Builders Collective] letmedanz:
Aaaaaaaaaaaaand finally OP has been updated :D

MY OP

i'll get around with my GitHub account pretty soon as well

Yes.. that's been fixed..

along with any other bugs as well

I haven't really had any time to post the builds.. i've kinda lost track on what's been added... lol

i'll have a build posted soon...

---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------

What were you trying to do?

Have you been able to get a build completed in the past in the same environment or is this a first time build?

And it would be great if you can pastebin the entire terminal output as usually the errors appear a bit before the compilation stops
[Android Builders Collective] kagwind:
If you simply want to get past that, I think you can add "-Wno-maybe-uninitialized" to the cflags.

I guess you switched to gcc4.8 recently? (been there before)
[Android Builders Collective] reS28raM:
Eheh, glad you got it working! This is the proof if any needed that I have all the necessary commits but shortcuts still do not work for me, they break the Settings app. I must restart the Settings repo from scratch it seems, I keep getting logcats about missing files in java libraries, something is gone south. :(
[Android Builders Collective] ezio84:
Maybe i will able to push a build today, the weather is still super s#it so we can't work :p

Weird, here the Settings app seems to be working well.

At the moment only the screenshot shortcut is buggy.

In the meanwhile i added the "open custom app" action to the awesome [MENTION=1228651]fusionjack[/MENTION]'s Slim Actions tile, but the icon in the tile isn't updated according to the app.

Maybe we can solve it loading the icon with PolicyHelper (the jave file used by Global Actions) instead of ActionHelper, but it's kinda out of my skills :p

EDIT: there's a drawback, with the actual QS implementation we can't add a tile (like the SlimActions one) twice, so no two or more different custom app tiles.
[Android Builders Collective] Riddlah:
I've actually got a few builds previously. The last few commits that I did were mostly in settings and frameworks base for building SuperSU and Adblock into the the build. I did however mess up my android_build repo by pushing the wrong folder to it but I clean the entire sync and redid it. I am just about to head out to work but I'll connect to my build machine and grab the build log output.

The weird part is, I've built with 4.8 for a little while and didn't have that in the cflags.
[Android Builders Collective] kagwind:
Then I have no idea, but I know that warning/error will pop up after switch to 4.8.

=========================================

If anyone still has a Nexus 5 here, could you test whether the pick-up gesture in Ambient Display works?

I think I managed to make that work after changing the sensor library, but I want to make sure it did not work before.
[Android Builders Collective] reS28raM:
Never worked here. Any battery drain?
[Android Builders Collective] Riddlah:
alright here is the link to the pastebin, with the error: http://pastebin.com/2SRz0PTB

If the full log would help, i do have that output to a txt file.
[Android Builders Collective] kagwind:
Not quite sure, only tested it for a while.

Since it should be a low power sensor, I assume the battery drain is ok.
[Android Builders Collective] Mikulec:
On which build?

I am running Yanks build and its working there, if you have all the options turned on.
[Android Builders Collective] csolanol:
[MENTION=2095315]ezio84[/MENTION] waiting for your alpha 1.0c ?
[Android Builders Collective] Yank555:
On which kernel ? Not working for me :laugh:

JP.

Edit :

About to push a tiny update, something I find comes in handy, one additional column of QS tiles :
[Android Builders Collective] acultr:
+1
[Android Builders Collective] reS28raM:
ElementalX probably, right [MENTION=653788]Mikulec[/MENTION]?
[Android Builders Collective] ezio84:
Cooking now, i had one more free day before leaving home again :D
[Android Builders Collective] DroidIt!:
Annnd, 5.1 cometh! :) http://officialandroid.blogspot.co.uk/2015/03/android-51-unwrapping-new-lollipop.html?m=1
[Android Builders Collective] jtwlbz:
Woot!

AOSP out yet?
[Android Builders Collective] Yank555:
Tiny update rolling out, just one added feature, an option to increase amount of tiles per row by one (enlarged 2 -> 3, normal 3 -> 4), as seen in my previous post.

Details and download links as usual in Post 14.

Shamu is up, hammerhead and flo are still uploading.

JP.

PS: This needs some more polishing, works fine on my shamu and hammerhead, but flo wasn't quite perfect. Let me know whatever misbehaves so I can get that fixed (but tonight I'm done, too tired :angel:).

EDIT : All up on both download sites.
[Android Builders Collective] AA1973:
Thanks [MENTION=2033478]Yank555[/MENTION]. I am enjoying your builds since 22/2. ?
[Android Builders Collective] ezio84:
Finally! I hope we won't need to add all custom features from scratch :D
[Android Builders Collective] Mikulec:
As Mr. [MENTION=5131448]reS28raM[/MENTION] said, I use ElementalX.
[Android Builders Collective] ezio84:
Ok here's the new build to fill the time waiting for Lollipop 5.1 :D

*** SlimLP 1.0c mod for

mako & hammerhead

***

Download:

https://androidfilehost.com/?w=profile&uid=23578570567714195

(links on the right)

Changelog:

- CM Eleven, AudioFX and Terminal source sync

- Slim source sync

- Customizable Power menu (thanks [MENTION=1228651]fusionjack[/MENTION])

(set it under Interface-Power_Menu)

Layers:

* Built-in Layers backup app by [MENTION=3306843]kantjer[/MENTION] : after loading your overlays with the main Layers app, run this little jewel tool so a backup script will be created in the system addon.d folder and your overlays will survive after a rom dirty flash.

* Layer Backup app: show a Settings entry (under Interface-Themes backup) if the app is installed (thanks to a collaboration with my bro [MENTION=2888538]letmedanz[/MENTION])

* Layers app updated from 2.0 to 3.2 (now you will be able to install playstore updates without errors) (thanks [MENTION=4410674]lovejoy777[/MENTION])

(please -only this time- uninstall your current version if you have removed the built-in one and installed the new one from the playstore).

- Chamber of Secrets is back (thanks [MENTION=5131448]reS28raM[/MENTION])

(go into Developer Settings and tap on the blank space at the bottom of the page)

- Some SlimActions/Shortcuts are back (thanks [MENTION=5131448]reS28raM[/MENTION])

(add them as Nova shortcuts, or as lockscreen shortcuts)

- QS tiles customization:

* User can set four tiles per row instead of three

* CM visualizer (AudioFX) tile improvements

Build additional features (Please read it before asking where to find a setting):

PS: this list also contains links to all commits if you want to cherry-pick them:

https://github.com/ezio84/scripts/blob/lp5.0/My_mods-commits_and_tips/Commits-list-with-links.txt

NB: SuperSU, the Layers app and the Layers backup app are now built-in, you don't need to install them after flashing the rom.

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] Yank555:
Interesting, do you know if he changed anything in the kernel to make it work ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] DroidIt!:
Should be able to load up shamu for sure and MAYBE flo ;)

---------- Post added at 05:02 PM ---------- Previous post was at 04:54 PM ----------

Oh and just as general infos :) If you decide to load up the exposed Alpha 2, hold onto the Alpha 1 apk, I had quite a few modules I use quit working after going to Alpha 2. You can still use the new 03/08 flashable installer, but the alpha 2 apk threw off some of my modules. And one thing for [MENTION=2033478]Yank555[/MENTION] if anybody else can confirm, I had some problems connecting to mobile data on my wife's N5 with your 03/04 build. Not sure if it was something with your build or a module or what, but did anybody else using yanks 03/04 builds have any mobile connectivity problems? WiFi still worked OK, just mobile data wouldn't connect. I didn't ha e time to look into it properly, so that's why I ask :)
[Android Builders Collective] Skripka:
So with 5.1, can we get Slim Team out of Area 51?
[Android Builders Collective] TonyTurboII:
The two have no correlation.
[Android Builders Collective] jtwlbz:
Aosp 5.1 is up!!!
[Android Builders Collective] Juzman:
Will wait for Yank555 build. :)
[Android Builders Collective] kagwind:
I use my own build, with CodeBlue.

That's why I asked. I saw your previous post that said yours working with ElementalX, so I want to ensure the real reason for which it works / doesn't work.

I unpacked ElementalX's zip but didn't find anything related, maybe I'm missing something.
[Android Builders Collective] letmedanz:
The bitsyko team & Steve Lovejoy seem to be giving us tough competition.

We added the backupscript made to an app thanks to some amazing tasker skills by [MENTION=3306843]kantjer[/MENTION] & they go ahead and add backup feature to the layer's app itself :D

Awesome
[Android Builders Collective] SOLheel:
All kinds of gains

Heads up customization

Android 5.1

:highfive:

I think I am dreaming

Please don't wake me
[Android Builders Collective] reS28raM:
I have read a comment somewhere that he enabled the sensor in the kernel but never had the time to further investigate - until I fix this nasty bug I have in the Settings app I am stuck. :(

Also can't understand why Google leaved that disabled on Hammerhead, that's why I asked about a possible battery drain.

That feature is really important for people running Nexus 5 in a cover, can't really wait to know if it can be enabled on stock kernel. [emoji41]
[Android Builders Collective] Yank555:
Weird, nothing changed in that part of the sources ... and no repo sync either.

But can't personally comment on that end, as I don't use my N5 as daily, so WiFi use only.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.

---------- Post added at 07:42 AM ---------- Previous post was at 07:37 AM ----------

It sure can, shouldn't be a big change, simply deny a sensor to be put to sleep. It will have an impact on battery, but likely nothing really important and small enough to go about unnoticed.

Could even be coded to be switchable via sysfs, so users who don't want to use it could keep it behaving stock.

Will have a look at his repo, if I can see something.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Android Builders Collective] kantjer:
From the screenshots it appears Layer Manager is adding a backup and restore option. My solution is aimed at the layer theme surviving a dirty flash without the need to manually restore and reboot again.

But lets wait and see when it's released.
[Android Builders Collective] Mikulec:
I am not sure but his kernel allows also "Double Tap To Wake" feature which might be something similar since it has to keep some sensor "alive". But I havent really investigate why it works.