yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
Best is to pick from here : https://github.com/LayersTeam

I'd just go pick these "Layers 2.1 (backwards compatible)" commits (those are squashed to 2.1), what comes after that, maybe, if you know why you'd want them, some might be "experimental" (as in WIP) ;)

JP.
[Android Builders Collective] Minux31:
Thank you, I've applied open commits for now, if something comes wrong with this, I'll revert all and use your method :)

Let's test now !

Edit : I made something wrong, after boot, no navigation bar nor status bar, i've got to get back in my code ...
[Android Builders Collective] colida:
Hi, can somebody point me to the setting where I can hide the alarm clock icon in yanks latest build on hammerhead? I am using "sanfter Wecker" as my primary alarm clock app.

Thanks in advance
[Android Builders Collective] Mikulec:
In the clock app, there is a setting to hide the icon.
[Android Builders Collective] colida:
Perfect! Thanks
[Android Builders Collective] Phazmos:
Is timeservice present in this?

Was missing from last build.
[Android Builders Collective] ezio84:
Ye, open commits in the rro2.1 tag are all fine, I'd avoid the abandoned ones atm because they require compatible themes.
[Android Builders Collective] Mikulec:
Whats that? If I may ask. :o
[Android Builders Collective] Phazmos:
Far as I know, it syncs time on boot.

Example, reboot, time is off and date is sept. 2001, or something like that. Then, 10 or 15 seconds later correct date/time shows.

Throws off my tib auto back ups, and may do the same with other time/date sensitive apps/processes.
[Android Builders Collective] colida:
That is the exact behaviour I can see in this rom. But it does not bother me.
[Android Builders Collective] Phazmos:
Doesn't really bother me either, but it does bother tib bu schedules for sure.

Have seen this many times over the years. Every now and then this apk gets missed on some rom, then added back in next build.
[Android Builders Collective] Yank555:
It used to be in the device tree, I didn't change anything about it ... would need to check.

JP.

PS: When booting to recovery without timeservice, time should be totally off in recovery. Is that the case for you (it's fine on my end at least).

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] Failyx:
Sorry [MENTION=2033478]Yank555[/MENTION]

It was too early in the morning ?

I meant the ring targets, btw thank you for your frequently builds. Everything i need plus high performance and battery.?

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Builders Collective] Phazmos:
I've never been able to get correct time to hold in recovery - twrp, or cwm, when I used to used that.

Never bothered anything, so never minded.
[Android Builders Collective] Yank555:
Works fine on my end, backup names sport the right time (given you've set your timezone in recovery).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] Phazmos:
I'm always off by an hour - dst never works out to correct time.

I worry more about my golf grip than time in recovery!

Edit - just an fyi - pulled the apk from another rom, dumped to system/app, set permissions, installed and time is working properly again.
[Android Builders Collective] Yank555:
Handling dst needs to be done by the ROM, so here recovery (just as timezone does). Time will always be UTC in the device's RTC.

And I wasn't saying time in recovery was important, but without timeservice, recovery would be somewhen in 1970 or so, so it was just an indicator.

Mind sharing what file exactly you changed (where you got it from) ? I might change it in the device tree and all would profit from it ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] DroidIt!:
Same here ;)
[Android Builders Collective] Phazmos:
I loaded a bu of chroma - copied timeservice folder to sd. Only thing in folder was the apk.

Restored a bu of your latest and did as mentioned above.

Enjoy!
[Android Builders Collective] Yank555:
Strange, checksum doesn't fit chroma's github...

But I've seen we still have an earlier timeservice apk in our vendor repo, will update it to the latest and we'll see.

JP.
[Android Builders Collective] mslatter:
D850 update.

NEW: CM Navigation Ring Targets (Thanks JP!)

RRO layers

Add alternate WebView provider package

SlimHeadsUp: Add a global 3-way switch

Flip to Mute (enable in call settings)

Accidental Wake up OFF by default

Latest Kernel, G3 and D850 commits

Also, removed the following (install app to replace):

FMRadio / HTMLViewer / wallpapers / Camera2 / Calendar

1. Full Wipe (am told dirty flash works)

2. Flash Rom

