yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] TJKV:
I would guess it has something to do with Smart Lock in that case. Maybe it doesn't respond while doing a check for the various conditions it encompasses. I personally use only location based Smart Lock, and get the lags fairly often. Time since last reboot doesn't really affect it here. So I temporarily removed the device pin and set it to Swipe. I'll see how that affects the lag.

It's a shame really, I had a system that worked perfectly before Smart Lock was introduced along with Lollipop. Tasker took care of location detection and ran appropriate tasks to enable/disable pin locking among many other settings (GPS Accuracy, WiFi, Manual/Auto brightness).

Home/College= WiFi on, GPS to Battery Saving, Manual brightness, and no pin.

Elsewhere = Opposite of that :p

Maybe I should switch back to that...
[Android Builders Collective] ezio84:
I have lag with smart lock disabled too.

With Yank's April gapps, no lag. The good thing is that Play services isn't updated till you choose to do it when you open some apps like Google search (they'll ask you to update it to use Google now).

It's the worst trolling issue we ever had [emoji14]
[Android Builders Collective] TJKV:
Yes I just came to the same conclusion. In fact even disabling lockscreen entirely causes the phone to not respond for a second or two when the screen is turned on. Normally that would sound like a kernel and/or governor issue but that doesn't seem to be the case here.

Unfortunately using an older version of play services is not an option for me. Next step would normally be to do a clean flash, but since that reportedly doesn't fix it, I'll head back to stock and then flash some other ROM and see what the result is. If the problem is only gapps then it should occur in other ROMs too.

Haven't ever flashed anything other than Slim, no idea what other ROMs are out there currently other than CM. Need to go looking around now :p
[Android Builders Collective] Yank555:
Agree on that, we already had sth similar due to camera stuff and smart lock face recognition.

Please keep us posted, this will be interesting feedback.

It could simply be triggered by gapps but not be an actual gapps issue. In that case other ROMs should be fine, and we need to find what indeed is being triggered...

In the facelock issue that was the case on shamu, fixing camera stuff in fact fixed these lags. But that was easier to pin down, as the lags only appeared with facelock enabled.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1b kernel.
[Android Builders Collective] Mikulec:
I went different route, flashed your latest build and flashed different gapps (not slim gapps). Will report if I get the lags.
[Android Builders Collective] ezio84:
Flashed my latest "bad" build with 23 July slim gapps, and some frameworks base commits from aosp, no lag atm :D

I just ****ed the google camera but i think i know why.

If all good within some hours, i'll push the new build. Fingers crossed :laugh:
[Android Builders Collective] JaylanPHNX:
Going off what you said about the face lock camera issue, I'm wondering if we can try narrowing this down by what play services might be accessing. One thought I'm having is location services (particularly cell-based location). Is everyone on hammerhead having the issue using the latest radio? Does an older radio change anything? I'm probably barking up the wrong tree, but maybe it's at least a viable we can eliminate.

From my SlimTab Pro 8.4
[Android Builders Collective] Yank555:
On my end, I use the latest radio, but have location services turned off all the time, except when I specifically need it (on both my shamu & hammerhead).

JP.
[Android Builders Collective] PerfectSlayer:
I still have issue on face unlock due to the camera. I watch the log and I saw same kind of error I posted you. But this kind of lag on lockscreen lengths more than 15 secs…

And sometimes, the camera fails too.
[Android Builders Collective] Yank555:
I thought that was fixed at some point, wasn't it ??

I'll try to have a look, but busy atm with trying to get my kernel building inline on shamu.

JP.
[Android Builders Collective] TJKV:
Thought I'll throw into the mix another idea that I had earlier. I think the navigation bar buttons are drawn differently in Slim since recently, right? Could that be related in any way?
[Android Builders Collective] Yank555:
SlimNavbar had been in for quite a bit now ... and I can't remember much change to it except SlimDim (which has been proven unlrelated).

JP.
[Android Builders Collective] TJKV:
Yes but we are assuming this bug involves a ROM component and a Gapps component :p

Well either way, what exactly is SlimNavbar, I mean in terms of the button drawing? What is done differently than in stock, for what benefit? I had been meaning to look into it but haven't got the chance to yet. Also does it have the side effect of not rotating the back button 90 degrees when the keyboard pops up?
[Android Builders Collective] PerfectSlayer:
It comes back… Less often but still happens sometime… :(

(Currently installed version: 20150715-2359)
[Android Builders Collective] Yank555:
ROM Update SlimLP beta 0.2 (shamu only)

A tiny addition I added today, native USB-OTG usbdisk support.

Downloads :

I will keep this in my posts fot the time being, you can download the slim mini 20150401 from there.

As usual, ROM download links can be found in my OP in the Builders Collective, post 14.

JP.

PS: builds for shamu uploading on both servers.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] midgarsormr:
It does work fine. I typically use Uber anyways so it works fine on latest multirom.
[Android Builders Collective] ezio84:
Had a lockscreen freeze again, but only that one so at least now it's acceptable.

The camera is still broken lol.
[Android Builders Collective] AquilaDroid:
I've tried to determine what's going on with the camera, don't know what kills it. The only way I've found to get it back is to delete it, reboot, and reinstall from play store. Doesn't last for long though.
[Android Builders Collective] Silentbob999:
Hi, I cannot associate(or see) any bluetooth device with your latest build after a clean flash.. Is it normal because of experiment to fix the lag or not?

Also, it seems like "black list" is broken in all recent build. I though that it was not showing when not implemented.. Is this a wrong assumption? Should it be working or not?

Thanks

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Android Builders Collective] Yank555:
Can't say for sure, since I don't use BT on my N5, my N6 is my daily driver.

