yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Almayce:
Hey guys, im using the latest [MENTION=2888538]letmedanz[/MENTION] build with beta gapps and im facing one slight problem. My navbar is not translucent when I'm on the home screen. I think it happened when I let greenify to be my device administrator for locking the screen & hibernating. I can't reproduce it though as the bar just stays black all the time even after several reboots and unnistall of greenify. It was clean flash by the way. I will try reflashing, maybe that'll help. Everything else is smooth as babys bottom :) the default font is really good!

Edit:reflash didn't help, still black.

Edit2:I'm on mako if it matters.

Last edit: I observed that if I change the dpi of navbar it changes when in settings, but when I go to home screen there is a 36 dpi I set first, the buttons are either smaller or bigger than the navbar, depending on the dpi I set. I attached a screenshot, don't mind the wall, that's my gf :)
[Android Builders Collective] ralpheboyo:
Try to add wallpaper like this...
[Android Builders Collective] Yank555:
You mean to avoid the extra battery drain ? Other than a slight battery drain increase, it does seem to work fine with just swapping the lib.

Dunno yet, as I don't use my N5 as daily, I could leave it in ... but should be easy to make a flashable zip for whoever wants this lib ...

No definate decision so far ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.8 kernel.
[Android Builders Collective] kagwind:
According to this, myfluxi seems to seek for another approach.
[Android Builders Collective] Arijit.Ray81:
[MENTION=2033478]Yank555[/MENTION] - Love your Hammerhead builds. Looking forward to updates and hopefully 5.1 :p
[Android Builders Collective] hooliganx:
[MENTION=2033478]Yank555[/MENTION]

with this libs in Rom, if user don't want use this option, just turn off in settings don't deactivate this battery consumption?

if yes, who likes this function, will use knowing about battery life consumption, like dt2w option.

and... your banner not showing in OP [emoji16]

thanks man[emoji106]

n5slimpop.reS28raM.1.0cartgapps.15.03.10

elementalx.2.10rd2.25v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Android Builders Collective] Yank555:
Going 5.1 solo might be above my "ROM" paygrade atm ;)

JP.

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

---------- Post added at 02:05 PM ---------- Previous post was at 02:00 PM ----------

Would need to test, but I expect the drain to be there always, since the bew sensor lib likely keeps sensors awake all the time, the switch in settings will pay attention to the sensors or ignore them ...

I will test tomorrow on my N5 with ambient display disabled to check ... so we'll know for sure.

But having the lib as a flashable ZIP seems like a good solution for everyone.

JP.

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

Edit : Banner fixed, damn Tapatalk, worked fine in browser ;)
[Android Builders Collective] DroidIt!:
I did a little experimentation myself a bit back with my N6 and ambient with ElementalX. Now I believe flar did look into ambient pretty heavily and I agree: I saw no battery drop with "standard" ambient. I ran my phone with ambient off for about 2 months and then with it on for about a month and I really can't tell any difference with my N6. So for me, I think weather the sensors are enabled in the kernel or not, I'll keep ambient on on my N6 because even with it always activated I still get far better battery life on my N6 than my wife does with her N5 with ambient off. Now with the N5, I noticed when I tried ambient that when the phone was powered off, I could visibly see the screen still very faintly lit so I immediately turned ambient off and decided not to test at all. That was what I figured from my whole study of it :)

---------- Post added at 07:47 AM ---------- Previous post was at 07:32 AM ----------

...oh and in the name of science :) : [MENTION=5131448]reS28raM[/MENTION] your n5 build works great. [MENTION=2033478]Yank555[/MENTION] your n5 build is also without issues. [MENTION=2888538]letmedanz[/MENTION] your n5 build is prefecto as far as I can see. [MENTION=2033478]Yank555[/MENTION] your n6 build runs really nicely as does yours [MENTION=2888538]letmedanz[/MENTION]. [MENTION=2033478]Yank555[/MENTION] your N7 build runs great as does yours [MENTION=2888538]letmedanz[/MENTION]....I think that was all of them and good builds all :)
[Android Builders Collective] Arijit.Ray81:
That's cool - I was just teasing you.
[Android Builders Collective] theesotericone:
"Hello. My name is DroidIt!. I am an addict."