3. Flash Gapps (I used Slim's gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu

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

MD5: 11ce1b445fae0a249a4d9218c3abdfe7

Changelog is all new merges since last build from this link:

https://review.slimroms.eu/#/q/status:merged

- Namely

Bumped product version

Dim Nav buttons!

Huge thanks to the following for making all this possible:

Slim Team - for a great ROM

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!
[Android Builders Collective] Yank555:
Checked on shamu (as is, last rom zip), the time is set some 259 miliseconds after logcat start (check screenshot below), and 24ms before Android starts, as such no TiBu can be affected by this, as no app has been started yet.

But, which device were you actually talking about ?

I assumed shamu, but since we're in the BC thread and I build for 4 devices ... I'm not so sure anymore :confused:

If it's a different device, I'll have to recheck on that specific device.

JP.
[Android Builders Collective] Phazmos:
Device is hammerhead.

Oh, I believe the date change screws up tib. I have it set to bu daily at 3am. The jump from 2001 to 2015 triggers the bu.
[Android Builders Collective] Yank555:
I have TiBu set up the same, but that's on shamu, and as you see, no issue, time is set before any app is started.

On HH I will have to check, will let [MENTION=4911350]RobbieL811[/MENTION] know about this, maybe this needs updating in the 'new' vendor repo we're testing because of the BT / streaming issues.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] Phazmos:
I'm sure you'll find out what's up. Folks always do.

I can make it work easy enough so I'm a happy camper.
[Android Builders Collective] RobbieL811:
I don't understand what's going on.
[Android Builders Collective] Phazmos:
Readers digest condensed version - timeservice.apk not included in yank's latest hammerhead build.

I'm afraid he has to take it from there - I gotta whack these little white balls across 3 or 4 miles of Vermont countryside!
[Android Builders Collective] Yank555:
I'd add to this that I suspect it's missing or not the right one in the "Google"-ish vendor blobs we're testing at the moment, but haven't had a chance to look at it, as I've been looking into shamu as I wrongfully assumed we had been talking about shamu here :cowboy:

JP.
[Android Builders Collective] Minux31:
New LG G3 D855 SlimLP Beta 0.2 personnal build : https://basketbuild.com/devs/Minux/d855/SlimLP

Features from official SlimLP :

- Alarms and no interrupt zen mode

- Allow/Prevent notification light in Zen mode

Changelog :

- Merged latest slim sources (with SlimDim :cool: )

- more FR traductions

More to come (layers will come ;) )
[Android Builders Collective] likonvampire:
I have tried downloading the ROM 3 times and i can never get it up and running , bootloops endlessly from slimlp .

Any suggestions ?
[Android Builders Collective] Yank555:
Let's start at the very base ;)

Nexus 5 ? If I can trust your signature.

Do you use multirom ? If so, it won't work, the kernel that comes with the device lacks support for it. You could flash the ROM, flash a kernel that has multirom support and it should work.

Did you dirty flash coming from a different SlimLP ? If so, might be "normal".

--> Always try this to rule out other issues :

1) Nandroid (so you can get back where you are)

2) fullwipe (don't wipe sdcard, you'd lose your nandroid unless you have it on a thumb drive !)

3) flash ROM, gapps

If that does not work, we can work on it, else it's mostly closer to voodoo magic to be able to help :(

Still willing to try to help, just less probabilty to get it sorted ;)

JP.

PS: I have the build running fine on my N5, just dirty flashed on top of my previous build, as usual.
[Android Builders Collective] likonvampire:
Yes this is a NExus 5

No i do not use multirom , use the latest TWRP.

Came from stock ROM clean flashed ( been doing that for a while ) .. Tried flashing another custom ROM and it booted up fine but I am more of a Slim guy so i would to run it on my device :)

I do have the stock nandroid , just booted back to it right now.

Flashed ROM , latest gapps with multi dpi addon followed by Super SU

Edit : RobbieSlimLP -hammerhead from this morning boots perfect ... IDK what the issue is now :P

Thanks for your help , much appreciated !
[Android Builders Collective] Yank555:
Hmm ... oky, what exact file are you using ?

Btw, no need for multi dpi if you run Slim ;)

Which gapps are you using ?

JP.
[Android Builders Collective] likonvampire:
I used the latest upload from I believe it is from 16th July if I am not mistaken .

I learned something new today about the multi dpi addon not required for slim [emoji1] , thanks a lot !

Flashed the zero gapps from 16th.

For some reason all is good on Robbie's hammerhead build .. No idea why
[Android Builders Collective] Yank555:
You should have the latest (Slim-hammerhead-5.1.1.beta.0.1-UNOFFICIAL-20150716-0102.zip).

Could you do a test for me, cleanflash Slim, don't flash gapps and boot up, see if it boots.