Just checked, indeed. which was the last version to work for you ?

Blacklist should work, it's fully included in Slim base, haven't tested it lately, though.

EDIT: Works for SMS, calls I can't test atm.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] likonvampire:
Hey [MENTION=2033478]Yank555[/MENTION] i can second the BT issue but didn't feel like reporting it because I didn't want to annoy you with more bug reports after the bootloop issues on N5
[Android Builders Collective] Silentbob999:
Hi, it is the first revision that give me trouble with Bluetooth. I don't know on which rom I was before. Either one of yours, robbie. (one of the build that was laggy)

As for the blacklist. I block absolutely everything, call & text from unknown, private & wildcard ".*" because I am on a "Internet for tablet" plan, my sim number is unknown from everybody except all the spammer of the world. My real number is inside a voip app... Currently I am getting a few calls a day that are not blocked. It was also an issue on the last rom I was (last time I remember it work I was on Ezio build)

Another thing. I am not able to find expandable volume. Wasn't the case before... Can it be a clue as of on which build I was before?

Screenshot my sdcard. The last rom I was running is one of those with a modification date from either the 20 or the 21;

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Android Builders Collective] Yank555:
NP, one tiny bit more or less :D

JP.

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

---------- Post added at 08:01 AM ---------- Previous post was at 07:58 AM ----------

Laggy were all afaik, hard call. But if you miss expandable volume, it wasn't one of mine, lol, I never have added that in my builds ;)

I will have to dig in my older zips tomget behind this, I wonder if this might have started with the new vendor stuff ?

I could spin a current build with previous blobs to test, will try to check tonight after work.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] ezio84:
Camera working again, build incoming :D

Maybe this fixes it:

https://github.com/SlimSaber/frameworks_base/commit/f6cd9b4a013d40e5848398a2c02d2906817f6844
[Android Builders Collective] Mikulec:
Does that incomming build have that commit? :o
[Android Builders Collective] ezio84:
Yes, in the meanwhile i hope i didn't break anything else :D
[Android Builders Collective] Mikulec:
My true hero. ..... Now GET ME THE BUILD!!!!!!!! j/k :angel:
[Android Builders Collective] ezio84:
Try the build before saying that :D

Adding also this little jewel by master [MENTION=1228651]fusionjack[/MENTION]: https://github.com/SlimSaber/frameworks_base/commit/c800df7a0d3899d68e73a464c3f554618252da5f
[Android Builders Collective] Mikulec:
Ohhhhh, great one.
[Android Builders Collective] ezio84:
Yes, I love his quick toggles stuff too :D

I'll upload the build tomorrow after testing all the new stuff ;)

---------- Post added at 11:16 PM ---------- Previous post was at 10:33 PM ----------