:laugh:
[Android Builders Collective] DroidIt!:
I prefer "enthusiastic" ;)
[Android Builders Collective] DroidIt!:
Oh, don't know if anybody else caught this , but google decided to spin off their Android System Webview and publish it to the play store and can be downloaded from here https://play.google.com/store/apps/details?id=com.google.android.webview It has to be entered exactly into the search box or hit that link. It doesn't show up yet under Google's published apps ;)
[Android Builders Collective] Yank555:
Well my stand is whether ambient display is on or off, the sensor lib 'might' keep the sensor awake anyway, hence no battery difference whether ambient display is set to enabled in settings or not. Of course if that was true, keeping ambient display off would make very little sence.

Now if the lib could be switched with a lib which never keeps the sensor active, that would break ambient display of course, but what impact would that have on battery ?

I agree battery oh N6 is pretty fine, but what if it could be (noticably) better ? ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.8 kernel.
[Android Builders Collective] dankoman:
pick up gesture sensor is a low power sensor, considered a "one-shot" sensor (detects an event and sends it through the HAL after deactivating itself - so it is not continuously on). not having the sensor present will not give you a noticeable increase in battery life.

even so, removing the sensor wouldn't break ambient display - it is coded to function regardless of whether or not sensors are present. it uses notifications as an ambient display trigger also. however, if you remove the sensors system-wide like you're suggesting, you'll probably break other things that also use them (or which may use them in the future).

anyway, you can control these triggers with my doze options :D
[Android Builders Collective] hooliganx:
[MENTION=2033478]Yank555[/MENTION]

do you have a flasheable zip for those libs?

can I take off in case doesn't work well?

in [MENTION=5131448]reS28raM[/MENTION] build can't make pickup gesture work even with elementalx.

ps: in your OP says navring options, but don't find it in your build. [emoji15]

turn back to reS28raM because Im at work and don't have much time to test everything.

[MENTION=1277872]dankoman[/MENTION]

every option in doze option works good. only pickup unselect all the time here.

[emoji15]

n5slimpop.reS28raM.1.0dxposedgapps.15.03.11

elementalx.2.10rd2.25v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Android Builders Collective] Yank555:
Hehe, when I said break I meant the pick up part of it, obviously ;)

I didn't suggest to remove them completely, instead of keeing some awake to just let them go to sleep on suspend as is the case on other devices for instance, and wake them up on resume. And does the lib really allow everything to go to sleep if ambient display is not enabled / motion detection is not enabled in settings, or just stops pushing the info from the sensor through ?

The question is, since that lib is a blob, so closed source, what stays awake due to it is a question. If I can find the time I'll have a look at what the kernel actually puts to sleep and keeps awake.

Since day 1 I've wondered how the n9005 could have a better 'sleep' batterywise on SlimKat (at the time) than a Nexus on stock...

But I for sure may very well be chasing ghosts here :D

JP.

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

---------- Post added at 11:09 PM ---------- Previous post was at 11:06 PM ----------

Haven't made the zip yet, undo would be simply dirty reflashing the ROM.

I'll post a link to it here and in my OP when I've made it.

The good news is, short test on N5 would show no drain when ambient display is totally disabled, first test overnight, next I'll have ambient display enabled but on notification trigger active.

JP.

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

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

Sticks fine on my end on the N5.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.8 kernel.
[Android Builders Collective] aow1980:
[MENTION=5131448]reS28raM[/MENTION] I did a build with just your framework and Settings commits and still FC on System UI due to profiles. So think I'm missing

