yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] ezio84:
Meanwhile, playing with Slim recents. These are my favourite colors:

Panel background: Color #AC000000 - Opacity 67%

Card background: Color #CF37474F - Opacity 81%

Card text: Color Color #FFFFFFFF - Opacity 100%

Immersive mode: Statusbar Only (i think it gives the best animation-functionality)
[Android Builders Collective] csolanol:
Hi Ezio, made a pull request to your github for spanish translations. It is just a test, if you will merge it i will continue doing it.
[Android Builders Collective] ezio84:
Glad to merge it! :highfive:

But atm i don't see your pull request on github :silly:
[Android Builders Collective] VictorLapin:
[MENTION=2033478]Yank555[/MENTION] found a bug in 0.96 - battery light is still yellow at 100% charging.

---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------

That vertical shift of card header with size > 100% really annoys me... :( Too bad I didn't find out the cause.
[Android Builders Collective] csolanol:
Well i did it from github website and i can't find it now lol.

Will do again.

---------- Post added at 12:19 ---------- Previous post was at 12:06 ----------

Could you check it now please?.

Ty.
[Android Builders Collective] ezio84:
You mean the cards header height, right? Maybe we can just set it to a fixed size, within a range of the panel size (for example: till 80%, set it to XX pixels, from 81 to Max set it to YY px).

Merged, thanks dude :highfive:
[Android Builders Collective] VictorLapin:
I mean app name vertical alignment. It is centered at 100% and top-shifted at >100
[Android Builders Collective] ezio84:
Ah right, it's shifted also at <100.

And i agree with you, it'd be better if always centered.
[Android Builders Collective] limjh16:
Bump please...?
[Android Builders Collective] Yank555:
It's not a bug, it's a feature :D

The commit comment reads : "Only consider battery full

when we are done charging

" (not when we reach 100%) :D

So being at 100% is not enough, full is when actually charging the battery stops.

Here you can see the difference :

https://github.com/YAOSP/frameworks...958#diff-e93a7463d53a667604c9fe5277aa054cR785

When you stick to 100% for a little time, it will turn to "full" color, that's when we reach "BATTERY_STATUS_FULL" which (oddly, I admit) is not the same as "level == 100" ;)

JP.

---------- Post added at 14:34 ---------- Previous post was at 14:30 ----------

I looked at this the first time you posted, no idea, never faced those errors (btw, hastebin links don't work anymore).

But I'd advise before playing with "fancy" toolchains, maybe it's best to get started with the indended ones... and then go step by step if you really want to use those toolchains.

On a sidenote, using "fancy" toolchains has never helped (me) in any way, all it did was create way more trouble than benefit (hence why I call them "fancy"). But that's just my very personal oppinion, nothing more so don't take it as a biblical statement and do your own experimentations ;)

JP.
[Android Builders Collective] limjh16:
1. Oh whelps basically something wrong with dex2oatd which I did not understand [MENTION=4546441]Twiq[/MENTION] instructions to fix.

2. The error happened before using a custom TC

3. Won't custom TCs make battery life better and ROM smoother? Correct me if I'm wrong.
[Android Builders Collective] Yank555:
Well that is what I'd call more or less urban legend, esp. talking battery life ... but whatever the difference, it will never be worth my time managing to "keep the source compatible" or "live with whatever it breaks".

Note these conclusions are from a time I only compiled kernels, but I've never regretted investing my time otherwise than playing with latest TC ever since I did a blind (kernel) test and everyone voted for the Google stock TC kernel versus linaro back then (150+ votes). Until I revealed which kernel was compiled with which TC and suprise surprise votes shifted strongly towards linaro, so that said a lot, placebo here we come ;)

Personally, after having gone the way, I prefer to use the TC the code was "kind of made for" and rather invest my time adding features (or fixing details in features) instead of working to achieve the same with a different compiler.

But as I said, best is you go that way yourself, so you can make a mature decision based upon your very own down to earth findings, just stay honest with yourself along the path :D And then stick to whatever works best for you, there's choice out there, and that's a good thing ;)

JP.
[Android Builders Collective] adm1jtg:


Battery light send fine for me but I did notice after it hits 100% it sure seem to take and extra few minutes to change color... But it sure eventually change