I've had issues with new gapps, maybe it's linked, maybe it's not.

JP.
[Android Builders Collective] Mikulec:
Looks like he is getting the same bootloops as me. [MENTION=4863880]likonvampire[/MENTION] could you afdter u get the bootloops go to recovery and flash some custom kernel (for example ElementalX), that should fix the bootloops and the rom should boot fine. Try that.
[Android Builders Collective] likonvampire:
Will try and report back .. [emoji1]
[Android Builders Collective] Yank555:
Seriously ??

Aha, which kernel helps ?

N5 we're talking in both cases ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] Mikulec:
I only tried ElementalX, and yes we are talking about N5. But I thought its a problem on my side, because I was dirtyflashing your builds (at least I think). Judging by the number of download of your builds and the fact that we are probably the only ones having problems, its probably on our side.
[Android Builders Collective] Yank555:
Still would like to understand :D

So this happens on clean AND dirty flashes, right ?

I've tried latest gapps yesterday, and that screwed up my shamu (had a backup) ... I restored and used the old 20150401 mini gapps, and all was fine.

Maybe linked ?

Does Elemental bring its own ramfs ?

JP.
[Android Builders Collective] Mikulec:
I cant really remember if I got bootloop after a clean flash. And regarding ElementalX kernel and ramfs, I have no bloody idea. :o
[Android Builders Collective] Yank555:
I should have a little time tomorrow, will try to do some testing.

And for the kernel, I'll check that ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] amphi66:
For what it is worth, I also had bootloops w/ [MENTION=2033478]Yank555[/MENTION] Roms starting about 3 revisions ago, but not w/ [MENTION=2095315]ezio84[/MENTION] or [MENTION=4911350]RobbieL811[/MENTION]. I assumed it was just me and stuck w/ ezio's. (Hammerhead)
[Android Builders Collective] Phazmos:
It's missing. Should be in system/apps, but it's not.

---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------

Check your "clean" flash. I did a proper clean flash, as always, and no problem booting.

If confused

http://xdaforums.com/showpost.php?p=60786190&postcount=3743
[Android Builders Collective] RobbieL811:
I added the timeservice stuff it's in my latest build and also in the blobs in my Github account. Oh yeah, what did you shoot???

Check my git. Timeservice was missing. I also added a load of other stuff.

Read above.
[Android Builders Collective] Phazmos:
Thought that was the case. Been seen before, more than a few times.

What'd I shoot - my 5 wood! Been acting up anyway.

Nah - still love it - 39 for 9, then an 81 for 18. But I was in a rush. They had a big tourney going in the afternoon so I had to hurry to get 27 in. Not too bad for squeezing 27 holes in under 3 hrs.
[Android Builders Collective] DroidIt!:
:) I usually float around 100ish...maybe I should stop going to Hooters and having a few with my dad and brother before we hit the links [emoji56]
[Android Builders Collective] Phazmos:
A few never hurt - but a few more is another story!

I've been playing for over 30 years - I should be better than I am, but I'm just getting back into it the last couple 3 years. Had to take a 5 year break due to back problems, which were caused by playing too much golf - with the wrong swing.

Helped out the club where I'm a member with a computer problem earlier in the year and got some help from the pro - who happened to be long drive champ 2 years running. Now I'm back to 36+ holes a day and I can still walk when done.

If you're into it, a few lessons can be a wonderful thing. I thought I needed back surgery the pain was so bad after playing. A few tips from someone who knows what they are doing and I've been pain free for 3 months. Truly amazing, life changing even!
[Android Builders Collective] ezio84:
Guys please don't install the build I pushed (and removed) yesterday on afh, it had a huge lag problem when unlocking the phone after screen off due to some blobs.

Now it's fixed, I'll push the new build later today ;D
[Android Builders Collective] Yank555:
Yep, intended to do just that later today ;) Thanx !

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] PerfectSlayer:
[MENTION=2033478]Yank555[/MENTION] on your latest builds on shamu, I get lags on the lockscreen.

I mean, power button or moves light on the screen but it does not draw time, notifications or patter unlock when I swipe up. Sometime, I just have the background, sometime the screen only draw black.

I have to switch off an on the screen (even several times) to get the pattern unlock displayed and working. Am I the only one? Thanks!
[Android Builders Collective] Yank555:
Which was the last that worked fine for you ? So I can check on what actually changed in the meantime...

I did notice sth strange on the lockscreen, too, although I don't quite understand what it could be, only SlimDim was added before I noticed it first, but I don't quite see what could be the link...

