yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Yank555:
Ok, then let me explain something very basic because I have read so much rubbish about powersuspend, that I've stopped caring to correct whatever b*ullsh*t was being posted (sorry for the language, but when someone doesn't know what he's talking about, best is to at least say "I think" or even better just not post at all).

Ok, so what is powersuspend ?

It is an in-kernel framework which replaced "earlysuspend" that was present in old Linux kernels and got deprecated (as in abandoned) somewhere between Linux 3.0.y and 3.4.y in mainline Linux.

Now what does it do ?

All by itself, absolutely nothing at all ! So kernels which just have it in without anything else using it, are just wasting space and CPU time (theoretically, in fact, it's not a problem, but it's totally useless).

Ok, so now what is that thing actually good for, then, if it does plain nothing ?

As I said above, it's a framework, and it does what earlysuspend used to do. In-kernel mods can register to powersuspend (same interface as earlysuspend), so that those mods will be informed by powersuspend whenever the screen state changes (screen on -> off, or off -> on), so that each of those mods don't need to hook to god knows what by themselves, and instead simply register to powersuspend (as they used to register to earlysuspend) and wait to get informed, exactly like earlysuspend did before.

So ...

Mods that use powersuspend are :

- dynamic fsync

- intelliplug

- cpu hardlimit driver

- touchboost

- you tell me...

Since this framework has been ported on multiple devices (like Note 3, HH, Shamu are 3 I know as I use myself, but it's available on more), adding powersuspend only makes sense if any of such mods using it are also present in the kernel.

To sum this up, what does powersuspend do

It makes in-kernel mods needing to know when the screen is turned on and off to actually work, so all actually depends on what is in the kernel using powersuspend.

JP.

PS: Sorry for the kind of rant, but this has been boiling in me for a bit already, and I'm very happy you asked, as this had to come out ;)
[Nexus 6  Original Android Development] _Garry_:
Thx. This helped a lot

And what about the different modes? I keep reading to use Autosleep, LCD or Userspace...but no one writes what does what and how...special Hybrid is a mystery for me.

Added:

Or do you know a site where I can read about the different modes?

Sent from my Nexus 6 running latest SlimRom
[Nexus 6  Original Android Development] Yank555:
The modes are just "hooks", that's where powersuspend gets the information if the display is active or not within the original kernel drivers. Not all hooks are available on all devices, if you have hybrid in the list, that's the best, as it will just use whatever notifies first (excluding userspace, which needs fauxclock to tell the kernel, but that's a last resort if nothing else would work).

You asked the right guy, I'm "Mr. Hook" in powersuspend, that's the part I coded, I don't think anyone made any documentation on the parts I coded ;) But it's pretty much explained in my commit comments.

Initially faux used fauxclock only, which is the userspace mode. I added the autosleep hook first, then the display hook later, and eventually combined both and called it "hybrib".

JP.

Edit : Have a read of the commit comments you can find here, should help a bit :

https://github.com/yank555-lu/N3-KK...ts/kk44_NG1_n9005/kernel/power/powersuspend.c
[Nexus 6  Original Android Development] Pete_79:
Hey guys,

Just wanted to say hi :)

Got my Nexus 6 today, long time user of Nexus and Slim.

Quick question, i did look at Slimrom.net but i coulndet find gapps for 5.1.1

Anyone kind enough to supply a link? :)

Thanks
[Nexus 6  Original Android Development] _Garry_:
Welcome on board. :D

[MENTION=265093]yank[/MENTION]:

I wanted to try hybrid for overnight. But it doesn't want to stick. It always revert back to display. I use fauxclock app.

Sent from my Nexus 6 running latest SlimRom
[Nexus 6  Original Android Development] Yank555:
That's normal for shamu, Autosleep doesn't work on shamu, hence with lcd only, hybrid makes no sense, only possible options are userspace and lcd.

Also, for overnight, it wouldn't make any difference, screen is off and stays off, hence powersuspend would have done its deed when you start the overnight in any way, the difference would have been aboht 0.1 second sooner trigger of powersuspend registered mods.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] Yank555:
ROM Update

Tiny update, with 2 changes, SlimRecents has been updated to current latest patchset (still tiny issues to be fixed, griffin is on it) and I've updated my kernel to M-preview sources.

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