Just noticed this was explained earlier
[Android Builders Collective] VictorLapin:
Guess I was impatient :D
[Android Builders Collective] ezio84:
[MENTION=5790246]VictorLapin[/MENTION]

Title centering fixed :D

https://github.com/ezio84/frameworks_opt_cards/commit/9687b9f504909ca1f1b0b4c9516c60bcc3f781b8

We were centering the text frame, but not the text itself ;)
[Android Builders Collective] dankoman:
not this nightmare again :p

---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------

:good:
[Android Builders Collective] ezio84:
Add this commit too :D

https://github.com/ezio84/frameworks_opt_cards/commit/405536eff5b1277f2dfa3d556e4eb13a9bc63105

It removes the "android:textAlignment="center"" (it was centering the text horizontally), "the android:gravity="center_vertical"" line is enough to fix our issue.

Horizontal centering doesn't play nice when the panel size is set to 100%, because 2 rows text is center but 1 row text still starts from left.

:good:
[Android Builders Collective] franatic08:
Would SlimPie be a nice addition for YAOSP? Or won't it run on MM Roms?

Sure like where this ROM is headed!

Thanks for your efforts!
[Android Builders Collective] Yank555:
Well personally I use LMT, have been using it since lik forever, so I see no point in including SlimPie in my use tbh, because LMT has a few things I use which SlimPie lacks (like what I call the finger extender, which on 5.5"+ devices is really nice in onhanded operation).

So I don't think I'll be adding it, not soon at least, since I'd keep it disabled myself, I have still a few other things on my list ;)

JP.
[Android Builders Collective] franatic08:
Thanks for clarifying.

Your ROM, your choice.

Looking forward to your other things on the list.
[Android Builders Collective] limjh16:
http://hastebin.com/huxileriji.vbs

this happens with/without custom TC when trying to compile slimsaber. Could you help? until now whatever I tried doesn't work.
[Android Builders Collective] ezio84:
Stupid question: did you do a make clean (and also tried to reset ccache) after switching from a toolchain to another one?
[Android Builders Collective] limjh16:
this error happened on my first build. Then I tried it with uber tc because I do not know anything about the nature of the problem and just maybe changing a tc may help, but exact same error. This is my 2nd ROM so I'm sorry if im just retarded.
[Android Builders Collective] ezio84:
Have you set openjdk 1.7.x as default in your distro? And which distro?

It shouldn't be related to that specific dexoatd problem but you know, software stuff is weird :D

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

PS: did you try to build another rom, for an officially supported device? Just to be sure that your building environment is correctly set.
[Android Builders Collective] Yank555:
I've never seen this kind of issue ever, so no idea... But I think you should indeed follow ezio's advice and validate your building environment, not that you have some lib missing or sth. thelike

JP.
[Android Builders Collective] likonvampire:
[MENTION=2033478]Yank555[/MENTION] I am back on YAOSP after a long time and running the latest build , just wanted to confirm if slim recents was included in your latest build. I can not seem to find the option anywhere
[Android Builders Collective] ezio84:
PureNexus mod 6.0.1-20160224 :D

Download for Hammerhead: https://www.androidfilehost.com/?w=files&flid=50100

Changelog:

PureNexus source sync @ today

PureNexus lockscreen config:

- Keyguard alpha and Keyguard Bouncer alpha

- Secure Lockscreen Bouncer Bypass configuration

Main Settings menu customization (set it in the Display menu):

- Dashoard tileview dividers toggle

- Dashboard tileview double lines toggle

- Configurable dashboard columns

Add always quick pulldown option

Layers: dynamic backup script (no custom layers loss after a dirty flash)

Additional IT end ES translations

SimRecent: Fix card header title centering when the panel size is not set to 100%

Installation, tips, info: check the 6th post of this thread: http://xdaforums.com/showpost.php?p=55121776&postcount=6

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] VictorLapin:
Nope, stock AOSP recents
[Android Builders Collective] adm1jtg:
Read back a few posts he answered that exact question
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION] Everything running great no issues at all. Actually bored to tears as there is nothing to change or tweak or test. Reading through tons of posts and was curious about your opinions on the following:

The latest Qualcomm Adreno GPU Drivers apparently released only a few days ago.

The latest CAF sound drives like those used in the now defunct hydra kernel.