a commit from another source and just haven't been able to locate it yet.
[Android Builders Collective] reS28raM:
I think i'll not be able to fix it now, i lost my mom yesterday as a direct consequence of that roof issues - i retire from the hobby for a while. I did a rebase, it is possible that profiles commits are now in the wrong order, cannot exclude it 100/%.
[Android Builders Collective] gjnicholson:
Sorry to hear that and please accept my condolences.
[Android Builders Collective] letmedanz:
Extremely sorry for your loss Paolo.

Condolences from all of us - your extended family.

Wish you & your loved ones all the strength you need to tide over this difficult phase.
[Android Builders Collective] aow1980:
Sorry for your loss [emoji20]
[Android Builders Collective] ezio84:
I have no words... Condolences Paolo.

Stay strong during this stage.
[Android Builders Collective] AquilaDroid:
Our prayers are with you, wishing you strength to cope with your loss and hope to see you back here to let us know how you're doing. I've really enjoyed your presence here, not just the great builds, but all the help you've been. Good luck, friend!
[Android Builders Collective] Yank555:
Really sorry for your loss, losing a parent is a very hard experience in life, I've lost my dad less than 2 years ago, my thoughts are with you and your family.
[Android Builders Collective] hooliganx:
really sorry ?

my condolences too.

is very very hard moments like this.

lost my dad almost 5 years ago.

and only after loose him, I understand everything he did for me. [emoji26] [emoji22]

keep strong dude! we are family here!

good thoughts and prayers for you and your family.

[emoji8]

n5slimpop.reS28raM.1.0dxposedgapps.15.03.11

elementalx.2.10rd2.25v4a.2.3.4twrp2.8.3.0

-----------------------------------------------------------
[Android Builders Collective] :
[MENTION=5131448]reS28raM[/MENTION] Oh man that is just.. Don't know what to say :( My condolences to you and your family. Stay strong!
[Android Builders Collective] Garrykd:
So sorry for your loss Paolo.....Say not, in grief, that your mother has gone but always remain thankful that she was yours.
[Android Builders Collective] DroidIt!:
Oh, really truly sorry to hear that. You'll be missed. Wish you and your family all the best in this tough time.
[Android Builders Collective] theesotericone:
[MENTION=5131448]reS28raM[/MENTION]

Words are scarce at times like these. Remember the good times and smile at every thought of her. Stay strong but cry when you need to. Where all here if you want to get anything off your chest. PM me anytime man. Positive vibes sent your way.
[Android Builders Collective] reS28raM:
Thank you all my friends, very much appreciated. :)
[Android Builders Collective] kagwind:
I'm quite new here, but please accept my condolences.

Remind me of my grandpa passing away 3 years ago. It will always hurts, but hope time will assuage the pain.
[Android Builders Collective] ezio84:
Let's think about useless things for a while:

SlimLP 1.0dUBERTC mod for mako & hammerhead

NB: wipe cache and system this time, the build is now made with ubertc toolchain (please report back your impressions).

Download (links on the right):

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

Changelog:

- CM Eleven, AudioFX and Terminal source sync

- Slim source sync

- Switch from stock toolchain to UBERTC toolchain (thanks [MENTION=5497766]aow1980[/MENTION] and [MENTION=2888538]letmedanz[/MENTION] for the recommendations and how-to)

- Visual/performances fixes (thanks CM):

* Systemui: fix glitches with recents view and search widget

* SystemUI: improve qs tile scroll handling

* SystemUI: fix small jump when expanding QS w/o notifications

* QSutils: use package manager to query whether nfc is present

Build additional features (Please read it before asking where to find a setting) - This list also contains links to all commits if you want to cherry-pick them:

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

NB: SuperSU, the Layers app and the Layers backup app are now built-in, you don't need to install them after flashing the rom.
[Android Builders Collective] DroidIt!:
Thanks ezio :) I'll see if I can get my hands on the wife's N5 and try it out. I think she's thinking about an N6. I told her, size DOES matter :)
[Android Builders Collective] ezio84:
About layers: today i had an issue, i tried to install some overlay apks with the Layer app but after the reboot they were not loaded and they had a size of 0Kb.