JP.

PS: Shamu is up, Hammerhead, Flounder and Flo will follow, all is compiled (new kenrel is shamu only !).
[Nexus 6  Original Android Development] TonyTurboII:
So far on Elemental X everything is super smooth. No hangups with the camera, or complete freezes requiring reboot.
[Nexus 6  Original Android Development] Yank555:
If you had these issues before, I bet they'll show up again, NOTHING changed at all, I just updated SlimRecents and my kernel, and since you use a different kernel, that means all that has changed are a few lines of code in SlimRecents, no link to camera at all...

This camera thing is bugging me, as I can't seem to reproduce it :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] TonyTurboII:
So far I dont think it is placebo, but I will definitely keep you posted on if it creeps back in.
[Nexus 6  Original Android Development] Yank555:
Incoming ROM Update

SlimRecents is fully functional, gmillz sorted out the last tiny issues ;)

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

JP.

PS: ROM is uploading.
[Nexus 6  Original Android Development] PerfectSlayer:
I had slow down issue with camera even before the Slim Recent feature!

I have the feeling it more often happens when I take picture from Lock Screen.. Maybe because it doesn't fully wake? Or the location retrieving fails?

I mean, I could preview the camera but everything stops to respond as soon as I take a picture… (but the picture ends to be store after 10mins!)

I hope it could help you to reproduce the bug :highfive:
[Nexus 6  Original Android Development] Yank555:
That's what I meant, I didn't believe it would be solved, since only SlimRecent was changed, and there is no link between that and camera ;)

I use several camera apps, mostly Google Camera and Manual Camera.

JP.
[Nexus 6  Original Android Development] PerfectSlayer:
For info, I use Google Camera ;)
[Nexus 6  Original Android Development] Yank555:
ROM Update

I've added kagwind's NavBar cursor keys.

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

JP.

PS: ROM is up on AFH, still uploading on d-h.
[Nexus 6  Original Android Development] rignfool:
I just can't keep up anymore ?
[Nexus 6  Original Android Development] Yank555:
I'm almost afraid to say so ... but ... :D

ROM Update

Global menu (power menu) added and settings and cursor icons use vectorised icons.

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

JP.

PS: ROM is uploading.

Edit :

[MENTION=2872010]danarama[/MENTION] : With the vectorised icons merged now, the settings icon theme needs a little adjustment :

ic_settings_display_am --> ic_settings_display