I have seen raves about each especially the CAF sound drivers. Some have said the new drives by themselves rival V4A quality

Just curious on your opinions and if you agree there is a benefit to either if you will be implementing either in future builds

As always will be happy to test anything you roll out

Thanks for all your great work and such a stable rom/kernel combo
[Android Builders Collective] Yank555:
Well CAF base will always be the latest for QC hardware, as such that can only be improvement compared to AOSP, since it's newer (AOSP QC stuff comes from CAF, it's just older).

The drawback, though, is also newer can mean new bugs ... CAF is rather 'experimental'. I still have a very bad memory of CAF updates and the Note 3, my device was rendered useless, it rebooted several times a day, and since Sammy impeeded a BL rollback, I was stuck with way to rollback, it didn't boot on the old kernel base anymore and that made me buy a Nexus (hh back then) and put my (rather new) Note 3 in a drawer.

So I've mutated into the rather old scholl kind of guy by now, rather a tad less cutting edge but proven stability :D

Could have a look, though, if it's kernel-side only, an no ROM-side changes are needed...

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.96
[Android Builders Collective] t0mas_:
[MENTION=5790246]VictorLapin[/MENTION]

I tested your yaosp build for hh and I have a problem restoring Google account backup/restore during initial backup I login with my Gmail, and I get to the screen where I can confirm which backup I want to use. but when I click next, after a while the same screen pops back up,the one that let's me choose. which backup to restore. I have tried slim and open gapps, both with same results. does anyone else have this problem? is there anything I can try?
[Android Builders Collective] VictorLapin:
Hmm, I can't remember whether I was using this feature, I could do a completely clean install... Anyway, there were no issues.
[Android Builders Collective] Yank555:
That is indeed a known issue (gotta put that on the official known issues list).

I had the same reported on other devices ... unfortunately I don't know what the issue is atm, and haven't had the time to look into it either :(

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.96
[Android Builders Collective] limjh16:
1. yes ubuntu with KDE plasma desktop environment if that helps. JDK 1.7.XXX

2. I am building a ROM at the same time for slimROM (not slimsaber just slimrom), will that affect? If it does ill just delete the repo first.
[Android Builders Collective] idkidk:
Hi Ezio,

Simple question, can i dirty flash your slimmed PureNexus rom over original PN?

Thanks for your work!

Bye

idkidk
[Android Builders Collective] acultr:
it's worked for me, but wipe system manually before you flash
[Android Builders Collective] ezio84:
No need to remove the other repo. As said above, just try to build another rom (like slimlp, or purenexus, or other ones) but for a device officially supported by that rom.

It should work well. Wipe system, because i've removed some stuff from the official source. Then flash rom and gapps.

EDIT: ninja'd by [MENTION=4465948]acultr[/MENTION] :D
[Android Builders Collective] limjh16:
so I just build it and re-build for my device? Because I only own 1 device and that device isnt supported by any slimrom officially
[Android Builders Collective] tofu:
SlimLp minuxbuild 12.2.2016 on Oneplus one.

Two questions:

1. Any way to get some transparent background gradient for status bar, because you can't see the symbols if you are using light colored wallpaper? I think KitKat and marshmallow have slightly faded/dark status bar background.

2. Any way to get weather for home screen clock? Or lock screen?
[Android Builders Collective] kantjer:
Just try building for a official supported device (even if you don't have that device)

You first need to make sure your build environment is OK.

If the supported device is building than you can start figuring out what you missed.

But you aren't making life easy on yourself by starting your build career with porting a ROM to a non supported device. That's not an easy thing to do.

I would suggest finding a ROM source that officially supports your device and start with that.
[Android Builders Collective] ezio84:
Build for hammerhead, or mako.

So you can be sure that your building environment is well set.
[Android Builders Collective] limjh16:
Oh okay, because slimLP builded but not slimsaber. But I feel its no fun since nothing to do for alrd done stuff, so I wanted to kinda challenge myself.

Ill try 2 days later when its weekend.
[Android Builders Collective] dankoman:
which gapps version? can you check app info for google play services and advise on the version number? (8.7.01 is brand new, and is in current slim gapps, and also in opengapps for certain densities).

if it's version 8.7.01, try rolling back to a previous version of slim gapps (you'll need to clean install) and see if that fixes it...
[Android Builders Collective] idkidk:
Hi Ezio,

Is CMTE or layer?

Need to know before flash, now i'm on CMTE...

TIA

idkidk
[Android Builders Collective] ezio84:
Layer.
[Android Builders Collective] adm1jtg:
The new video drivers are definitely rom side. The caf sound drivers appear to be kernel only, looking at the old hydra install file.

Source for hydra nexus 6:

https://github.com/neobuddy89/Shamu/commits/marshmallow

Let me know if you decide to delve into the caf stuff as you got a willing tester. So easy to change kernels that even if its completely unstable probably worth a go, as easily remedied by flashing back to stable kernel.
[Android Builders Collective] Yank555:
Should be the bunch of ALSA commits I guess, but might be more, so I could miss some.

Written on my todo, no idea when I'll get to it, though ;)

JP.
[Android Builders Collective] idkidk:
Hi Ezio,

I'm on your rom... Is awesome!

Personal request, do you think to switch or compile a CMTE version?

Imho CMTE is more reliable then layer..

Bye

Idkidk
[Android Builders Collective] ezio84:
Glad to hear that :D

No plans for the cmte version, i know there are some awesome themes but i want to stick with aosp layers, less code to handle ;)
[Android Builders Collective] ezio84:
The next Purenexus mod will have Slim navbar and Slim dim :D