Reason: the system partition was full. After deleting some system apps i don't need now (with Titanium or a root file manager), i've been able to install my overlays without problems.

So check your system partition size if the device has some strange behaviours like that one.

N5 has probably the best size ;)

PS: Optipop UberTC seems really good!
[Android Builders Collective] Maibol:
my condolence so sorry for your lost
[Android Builders Collective] PerfectSlayer:
Sorry for your loss. Stay strong. Sincerely.
[Android Builders Collective] veedubrocks:
Been around for a couple of years, reading every page and having fun with you guys. [MENTION=2095315]ezio84[/MENTION] my condolences to you and your family. Stay strong.
[Android Builders Collective] donnabelmartie:
My sincerest Condolences dear dev.
[Android Builders Collective] Jax Teller:
My condolences to you and to your family.
[Android Builders Collective] DroidIt!:
Oh hey [MENTION=2033478]Yank555[/MENTION] and [MENTION=2888538]letmedanz[/MENTION]. I forgot to mention something on both your latest builds. On my N6 (honestly can't recall on the N5) but with a clean install, on initial boot up where you first hook up to your WiFi after I connect it says initializing or whatever that next screen is but it never does anything. I always need to hit the back arrow, "forget" my network and then hook back up and then it goes. Sometimes I need to do that a couple of times though. That was the only thing though, everything else was perfect as I said and WiFi worked fine after booting it was just on the setupped screen. :)
[Android Builders Collective] Jax Teller:
I believe you are talking about the "checking connection" page.

It happens with the latest gapps. If you leave it for 2 minutes it will continue.

It's probably something related to the new playservices.

It started happening after play services updated to v.7.
[Android Builders Collective] kagwind:
It does.

You should try Optipop cflags as well.:good:
[Android Builders Collective] DroidIt!:
Ah OK, was not aware of that :) Oh hey [MENTION=2095315]ezio84[/MENTION], since I'm an addict :) I loaded up your latest build on my wife's N5 and gotta say it's running really good so far. I ran through all the settings quick and couldn't even find a problem. :)
[Android Builders Collective] theesotericone:
LOL. I thought we agreed on "enthusiast"? :cool:
[Android Builders Collective] DroidIt!:
I'm also ambitious...I can do both at the same time [emoji14]
[Android Builders Collective] SOLheel:
Sorry for your loss, many condolences
[Android Builders Collective] tomzefi:
My sincere condolences. Truly hope you and your family find the strength to get through this. Much love.
[Android Builders Collective] Arijit.Ray81:
Our sincere condolences. Really sorry to hear the sad news. :crying:
[Android Builders Collective] kagwind:
I created two zips in the attachment.

I think it should work, but did NOT test them.
[Android Builders Collective] Yank555:
Thanx, been too busy these past 2 days ... :good:

BTW, it really looks like the lib could stay in, when pickup is disabled, my N5 seems to sleep better, although maybe not that good as before.

I've done a few screenshots, will upload them tonight when I'm at home and see where we stand, I should have 2 days with old lib and 3 days with the new lib (1 day ambient display totally off, 2 days with ambient display on and pickup disabled), all in one battery run.

JP.
[Android Builders Collective] Konsumhaus:
[MENTION=2095315]ezio84[/MENTION]:

First time for me with your rom. Great work. Thx!

The UberTC compiled verson is really, really fast:good:

Running it with HellsCore hC b9.6, even compiled with UberTC. Great combo

One thing i've notice: there's no option for link/unlink ringtone in "Sound & notification" and no option for ascending ringtone.

Are you thinking about built in these commits?
[Android Builders Collective] kagwind:
I've been trying to figure out the unusual battery usage in the past several days. In opposite to your situation, it is the battery usage in screen-on usage (aka not-sleeping) that is higher than usual. :confused:

I uninstalled some apps and xposed as well, now it seems better. :silly:
[Android Builders Collective] Yank555:
Well my N5 has only a subset of the apps I use (only tapatalk, g+, hangouts, fb, messenger) as I don't use it as my daily phone, well whatever I'd use on it when at home and "browsing" the web (so WiFi is always on, but no mobile, neither voice nor data).

Screen on seems unchanged on my end, though no xposed and running my kernel (that's as usual, so unchanged over time / comparable).

JP.
[Android Builders Collective] kagwind:
I just played with the code too hard, too many variables to rule out. :mad:

Although I guess a clean flash will fix it completely, I don't really have time to setup my phone.:eek: (Caution: this is a bad example!)
[Android Builders Collective] ezio84:
I'm free also this weekend so:

CM Navbar customization for our Slim builds (with the arrow cursors when typing a text):

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

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

ps: the search button in the navbar supports long press tap (normal: text search - long: vocal search)

I'll try to add also the navbar ring targets commits later :)

Thanks dude!

Thanks, also for the suggestion about the ringtones and volume stuff. I found the commits long time ago and forgot them lol. I'll check them next days if possible ;)
[Android Builders Collective] reas0n:
When You are talking about is, what besides kernel, device is blobs needs to be done to port CAF to AOSP ROM? I have a policy problem. Could we PM?
[Android Builders Collective] dankoman:
right, that's what i was saying :D merely having the lib file present in the system does not force the pickup sensor to be used.

besides having the lib present, the sensor needs this boolean to be set to "true" (in your device's config overlay) for the sensor to be on.

(alternatively, using the doze preference for it also enables it because it controls this boolean in code)

long story short, yeah, you're safe to include the lib all the time - it won't affect whether or not the sensor is used.
[Android Builders Collective] ezio84:
And also CM navring targets are in :good::

https://github.com/ezio84/packages_apps_Settings/commit/548cca0c8f3d2223f6aa823f6733d4d4398a6bdf

https://github.com/ezio84/frameworks_base/commit/4897c971bcc7a721b4ba9e35ec237375b0213a98
[Android Builders Collective] skidaway:
I flashed the mako build this morning. It runs great, no problems whatsoever. Thanks for compiling for us lowly mako users, we appreciate it!
[Android Builders Collective] DroidIt!:
Hey [MENTION=2033478]Yank555[/MENTION] Well, I know you put quite a bit or work into it, but just keeping it honest here :) http://xdaforums.com/showthread.php?p=59415812

I think your 5 GHz thing might need some tweaking, I've been seeing quite a few comments like that in flar's thread when he implemented your 5 GHz fix. I report the good with the bad so you guys know what works and what doesn't and for most at least your fix seems to be causing some problems. Personally my router still works OK, but I got my only about 4 months ago and it is a top of the line, so maybe that has something to do with it. Well, just thought I'd make you aware, that's what I've been seeing anyways :)
[Android Builders Collective] Yank555:
As a old kernel and young ROM guy, I'm still not convinced :D You see, that tiny pesty dog that just won't let go of the arm and hanging above ground, that'd be me on such matters :angel:

The question is, does it simply ignore the sensor, or does it turn it (or allow it to be turned) physically off... ?

<!-- Doze: should the pickup sensor be used as a pulse signal? -->
<bool name="doze_pulse_on_pick_up">false</bool>

This does still sound like the sensor (as in hardware / kernel) is still kept active and not put to sleep on suspend, just that userspace will ignore the "pulse signal". A difference in draw is still there, even with the pickup disabled, but it's less pronounced.

The problem lies in the fact that what lies between this code and the kernel is a blob of which we do not have sources ...

One thing on the other hand is likely, the decision to keep that sensor awake or not is in that blob (not the kernel), since switching the blobs makes it work, and with the old blob we have less drain (suggesting all is suspended).

Only way to know for sure is looking at the kernel (dmesg) and if necessary adding debugging code to the kernel ;)

But long story short, for now at least, I'll keep the lib in, plus we now have 2 zips for users to flash to and from that lib.

JP.