and nfc tap to pay icon also changed.
[Nexus 6  Original Android Development] razrlover:
Not complaining one bit, such a active Dev, squashing bugs daily!!!
[Nexus 6  Original Android Development] DroidIt!:
Lol! Really? Now I can't even flash that much...today...tomorrow though...[emoji16]
[Nexus 6  Original Android Development] razrlover:
I'm silly like that;------+
[Nexus 6  Original Android Development] danarama:
Can they not just keep the same name :/
[Nexus 6  Original Android Development] Yank555:
That's for [MENTION=1277872]dankoman[/MENTION] to answer, I just used the commit (which is merged by now as well). All icons got verctorized, so the xml isn't pointing to the _am png anymore for both cases (what the _am stands for I don't know).

--> https://review.slimroms.eu/#/c/4815/

JP.
[Nexus 6  Original Android Development] danarama:
This is what annoys me about layers. We end up with multiple copies of the same icons all with different names. The png can overwrite the xml as long as it has same name. We need consistency across all roms. At one time, I had 4 identical icons all with different names. It's annoying and hard to keep on top of.
[Nexus 6  Original Android Development] Yank555:
I understand the problem... and I totally feel you on keeping up with variants, as a kernel dev it was hell keeping my ramfs working for all the various ROMs :(

The thing is, the xml name lacks the _am but points to a png with _am :(

This comes straight from AOSP sources :

https://android.googlesource.com/pl...5.1.1_r4/res/drawable/ic_settings_display.xml

Look at line 21 vs. the xml filename.

The problem is, when the icon gets vectorized, the path is within the xml, and there's no pointing to a png anymore...

https://review.slimroms.eu/#/c/4815/3/res/drawable/ic_settings_display.xml

Look at line 25+ in the 3rd patchset (file on the right).

Wouldn't it be possible to also overlay the xml making it point to the png icon name in the theme ?

--> I'm a total noob on layers, no clue if what I suggest even makes any sense "layerly" speaking ;)

JP.
[Nexus 6  Original Android Development] danarama:
png will overwrite either a png or xml as long as it is the same name.

So if ROM has ic_settings_display_am.png, Layer with ic_settings_display_am.png will overwrite. Similarly if ROM has ic_settings_display_am.xml, Layer with ic_settings_display_am.png will overwrite.

So what I will have to do with all my themes, is recompile with a second brightness icon without the _am part. Which is a pain.

android:src="@drawable/ic_settings_display_am" can be png or xml, it doesn't matter. It will find whichever is present.

For some reason slim has renamed this to not have _am, which makes all existing themes (not just mine) incompatible and all themers will all need to recompile their themes with a duplicate image with the new name, just to support slim. We're talking possibly 100 themes need to be recompiled

Edit - OK, it's not slim's fault - I'm wrong about that. It is AOSP issue, but still, all layers themes will need to include both ic_settings_display AND ic_settings_display_am
[Nexus 6  Original Android Development] Yank555:
Not Slim, AOSP (check the links I posted).

What Slim did is stop pointing to a PNG from within the xml and instead remove the pngs for all resolutions, and use a vectorised icon (defined within the xml).

AOSP just uses a diffrerent png and xml name ... that's the root cause of the issue as I see it :

AOSP sources on google's git server :

android / platform/packages/apps/Settings / android-5.1.1_r4 / . / res / drawable / ic_settings_display.xml

<?xml version="1.0" encoding="utf-8"?>
<!--
/*
* Copyright 2014, The Android Open Source Project
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-->
<[COLOR="Red"][B]bitmap[/B][/COLOR] xmlns:android="http://schemas.android.com/apk/res/android"
android:src="[COLOR="Red"]@drawable/ic_settings_display[B]_am[/B][/COLOR]"
android:autoMirrored="true"
/>

So this is in fact the same on any ROM.

Slim just vectorised the icons so the are freely scalabe without quality loss :

same files in SlimLP

<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (c) 2015 SlimRoms

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

[url]http://www.apache.org/licenses/LICENSE-2.0[/url]

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<[COLOR="Red"][B]vector[/B][/COLOR] xmlns:android="http://schemas.android.com/apk/res/android"
android:autoMirrored="true"
android:width="24dp"
android:height="24dp"
android:viewportWidth="24"
android:viewportHeight="24">

<group>
<path
android:pathData="M0 0h24v24H0z" />
<path
android:fillColor="#009587"
android:pathData="M20 15.31L23.31 12 20 8.69V4h-4.69L12 .69 8.69 4H4v4.69L.69 12 4
15.31V20h4.69L12 23.31 15.31 20H20v-4.69zM12 18V6c3.31 0 6 2.69 6 6s-2.69 6-6 6z" />
</group>
</vector>

So the sources point to the xml without _am, which in stock redirects to the png with _am.

It's messy, that's the least I can say, I totally agree.

My idea, couldn't stock AOSP "ic_settings_display.xml" just be included in the theme ? Then it would work either way.

if that "overlaid" the xml, as in adding to your layer apk the "drawable" folder to res with the stock AOSP display and nfc xml files in it.

JP.
[Nexus 6  Original Android Development] danarama:
I don't know. Maybe. Will have to test.

Eitehr way, still requires themes being recompiled
[Nexus 6  Original Android Development] Yank555:
That is certain and unfortunate :(

But it may be good practice to always include what's called from the sources in the theme files, to ensure themes are most compatible by including the "full path" to the actual "image" ?

I do see the added value of vectorized icons vs. bitmaps on the other hand ...

JP.
[Nexus 6  Original Android Development] danarama:
It has some disadvantages too. I know you can convert simple images (difficultly) into xml but not sure if more complex icons can be converted.

Again, something on my todo list, but I have a promotion at work so not much time to test.
[Nexus 6  Original Android Development] dankoman:
[MENTION=2033478]Yank555[/MENTION] [MENTION=2872010]danarama[/MENTION] :

the problem was the original drawables for these two icons redirected to a bitmap from xml with android:automirrored attribute set to "true" so that the icons would get properly automirrored (which is what _am indicates) in RTL language modes. well you can't redirect a bitmap to a vector, but VectorDrawable already supports the android:automirrored attribute natively, so a redirect is unnecessary. i've added that attribute to the vectors themselves to reflect this automirroring behavior.

so although the _am appendix for the icon is deemed unnecessary because of the now built-in attribute, i've redirected the drawables to their old names and renamed the vectors accordingly, so in theming now you'll be able to overlay either resource (with or without _am) and achieve the same result.

this commit fixes the issue: https://review.slimroms.eu/#/c/4855/

i agree with you guys - consistency for theming across roms is of high importance. sorry for the temporary inconvenience, it's fixed now :D
[Nexus 6  Original Android Development] danarama:
Thanks Dan, no worries. Sorry for going on about it.
[Nexus 6  Original Android Development] Yank555:
That of course is the most elegant solution :cowboy:

Thanx for chiming in ! ;)

JP.
[Nexus 6  Original Android Development] spevil07:
[MENTION=2033478]Yank555[/MENTION] Your Rom runs great but I have [MENTION=1269607]Hellsdog[/MENTION] Kernel at work.

I know your kernel is great also! ;)

Gesendet von meinem Nexus 6
[Nexus 6  Original Android Development] danarama:
Might be time to update my rom on my new N6. We'll see. It took 3 bloody hours to write the data back to it :(
[Nexus 6  Original Android Development] warfenix:
What happened?
[Nexus 6  Original Android Development] danarama:
Speaker volume used to inexplicably drop when playing games if over 75%
[Nexus 6  Original Android Development] mjohnson4580:
Can someone tell me what the latest version of slim launcher is?
[Nexus 6  Original Android Development] warfenix:
Ahhh mine did that to. But why did you have to restore data for 3 hours.
[Nexus 6  Original Android Development] danarama:
Read / write speeds? Took 30 minutes to copy to computer then 3 hours to write back
[Nexus 6  Original Android Development] razrlover:
Just saying thank you for latest build. I'm on Tmobile and volte confirmed working.

Appreciate hard work.
[Nexus 6  Original Android Development] Yank555:
Wonder what fixed it ??

Which build was the first to work ?

JP.

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

---------- Post added at 08:09 PM ---------- Previous post was at 08:03 PM ----------

With [MENTION=1277872]dankoman[/MENTION] 's commit your theme now works just perfectly fine :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0a kernel.
[Nexus 6  Original Android Development] _Garry_:
Now i'm done preparing my setup files, and i read that a new update will come soon....gosh...guess i wait for next yanks rom XD
[Nexus 6  Original Android Development] Yank555:
ROM Update

SlimRecents panel size can be set between 60% and 160% in steps of 5% via seekbar (see screenshots). Patchset uploaded to gerrit.

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

JP.

PS: build is up on both servers.
[Nexus 6  Original Android Development] x111:
wow, finally slimrecent with almost true 100% size,

Is it possible to do 100% size that recents will fits all screen ?

and BT connection interruptions is still there.

thanks.

...

the best feature of slim recents is "only show running apps", nite I don't need to even clean recents.

thanks for that, it's so important on daily basis.
[Nexus 6  Original Android Development] danarama:
No because that defeats the point of it not stealing app focus, ruining multi tasking
[Nexus 6  Original Android Development] Yank555:
As danarama said, that's against the point of SlimRecents, it's about being a slide-ouot panel so you don't lose focus of the app you're running.

As for BT, I'm afraid, there won't be much we can do about this, you seem to be the only one reporting such issues, sounds like an incompatibility between your N6 and the device you're trying to connect to :(

JP.

---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------

Just a headsup for next update, it will require a clean flash :(

Unfortunately this is necessary since switching from CM's navbar to Slim's the DB Helper version is now lower (115, 117 for CM's stuff) and downgrading is not possible, is will result in a bootloop.

I've kept a hack in my builds to make dirty flashing go on working, but at some point I would like to get back to Slim stock DB version, and I've decided now will be that moment.

So you know, backup stuff, make screenshots of system settings etc.

JP.
[Nexus 6  Original Android Development] Smallsmx3:
Has it been fixed so the latest radio can be used on Volte?
[Nexus 6  Original Android Development] Yank555:
Can't comment personally, as I don't have that option where I live, but it has been reported to work :

http://xdaforums.com/showpost.php?p=61294468&postcount=2921

JP.
[Nexus 6  Original Android Development] Smallsmx3:
Well I know it was working on the 95r radio, but not on the 14r

---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------

What radio are you on?
[Nexus 6  Original Android Development] franatic08:
Could anybody be so kind to pull and share the slimlauncher.apk?

Thanks in advance!
[Nexus 6  Original Android Development] razrlover:
That's correct. I was on 95r radio when I tested 6/10 build. Havent tested 6/11 or later yet.
[Nexus 6  Original Android Development] Yank555:
I have 95r, which radio is 14r ?

These are the ones I've download so far :

LMY47I : radio-shamu-d4.0-9625-02.95.img

M preview : radio-shamu-D4.01-9625-05.16+FSG-9625-02.94.img

JP.
[Nexus 6  Original Android Development] Smallsmx3:
14r is the newest, from the tmo 28E Rom
[Nexus 6  Original Android Development] Yank555:
Not using that one on my end, I have a non branded device, rather stick with non branded baseband ;)

JP.
[Nexus 6  Original Android Development] Smallsmx3:
M preview would be nice to get Volte working since it fixed an issue or two and I get great reception
[Nexus 6  Original Android Development] Yank555:
Only thing I can offer of M-preview is the kernel, if you stay on the one coming with the ROM, it's fully M-preview source based.

Not certain that would make a difference, though... this VoLTE thing eludes to me ;)

JP.
[Nexus 6  Original Android Development] Smallsmx3:
[MENTION=1978554]zephiK[/MENTION] has it working on chroma, I think it's a binary issue, being on the newest ones from 28E
[Nexus 6  Original Android Development] Yank555:
It's based on the Muppets repo (or just a fork of it), don't know if that would compile properly with Slim...

If I manage to find the time, I'll give it a try, if it compiles, I'll let you know.

JP.
[Nexus 6  Original Android Development] x111:
Sorry that I'm again with my BT issue but I flashed "[ROM] [5.1.1] Stock rooted LMY47Z"

http://xdaforums.com/nexus-6/development/rom-stock-rooted-lmy47z-init-d-busybox-t3120295

and everything works, no issues.

Than I made FULL Wipe and flashed "Slim-shamu-5.1.1.alpha.0.3-UNOFFICIAL-20150611-2332" (didn't install any app except google music)

and again got BT interruptions.

Damn it, now I should sit with Stock :(
[Nexus 6  Original Android Development] _Garry_:
So....when will this update be released?
[Nexus 6  Original Android Development] warfenix:
Whenever he posts it...... Wondering why people still ask for ETA's
[Nexus 6  Original Android Development] _Garry_:
naaaa....i dont ask for etas. in the old times i might have done it.

BUT....

in yanks case i like to ask for it because his releases are damn fast. And befor i need to flash after a flash which is ~30mins old i prefer to ask. ^^

when yanks ask to stop asking, i will respect it and wait ^^
[Nexus 6  Original Android Development] razrlover:
True lately yank has been on a mission. And BTW happy bday Yank555!!
[Nexus 6  Original Android Development] Yank555:
Well in fact it's up, just not posted yet, been busy setting up my device (first clean falsh since 5.0 :D)...

But wait another 1/2 h I'm cooking another one, I now understand the battery charging light issue I didn't have myself and why fiddling with ny script didn't help ;)

There was sth missing to enable the battery light switch and that was there some time in 5.0.x where I switched it off. And since I only dirty flashed, I didn't have the issue since it was set to off, as it looks only the 'switch' is missing... well hopefully not for very long anymore ;)

You can use the current latest, though, if you want to start setting up your device, from here on dirty flashes it will be again ;)

JP.

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

EDIT :

I give you ... BATTERY LIGHT CONTROL for your shamu ;)

Uploading in a minute.
[Nexus 6  Original Android Development] _Garry_:
Do we still need to edit your script for it? Or should we kill this line?

Sent from my Nexus 6 running latest SlimRom