[MENTION=4911350]RobbieL811[/MENTION] [MENTION=2033478]Yank555[/MENTION] this could be good to fix some bt connection issues with some car systems:

http://review.cyanogenmod.org/#/c/103111/
[Android Builders Collective] RobbieL811:
Possibly. Let's wait and see if CM merges it.
[Android Builders Collective] ezio84:
Confirmed, it works :D
[Android Builders Collective] paradoxiumwind:
Is your latest build more up to date / feature complete etc than the official beta slimLP?

thanks!
[Android Builders Collective] RP74698:
Dear Sir please share how using 280dpi for your nexus6 phone .
[Android Builders Collective] Mikulec:
Like I said, my hero. :D When do you plan to post the build?
[Android Builders Collective] Yank555:
Well I switched video to 1080p, instead of 1440p, so dpi needs adjusting, too. Been up at 300 now, though 280 trigger tablet layout, not a good idea ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] SunamY:
I'm new to slim... Wanna try it... But I have a question to the builds. I own a nexus 5 and know that the official version is beta0.5. [MENTION=2033478]Yank555[/MENTION] why is your build beta0.2??? And [MENTION=2095315]ezio84[/MENTION] why is yours beta0.6??? I'm a bit confused :D

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Builders Collective] TJKV:
So I just discovered a crazy side effect of Navbar button customizability on Lollipop based Slim. Steps to reproduce:

1. Enable a device PIN and also enable Screen pinning in Settings->Security

1.5. Screen pinning is not available when using SlimRecents, possible to add this to the long-press menu on SlimRecents?

2.Customize the Overview/Recents navbar button to switch to last app on long press (or any other random action)

2.5. While you are there, customize long press of back to kill foreground app. You will need this.

3. Pin an app (using regular recents/overview)

To unpin, you need to long press Overview. But Long pressing overview has been reassigned to some other action, hence doesn't work. Even setting it to switching to Last App breaks Unpinning.

So easiest way to get out of this is to long press back button to kill the app (Hope you followed step 2.5).

In essence, Screen pinning is totally unavailable with SlimRecents, and can be annoyingly broken when Navbar buttons are customized :p

---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------

Because names don't matter :p

For the Nexus 5, [MENTION=4911350]RobbieL811[/MENTION]'s builds are as official as it gets. [MENTION=2640853]Garrykd[/MENTION]'s builds are pretty much the same as Robbie's, but with the addition of Layers. [MENTION=2033478]Yank555[/MENTION]'s builds are Yank flavoured, just as [MENTION=2095315]ezio84[/MENTION]'s are ezio flavoured.
[Android Builders Collective] Garrykd:
The build tag is just an indication of the state the rom is. It is raised incrementally reflecting additions or changes of some significance to the source. When you build, a repo sync will update you to the latest state of the source, including the build tag. So Yank has not synced to slim's source as recently as Robbie has, and Ezio's build is the most recently synced. But, specifically, in this case, there isn't a lot of difference between beta 0.2 and beta 0.6 :)
[Android Builders Collective] TJKV:
Okay that's a more accurate explanation :p

Anyway I have one more addition to the craziness in my earlier post. It seems that somewhere along the process I detailed (probably in the last step when you pin an app), you will be granted menu buttons on either side of the Navbar as seen in the image. No amount of fiddling with Navbar settings will get rid of them until you reboot the device.

I just love these strange side effects :cyclops:
[Android Builders Collective] SunamY:
Thank you all so much :) that helps a lot :D

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Builders Collective] ezio84:
Today or tomorrow [emoji14]

PS: with 23 July gapps sometimes i still have the lockscreen lag, so Yank's April package is still the one that gives the best experience.

See posts above :D

All builds in this thread have some differences, choose the one you like.
[Android Builders Collective] Yank555:
To get out of screen pinning, you need to press both menu buttons, that's why they appear ;)

The text should be updated to say so... long time no try.

And unfortunately SlimRecents won't make pinning possible, and kill app will indeed just do that, could be disabled when pinned...

JP.

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

---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------

Hmm ... bad news, my play services auto updated to the latest :(

I noticed some lags, checked, and damn ...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] ezio84:
Damn it...
[Android Builders Collective] Mikulec:
I run two days without lag and now the lags started again.
[Android Builders Collective] TJKV:
Haha that's quite unexpected XD