Commits already pushed to the mm branch if you want to try (but everything seems working well, tested a while ago).

Thanks [MENTION=2033478]Yank555[/MENTION] for the squashed commits (i squashed them more lol) :good:
[Android Builders Collective] h4gH:
Had couple of problems with some layers (bootloop) when trying on your latest build. Is there any way how to find out if the layer is fully compatible with PureNexus? Or maybe some list of compatible layers?

Other then that, one best of a ROM! :) coming back to your builds after some time with Chroma and really glad that I did the switch again.
[Android Builders Collective] idkidk:
Sounds good!

Now in PN app -> Navigation bar -> Buttons and Layout, there isn't the option to link an app (like navbar in your image), is possible to add it?
[Android Builders Collective] ezio84:
It's hard to have a compatibility list for layers, because when something changes in the rom the theme dev could need to update it.

Here you can find all updated layers and ask for support about them: https://plus.google.com/communities/102261717366580091389

With Slim navbar, yes ;)

It's way more customizable than CM one.
[Android Builders Collective] coolek33:
Go ezio! Only slimpie left :p
[Android Builders Collective] t0mas_:
[MENTION=2095315]ezio84[/MENTION]

would you consider adding a few features? I really miss increasing volume ring tone and flip to mute speaker in many roms I try. another thing I often miss is slim actions. all of them are in yanks a osp, should. make them a little easier to fork. thank you, it is a very nice rom allready

---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------

I haven't had the time yet to reflash to mm since I don't use it as daily yet. but I suppose it is not gapps, because I flashed the same zip on two other roms and it worked fine...
[Android Builders Collective] ezio84:
Slim actions are back due to slim navbar, other two features are in the todo list, i love the flip to mute one :D
[Android Builders Collective] ezio84:
You've reminded me another nice thing we had on old Slim builds, the Chamber of Secrets and SlimActions as shortcuts for the home launcher.

Maybe it's not so hard to port them back on M :)
[Android Builders Collective] ezio84:
Chamber of Secrets and SlimActions to shortcuts, back and working :D