JP.
[Android Builders Collective] PerfectSlayer:
For example, it seems to work better on 20150715-0821 than 20150715-2359 (which feels really bad :()
[Android Builders Collective] Yank555:
I may be wrong, but the only difference would be SlimDim ?!

Could you disable it and see if that changes anything ?

JP.
[Android Builders Collective] PerfectSlayer:
I will try the whole day then report you tomorrow. But I don't think SlimDim is in cause I had the issue before it was included.. Or the previous lags was due to camera issue with face unlock and the new ones due to SlimDim?
[Android Builders Collective] ezio84:
Check the logcat when screen is off guys, do you have some QCOM stuff errors spamming?
[Android Builders Collective] Yank555:
Honestly I don't think it is linked, but I don't see what else changed between the 2 versions...

JP.

---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------

Can't say I can see anything qcom related on my end.

JP.
[Android Builders Collective] PerfectSlayer:
I will check as soon as I grab a computer after finishing my current familly trip! :silly:

(I never found a usefull logcat viewer an Android…)
[Android Builders Collective] ezio84:
Or maybe the new commits in frameworks native? I noticed some "native" lines too in the logcat.

Now at sea, can't check better [emoji14]
[Android Builders Collective] Yank555:
Well it may be interesting to test the last build before July 14th (last time I repo sync'ed)...

[MENTION=2822685]PerfectSlayer[/MENTION] : Maybe worth a try ?

JP.
[Android Builders Collective] Thecrazyskull:
Show me the exact qcom error spam :p
[Android Builders Collective] ezio84:
I thought the lag on hammerhead was due to that qcom error spamming but after fixing it, today i noticed the lag again in some situations (always when unlocking the phone after screen off).

So there's still something crap :D

I don't have the log anymore, it was due to these missing binaries:

https://github.com/ezio84/proprietary_vendor_qcom/commit/4651d5712b0805434fb84b9430e5d06fcf906d10
[Android Builders Collective] Mikulec:
OK, that makes us 3. :D I also had no bootloops on other roms.
[Android Builders Collective] Mikulec:
[MENTION=2095315]ezio84[/MENTION], btw you might be better informed than me. Any news on the missing lockscreen animation while using Smartlock feature?
[Android Builders Collective] Yank555:
Well I've wiped my HH clean, flashed the ROM, gapps and SuperSU and all went as expected ?!

Bootloader / Radio ? (wild guessing here)

I'm running HHZ12h bootloader and M8974A-2.0.50.2.26 radio.

JP.

---------- Post added at 06:56 PM ---------- Previous post was at 06:13 PM ----------

Indeed... could be, but what is causing it ?

I flashed back the first build I made after last repo sync (20150714-2210), from there, there are only few changes that went in.

Animation seems 'normal'.

JP.
[Android Builders Collective] ezio84:
No news on that [emoji14]

Did your 20150714 build have the cm Per-app performance profile commits:

https://github.com/ezio84/frameworks_base/commit/5c4eb4c7aca74d0fb9ede476ad758a67bc408606

https://github.com/ezio84/frameworks_base/commit/9481e15ec1cb5444701018303a21a825f8f02bfa

https://github.com/ezio84/frameworks_base/commit/b7de4f5e51f6d23f1f157ca13723c9c6ab848c19

Out of curiosity, i'm gonna try to revert them and see what happens (they handle the power manager service, so...)
[Android Builders Collective] ralpheboyo:
Ezio like BBC news....

1+1 Ultra~LP~5.1.1
[Android Builders Collective] Yank555:
Yep, they came with the repo sync (I sync'd right before that build), I didn't add any of them myself.

JP.
[Android Builders Collective] Mikulec:
BBC is like a small brother to ezio. lol

---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------

Same bootloader, same radio. I might clean flash your next build just to see if I get the bootloop after clean flash.
[Android Builders Collective] Yank555:
Well if you feel like it, my next is alread up :D But didn't announce it, only updated SlimDim to latest, and HH has the vendor stuff Robbie added.

I uploaded a new one a few hours ago ;)

JP.
[Android Builders Collective] Mikulec:
Titanium backup already running. Will report back.

---------- Post added at 08:52 PM ---------- Previous post was at 08:34 PM ----------

@Yank555 bootloop even after clean flash. I flashed rom, gapps, lollipop sounds and SuperSU 2.46
[Android Builders Collective] ezio84:
Hey Ralphy!!!!!!

Nice to see you around :highfive:

I've reverted these:

https://github.com/ezio84/frameworks_base/commit/5c4eb4c7aca74d0fb9ede476ad758a67bc408606

https://github.com/ezio84/frameworks_base/commit/9481e15ec1cb5444701018303a21a825f8f02bfa

https://github.com/ezio84/frameworks_base/commit/b7de4f5e51f6d23f1f157ca13723c9c6ab848c19

https://github.com/ezio84/packages_apps_Settings/commit/e1816b6e1dc8f723ae81b35b9bcfb70e53cbb977

https://github.com/ezio84/packages_apps_Settings/commit/8d07a62188b54a5d98cf89406e11e9dfb285798d

Atm no lags/lockscreen freezes, let's see how it behaves within next hours :rolleyes:

EDIT: or, if it won't be fixed, i was wondering about Deskclock widget: could it be the culprit? I just saw some fwbase commits related to widgets and drawing services.

Lol :D
[Android Builders Collective] Yank555:
Try the just flash the ROM, no gapps, no sounds, no supersu just to see if it boots. I don't get it, me it just boots right away :eek:

Dankoman has disabled SlimDim on lockscreen, seems to do the deed. Compiling, about to test.

JP.

EDIT :

Works ! Put everything back in and add this : https://review.slimroms.eu/6630

JP.
[Android Builders Collective] ezio84:
Indeed, had lag again after reverting cm performance stuff, now with Dan's fix it seems really ok :D

Edit: [MENTION=2033478]Yank555[/MENTION] not fixed yet, sometimes the lockscreen freeze is still here.
[Android Builders Collective] damngood98:
would this be the latest available that's posted?
[Android Builders Collective] Yank555:
No, not yet pushed, compiling all 4 devices atm.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Android Builders Collective] Yank555:
Strange, it fixed it for me on HH, Shamu and Flounder (haven't tested Flo).

JP.
[Android Builders Collective] ezio84:
It happens very less times, i don't know if it's still related to SlimDim.
[Android Builders Collective] Yank555:
ROM Update SlimLP beta 0.1

Maintenance update, SlimDim is updated to not be active on lockscreen, which removes the lockscreen sluggishness.

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

JP.

PS: shamu, hammerhead, flounder and flo are up on both servers.
[Android Builders Collective] Minux31:
New LG G3 D855 SlimLP Beta 0.2 MinuxBuild 20150719 : https://basketbuild.com/devs/Minux/d855/SlimLP

Changes :

Sync with latest SlimLP Sources (https://review.slimroms.eu/#/q/status:merged)

- Alarms and no interrupt zen mode

- Allow/Prevent notification light in Zen mode

- RRO 2.1 support (thanks to [MENTION=2095315]ezio84[/MENTION] and [MENTION=2033478]Yank555[/MENTION])

Sources of my modifications : https://github.com/Minux31?tab=repositories
[Android Builders Collective] likonvampire:
Hey the new build booted up fine with no issue or bootloops. Good stuff !!
[Android Builders Collective] Yank555:
Then I suppose Robbie's changes to the vendor stuff did the trick ;)

JP.
[Android Builders Collective] Yank555:
ROM Update SlimLP beta 0.1

Another maintenance update:

NavRings are now fully slimified (use SlimActions rather than static actions, thanx to [MENTION=6048392]kagwind[/MENTION] for most of this, it made finishing it pretty easy ! ;))

I've added another fix that should reduce SlimDim impact on lockscreen (and in general)

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

JP.

PS: shamu, hammerhead, flounder and flo are uploading on both servers.
[Android Builders Collective] PerfectSlayer:
Right now, I want to try the [MENTION=2095315]ezio84[/MENTION] sea! I'm currently in Normandy (in France) and the sky goes well with the sea.. They both are gray..

I have an animation on my lockscreen when smartlock is enabled but it doesn't stop when your face is recognized or not [emoji53]
[Android Builders Collective] ezio84:
Atm your fix plus Daniel's one seem working well, thanks again :D

France is awesome but we have more sun [emoji14] :D
[Android Builders Collective] Mikulec:
I am talking about the anmation when u have trusted face as smartlock and the phone recognizes your face. The lock icon should change from locked to unlocked to show you that the phone has been unlocked by trusted face. This does not work.
[Android Builders Collective] PerfectSlayer:
Nope, this doesn't work. But the circle animation (around the lock) doesn't stop either if the smartlock failed to recognize your face.