But why do I have a distinct impression that it was pressing both Overview and Back buttons on Stock...

I'm on the special request build now, I'll update it's status in a day or two ;)
[Android Builders Collective] Yank555:
Because your impression is totally right ;) But with a customizable NavBar those could not be present and you could be caught in a pinned app forever, so the dual menu were introduced with SlimNavBar ;)

i'm on one, too, well it's still cooking ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] Mikulec:
He is LOLing but we, who wait for his build, are COLing. :D
[Android Builders Collective] coolek33:
Hey [MENTION=2640853]Garrykd[/MENTION]. Using your mako build on my wife phone. Works great so far. Is possible to pick more features for it? Mostly the option to disable volume adjust sound when using Vol rocker wake.

Edit: manage to disable it by switching to media sound adjust.

But if you want to pickup some other stuff from Robbies builds for example be my guest ;)
[Android Builders Collective] Yank555:
Can you give this built a test : https://www.androidfilehost.com/?fid=24052804347783370

It has a tiny faceunlock fix.

Thanx, JP.

PS: It does also lack SlimDim.
[Android Builders Collective] VictorLapin:
Just a thought guys. What launcher are you using? Can it be the culprit?
[Android Builders Collective] likonvampire:
Stock slim launcher here
[Android Builders Collective] Mikulec:
I dont think the launcher is the culprit. Nevertheless, just for the record I am using Action Launcher.
[Android Builders Collective] VictorLapin:
BTW [MENTION=2033478]Yank555[/MENTION] I can confirm BT issues in your July 25th build. Smartwatch doesn't get paired. Trusted devices work though.

Tapatalked from Slim Nexus 5

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

I'm just trying to figure out why I don't experience any lag. I'm using Google launcher.

Tapatalked from Slim Nexus 5
[Android Builders Collective] meduza:
My SLIM is extremely smooth, fast and snappy with apex.

CM 12.1 on my mobile is lagy with apex... .

m.
[Android Builders Collective] Mikulec:
Its really strange, I am using Yanks build from 25th with non Slim gapps. First two days without single lag, yesterday I had few lags at the end of the day and now its back to normal, no lag since mornig.
[Android Builders Collective] Yank555:
Nova ... since forever ...

JP.

---------- Post added at 03:55 PM ---------- Previous post was at 03:41 PM ----------

Yep, I wonder if the issue isn't linked to the vendor blob switch ?

Works on shamu, same sources.

JP.
[Android Builders Collective] likonvampire:
I really hope we can get to the root of this lag problem , i have been running stock for the past few days and really itching to get back to slim , especially [MENTION=2033478]Yank555[/MENTION] 's builds :)
[Android Builders Collective] TJKV:
I'm using Apex. I doubt it has to do with launcher, at least Apex hasn't been updated recently and it's been months since I mucked around with it's settings. Either way around 9.5 hours uptime now on a build without SlimDim, and no issues so far. [MENTION=2033478]Yank555[/MENTION] Yes it is really quick without SlimDim (And navrings maybe?)

Yeah, I really hope my hunch of it being related to SlimDim is correct...quite an annoying time to lag, when unlocking the phone to do something :p
[Android Builders Collective] likonvampire:
Is it safe to assume there is something related to slimdim ?

Maybe i should find a latest build without slimdim..

EDIT : Is there a [MENTION=2033478]Yank555[/MENTION] build for N5 without the slimdim?
[Android Builders Collective] PerfectSlayer:
Sure, I test it right now and I will report after 20h+ uptime (gapps updated in my case).

Nova for me!

SlimDim increase the issue but it's not the cause. Lags still appear after some days..
[Android Builders Collective] TJKV:
Yes, I felt I just had to test one build without SlimDim, I begged Yank to make one for me without the slimdim commits yesterday (My build system is down for routine maintenance). Running it now, no issues so far. I'm sure Yank will share it if he wants to...if not don't worry I will report everything I see!
[Android Builders Collective] PerfectSlayer:
Today? Are you upgrading your build system to Windows 10?? :silly:
[Android Builders Collective] kantjer:
Done that about 10 hours ago ;)
[Android Builders Collective] TJKV:
Trying to :laugh:

"Build system" is actually a VM running on my primary computer, so not doing anything on it till I can get that Upgrade figured out :p

Just hanging around the MDL Windows 10 forums and some subreddits while I wait for something to happen. Just not this though.
[Android Builders Collective] Yank555:
I have a build ready for shamu, let me compile it for hammerhead as well...

It is a full featured build with just SlimDim removed, and a tiny faceunlock fix.

The testbuild I made for TJKV is a 100% stock Slim with SlimDim removed (no added features at all), that I only have for hammerhead.

Give me a little, I'll upload them, will post when done.

So far the build for shamu has been just as I hoped, crossing fingers it'll last !

JP.

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

Edit :

Build for shamu already up, I had uploaded it earlier : https://www.androidfilehost.com/?fid=24052804347783370

Build for hammerhead (stock Slim as of 2015-07-23 with SlimDim removed) : https://www.androidfilehost.com/?fid=24052804347783558

Build for hammerhead (full featured with SlimDim removed) : https://www.androidfilehost.com/?fid=24052804347783570
[Android Builders Collective] kantjer:
Using Mint on VirtualBox and everything is still working after the Win10 update
[Android Builders Collective] VictorLapin:
I've also upgraded Mint to 17.2 without any issues

Tapatalked from Slim Nexus 5
[Android Builders Collective] Mikulec:
Is that little faceunlock fix the one Ezio posted? The fix that brings back the animation? And would you mind including the other fix Ezio mentioned: http://xdaforums.com/showpost.php?p=62067772&postcount=6914

---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------

I am still waiting in the line for the notification. I wish there was other way to download the build (official way offcourse).
[Android Builders Collective] likonvampire:
Just a FYI [MENTION=2033478]Yank555[/MENTION] , had to flash EX kernel to get rid of bootloops
[Android Builders Collective] kantjer:
There is, I used the media creation tool

I wanted a non-standard language so opted for the "create installation media" option (that lets you choose the language for the iso), let it install on a USB and stared the setup.exe from within the current Win version.

Upgrade took about 20 minutes.
[Android Builders Collective] Mikulec:
wow, thanks, didnt know that. already downloading it. did all your installed programs work after the upgrade?
[Android Builders Collective] kantjer:
Yes everything is working

Sent from my OnePlus One
[Android Builders Collective] Yank555:
No kernel change in the ROM, I have no idea why some get bootloops, if you do, flash a different kernel over, I don't have a different solution unfortunately.

JP.

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

---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------

Nope, this one has been posted to gerrit less than a day ago, it's not a visual fix, but a code fix.

Will check for the other commit you mention, for a next build. Remind me if I should forget, the todo list is growing ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] Mikulec:
I am posting both commits that [MENTION=2095315]ezio84[/MENTION] mentioned:

https://github.com/SlimSaber/frameworks_base/commit/f6cd9b4a013d40e5848398a2c02d2906817f6844

https://github.com/SlimSaber/frameworks_base/commit/c800df7a0d3899d68e73a464c3f554618252da5f
[Android Builders Collective] ezio84:
About the data tile: i pushed the commit to the Gerrit, for Slim something needed to be changed (otherwise you need to add more new stuff Slimsaber already had):

https://review.slimroms.eu/#/c/6795/

---------- Post added at 11:12 PM ---------- Previous post was at 10:45 PM ----------

Ok, build boot fixed :D

I'll upload it tomorrow (maybe for real this time, lol).

Also noticed this:

https://github.com/ezio84/vendor_slim/commit/d882960dcbe72f00dd302e3265bec9e59ee7f49d

Restoring the default dpi value to the stock device one let's avoid the corruption of some elements after a clean flash (on previous builds you needed to set again the dpi value under Display).
[Android Builders Collective] PerfectSlayer:
I wonder if I am the only one but I can't switch Chrome tabs from swiping the navbar anymore :(

Is it related to Chrome or it's due to the mod made in Slim of the navbar?

For those who don't know the feature: http://www.androidpolice.com/2015/0...me-by-swiping-across-androids-navigation-bar/
[Android Builders Collective] Mikulec:
[emoji24]