(if someone doesn't remember what chamber can do: https://youtu.be/RrpWTIQA708 )
[Android Builders Collective] csolanol:
Nice ezio ???

Lazy to build on Friday evening... Gonna upload it?.

[emoji12]
[Android Builders Collective] dankoman:
should be a fairly straightforward cherrypick from my lp5.1 commits:

https://review.slimroms.org/#/q/topic:chamber

---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------

ah, ninja'd :mad:
[Android Builders Collective] ezio84:
Maybe, my connection is a crap today (well, it's always a sh#it, but today more than usual :D).

I had to remove some actions like the torch (we don't have the ITorchService anymore, but we could use the FlashlightController like in the flashlight tile - Click -), but everything works well :D

PS: added [MENTION=2033478]Yank555[/MENTION] navbar SmartPulldown action to shortcuts too, very nice idea dude!
[Android Builders Collective] ezio84:
PureNexus mod 6.0.1-20160226 :D

Download for Hammerhead: https://www.androidfilehost.com/?w=files&flid=50100

Changelog:

PureNexus source sync @ today

Switch from CM navbar to full Slim NavBar customization + Slim Dim *settings under PureNexusSettings - Navigation bar*

Slim Chamber of Secrets (https://youtu.be/RrpWTIQA708) *enable it under developer settings, see the linked youtube video*

Slim Actions to shortcuts (e.g. you can add them from the Nova widget panel or as Nova gestures, or from any app -navbar too- that can run a custom app shortcut)

Add Haptic Feedback to QS tiles *settings under PureNexusSettings - Notification drawer*

Add increasing ring feature *settings under Settings - Audio and Notifications*

Flip the phone to Mute/Reject Call *settings under Dialer - Calls*

Additional translations

NB: due to navbar changes in this build, if you do a dirty flash (it's fine) set again the navbar height if it's smaller than normal.

Installation, tips, info: check the 6th post of this thread: http://xdaforums.com/showpost.php?p=55121776&postcount=6

PS: if you have problems, call A-team or clean flash.
[Android Builders Collective] Yank555:
Been playing with a fun thought tonight ... works, but different to implement than I thought ... again nice learning sth new ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.96
[Android Builders Collective] adm1jtg:
Pure nexus has these options but they were removed as they cause conflicts I am not sure with what but they were removed and have not returned in many builds since. Something about conflicting with dark mode on some apps I think

---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------

Pure nexus had these options but they were removed as they cause conflicts I am not sure with what but they were removed and have not returned in many builds since. Something about conflicting with dark mode on some apps I think. As remember I asked you about that and also coloring the wifi and data icons and the other status bar ones as well. I think those mods all cause issues. Great learning experience though.
[Android Builders Collective] Yank555:
Color is not new, has worked just fine for weeks ;) If you want to control tint of the icons, clock will certainly not accept getting tinted, but that's wanted.

What I've added tonight is seconds in clock :D

JP.
[Android Builders Collective] adm1jtg:
What I am really after and yes i know its pie in the sky is to have the rom function like this module but WITHOUT needing xposed:

https://play.google.com/store/apps/details?id=com.bocharov.xposed.fsbi&hl=en
[Android Builders Collective] brordavid:
The real question is why I still own a nexus 4? Stupid me. :silly:

One day... :laugh: :good:
[Android Builders Collective] Yank555:
You mean signal icons on the left ? Doable, but ... ;)

The rest would be a layer I suppose.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.94
[Android Builders Collective] ezio84:
Mako is still an awesome device, i don't find any important difference on hammerhead. I switched to the latter only because i broke the display ;)
[Android Builders Collective] brordavid:
I know it's an awesome device, the problem is that you don't own it anymore. ;)

It's really not a big problem, pn is a great rom, but I've guess you've heard about those flashoholics... :D
[Android Builders Collective] Mikulec:
The seconds in clock has to have some impact on battery, no?
[Android Builders Collective] t0mas_:
[MENTION=2095315]ezio84[/MENTION] wow thanks, that was fast :)
[Android Builders Collective] Yank555:
Not worth mentioning, it's a redraw of the statusbar every second. Enable the 'show redraws' in dev settings to check how it is for your setup now, it's redrwan often anyway, like if you use network traffic etc.

It's just updating a string once a second.

JP.
[Android Builders Collective] limjh16:
I built slimsaber for bacon which is officially supported and I get this error. http://hastebin.com/ebucovumat.pl

This error also occurs for slimLP when I try to use uber. Note that I did not have any local manifest for bacon I just let it auto sync when I typed lunch bacon.

Is it the problem with my compiler? Now I'm going to try compiling slim again w/o uber (which suceeded before) and see if error pops out.
[Android Builders Collective] liquidreign:
Back on Yank555.lu shamu build from pure nexus. I love his roms. My Bluetooth stopped working with Google now so I switched over here and what do you know it started working again. I was wondering if someone can help. I tried to get charging sounds to work but I get no sound when connecting or disconnecting. Another thing I noticed is that my charging light stays one color through the whole charging cycle instead of changing with different levels. I went into settings and made sure all the colors were right but still no luck.