yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] x111:
Is anybody know, how to add an icon "settings" and "battery" to the status bar when swipe once down ?

I'm so tired to swipe up and down twice.

So, happy that finally all nav bar buttons are completely black, better if it would be absolutely transparent but still cool.

btw, color option has interferences with Xposed Gravitybox, that Recents button is not completely black and I need to use Gravity box action instead.
[Nexus 6  Original Android Development] franatic08:
Enable quick pulldown.

Look for it in appearance>quick settings>qs general
[Nexus 6  Original Android Development] franatic08:
If there's a commit for unlinking ringtone and notification volume, would you please consider adding it?

Thank you.
[Nexus 6  Original Android Development] danarama:
DO you think we'll ever see custom QS? I have a tasker toggle I'd love to add.
[Nexus 6  Original Android Development] stevew84:
Verifying that 5/26 build 1605 is the latest unofficial.
[Nexus 6  Original Android Development] damngood98:
yup :good:
[Nexus 6  Original Android Development] capnkrunch:
Found the fix for Verizon roaming. Actually, poitee did quite a while ago. I should have just googled it from the beginning. Add

ro.telephony.get_imsi_from_sim=true

to your build.prop and reboot. For devs, the CM commit is c62ed18. Big thanks to poitee.
[Nexus 6  Original Android Development] Yank555:
Well if that's not causing ill effects for others, I'll add this and push it to gerrit. I'llmadd it manually and see if I see anything odd on my end today.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] DroidIt!:
Hey yank :) just as a report. I've been using your latest N6 build since you released it and all is running good and stable but I believe me and RootSu are both facing the same issue. We both are getting some minor lags when running your latest build. I'm not TOO sure what his exact issues are, but mine seem to show up mostly just when I'm typing, either a text message or like in Tapatalk. It doesn't happen every time and I haven't seen the lags like when opening apps or when navigating within apps themselves, they only seem to show up when I'm typing and then only sometimes. So kind of a more minor issue for me, but does seem to show up about every other time when I type. I don't know if there's anything more I can do to help. Have you seen this issue at all? Like I said me and RootSu have both noticed it though. Kind of interested to just get your thoughts on it. :)
[Nexus 6  Original Android Development] danarama:
Mine wasn't so much "minor lags" as my CPU was hitting an upper limit of 1267Mhz. I'm not sure if it was because I had 2 kernel apps installed. I removed one. It hasn't happened since, but I am not certain it was that yet.
[Nexus 6  Original Android Development] PerfectSlayer:
Looks the same for me :(
[Nexus 6  Original Android Development] Blaiser47:
Any word on getting volte working on Verizon? Otherwise this ROM has it all! Thanks Yank.
[Nexus 6  Original Android Development] Yank555:
Well, first off, I suppose we are talking about the ROM using my kernel ?

If so, there are a few things you could test, but it involves either the use of fauxclock or changing my kernel init script.

You could raise touchboost freqs (low and high), while high is more interesting when using the keyboard since tapping several times within a given timeframe will go from touchboost low to touchboost high (that's my own touchboost driver, part of my CPU hardlimit driver).

The other thing you can do is lower the intelliplug threshold value, I use 7500 which is VERY high and makes cores mostly stay offline. Using a lower value will allow cores to more easily come up.

ROM-wise there's not much that has changed, especially nothing I can see which would cause such behaviour, I mostly replaced stuff I added in the meantime (like navbar) by stock Slim stuff which had been ported and merged in the meantime.

So featurewise the ROM has been stable, if you want.

If you don't use my kernel, this will be a hard one... and such microlags pretty much will rather come from the kernel than from the ROM.

Personally I can't say I saw that kind of behaviour, and I've been using the device longer than usual, due to lack of time for making any new builds or whatever ;)

BTW, been syncing my repos, and the rebase is done, I'll be adding a few things (including SlimRecents) and hopefully if all goes as expected, there could be a new build sometime today (well it's 7pm already, so maybe not for all 4 devices I support).

[MENTION=2872010]danarama[/MENTION] : CPU max. locked that low is very odd... thermal throttling maybe ? But using more apps (if they do more than just read) could indeed be an issue. But again, if you run my kernel, apps can't interfere as my CPU hardlimit driver is configured to ignore userspace CPU freq. changes, so apps can only read anyway (except fauxclock which has support for my Hardlimit driver).

Is that the build.prop thing ? If so, it will be in my next build, I've been using it today and I didn't see anything out of the ordinary on my end, so it doesn't seem to cause issues on other providers.

JP.
[Nexus 6  Original Android Development] danarama:
Hey [MENTION=2033478]Yank555[/MENTION] i use elementalx. I don't personally feel my issue is Yank related to be honest.

Also I thought the volte thing was just not having data and voice simultaneously, but that is a binary thing, which I would expect all slim builders are using anyway.
[Nexus 6  Original Android Development] Yank555:
Well, if we can do something about it any way ;)

Just as a test, you could try to see if you have better/worse results running my kernel for a day or so. Might be usefull, if it's a kernel thing, to hint how to avoid it using elementalx.

Well that I have on my end as well, as soon as I have a voice communication, my mobile data is gone, pretty annoying, although I don't often run into that situation, personally.

So that would be an issue in the vendor blobs ? Never looked into this at all, wouldn't actually know where to start off hand tbh ;)

The build.prop thing is for the "R" roaming I think.

JP.
[Nexus 6  Original Android Development] danarama:
Actually I think it's just getting volte for Verizon period. I'm not sure which files are needed. I know [MENTION=1978554]zephiK[/MENTION] pulled them from an update and put them in his github somewhere. [MENTION=1050103]sykopompos[/MENTION] should know too.
[Nexus 6  Original Android Development] Blaiser47:
Correct. Verizon being CDMA I think was a little different than other US carriers. I'll look around too. I know it works in Chroma, AOSIP, and XenonHD, all asop based so someone figured it out. Usually it is just a setting in cellular networks that you have to toggle.

Found this. https://github.com/CyanogenMod/andr...mmit/6bb46676ae4aeafa0ac3fe2ab0a1db9689a2bd8f

May not be helpful but could did the toggle issue on chroma
[Nexus 6  Original Android Development] DroidIt!:
Ohhh, ohhh, ohhh...Nexus 6 please! [emoji56] [emoji16]

---------- Post added at 02:14 PM ---------- Previous post was at 01:18 PM ----------

Oh BTW, the M dev preview radio works really well with your build on tmob :)
[Nexus 6  Original Android Development] DroidIt!:
....and M dev bootloader [emoji16]
[Nexus 6  Original Android Development] Yank555:
New 5.1.1 build available in my OP

Say hello to SlimRecents ! And also to a few other nice additions ;)

Changelog

- Use vectorized drawables for SlimActions / Navbar / Pie (Dankoman)

- Heads up notifications behavior fix (Victor Lapin)

- Use 20dpi steps also for high resolution devices (Yank555.lu)

- Allow unlinking ringer with notification volume (maxwen)

- Hide AlarmClock Icon in StatusBar (Marek Walczak)

- (shamu only) Verizon Roaming fix (Evan McClain)

- SlimRecents (kufi)

- Repo sync'ed​

Download links and full changelog can be found in my OP here on post 14.

devhost & AFH uploading : filename = "Slim-shamu-5.1.1.alpha.0.3-UNOFFICIAL-20150602-2243.zip"

JP.
[Nexus 6  Original Android Development] DroidIt!:
Te he...first! [emoji16]
[Nexus 6  Original Android Development] PerfectSlayer:
Thanks for the answer. Is there another kernel that you officially support?

I would like to try before taking time to tune your kernel ;)
[Nexus 6  Original Android Development] clothednblack:
That launcher is included in the flashing. You can download "simple home switch" from the playstore, it makes life much easier to jump between launchers

---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------

https://copy.com/iDTWEuUgjOH7kwpQ

Your welcome

---------- Post added at 09:43 PM ---------- Previous post was at 09:41 PM ----------

@xXghostXx313 wrong link, it's fixed above now.
[Nexus 6  Original Android Development] xWasabi:
Still does not work. The Google Launcher does not show as an option as a home launcher. I downloaded the google launcher from play store.

Edit: fixed now. Thank you.
[Nexus 6  Original Android Development] clothednblack:
Let me see if this is right,

You flashed latest slim rom from today

You flashed latest gapps (416 I think)

And you don't have Google launcher?

Edit: I see you fixed it, what was it?
[Nexus 6  Original Android Development] xWasabi:
It was strange but what i did after i pushed the google launcher apk to system/app i then installed from that point rather then rebooting. I don't know the difference, but it worked. Lol.
[Nexus 6  Original Android Development] xWasabi:
Apk

Unrelated, but I feel some of the people here would appreciate this. It's a dark themed google messenger apk

https://www.dropbox.com/s/g4jwqb5dponovm5/BlackGoogleMessenger-1.0123-v2.apk?dl=0
[Nexus 6  Original Android Development] xWasabi:
fix

Hdr is an easy fix. All you have to do is download build.prop from play store and type manufacturer in search bar and change moto to motorola all lower case
[Nexus 6  Original Android Development] skiwong20:
root is there , i make build everyday. the root option is under the development section in settings.
[Nexus 6  Original Android Development] clothednblack:
That makes sense because it's a system app by default for Google Apps, glad you figured it out and got it working.

Thanks, I forgot about that.
[Nexus 6  Original Android Development] Biaviian:
I'm hoping somebody can assist. Does this have an option to force the volume buttons to ALWAYS control the media volume? That is my only reason for installing a ROM until Xposed comes to ART.
[Nexus 6  Original Android Development] clothednblack:
This?
[Nexus 6  Original Android Development] Biaviian:
That's it! Thanks!
[Nexus 6  Original Android Development] dankoman:
THANK YOU! that's been driving me crazy!

edit: and this should fix it https://gerrit.slimroms.net/#/c/20136/
[Nexus 6  Original Android Development] bikeryder007:
Awesome. HDR not working was the only issue I was having at all. Its great that it is fixed because it makes a big difference on this camera.
[Nexus 6  Original Android Development] Smallsmx3:
Is this new unofficial 5.0.1?
[Nexus 6  Original Android Development] clothednblack:
Yes, latest is merged with 5.0.1
[Nexus 6  Original Android Development] celyko:
Does the new update fix the sticking GPS icon? Its driving me crazy. Side question: Is there any plans to get the notification led and double tap to wake/sleep working? Just thought I'd mention the amazing battery life I'm getting. 6+ hrs yesterday of sot

Sent from my Slim N6
[Nexus 6  Original Android Development] clothednblack:
Look back a page, I posted a fix for gps icon sticking. Led is in the works but you can use the light flow paid app for now (there is a thread about this) tap to wake works by using a free app (also a thread for this) tap to sleep is built into this rom by double tapping the notification bar (it's in your settings menu under interface/status bar)
[Nexus 6  Original Android Development] celyko:
I did do fix and it worked. I previously read it and forgot it was there. I didnt know about those apps. Love this ROM thanks for all your awesome work!
[Nexus 6  Original Android Development] clothednblack:
Led

http://xdaforums.com/showthread.php?t=2947625

Notification LED confirmed

Tap to wake

http://xdaforums.com/showthread.php?t=2949218

[Requires Root][Open Source] Doubletap to Wake Enabler v1.2
[Nexus 6  Original Android Development] hupo224:
Which camera are you guys using? I did the normal slim gapps package. But this one doesn't have HDR.
[Nexus 6  Original Android Development] dabug123:
So flashed hells kernel which has dt2w support but it won't enable tried an ap won't work don't see options for ..anything im missing or could do on my end..first for me seeing this happen
[Nexus 6  Original Android Development] capnkrunch:
I'm pretty sure Slim has all the proper blobs, the issue seems to be CAF induced. That is why all the AOSP roms work fine and is referenced in some IMS commits in CM's repos (for example the one [MENTION=2966179]Blaiser47[/MENTION] linked).

One CM commit to check out is: Add button in "hidden" settings to flip "VoLTE Provisioned" flag. That does what it says and, together with the build.prop edit gave me the "Enhanced 4G LTE Mode" switch in the "Cellular network settings" menu. I haven't tested if simultaneous voice and data actually works but that is the switch that should enable it.

EDIT: be aware that simulataneous voice and data can work if you are on WiFi even if it is broken over mobile. I've fallen for that trap before, make sure to turn off WiFi when testing this.
[Nexus 6  Original Android Development] kenbrownstone:
Anyone getting system ui force close after setting up color of recents ?
[Nexus 6  Original Android Development] Blaiser47:
Great work. If you want to share a build or if [MENTION=2033478]Yank555[/MENTION] can add it to the next build I am happy to help test. Been away from slim for awhile as I was on chroma after getting my N6 since things were slow in the slim department. I strictly ran slim on my S3, and man is it good to be back!

---------- Post added at 01:26 AM ---------- Previous post was at 01:19 AM ----------

I too couldn't get dt2w to work with HC. My guess, has to do with the custom ambient display settings slim has implemented. Anyone else have any ideas? Did you try any kernels that have flar2's version of dt2w like chroma's kernel or elementalx? Maybe they will work. I think HC uses googles stock implementation that was just off for our device.

---------- Post added at 02:03 AM ---------- Previous post was at 01:26 AM ----------

Edit. Just tried Elementalx and dt2w works.
[Nexus 6  Original Android Development] Blaiser47:
Anyone else notice that for some reason the saturation goes down about 60-70 seconds after boot on latest build? Looking at kernel aduitor it starts at 30 for situation intensity immediately after boot, but just over a minute in to a boot colors fade and intensity changes to 18. Thought maybe it was kernel related but happens in several kernels.
[Nexus 6  Original Android Development] dabug123:
Thanks
[Nexus 6  Original Android Development] capnkrunch:
Unfortunately, I just tried testing it and still no simultaneous voice and data in spite of the both the VoLTE Provisioned flag being set and the Enhanced 4G switch turned on. However, I switched back to Omni and realized it's broken for them as well. I fell for the wifi trap before when I thought it was working. I swear it worked in stock but maybe that was on wifi as well.

I have a test build but it's probably not worth posting considering it doesn't actually fix anything. Like [MENTION=2033478]Yank555[/MENTION] said, it is a rare occurance that you need both so not really a deal breaker. It would be nice to know if it actually works on stock and CM making sure wifi is off. I kind of want to play with the M preview build so maybe I'll check out VoLTE on some other ROMs on my way back.

Some observations:

The build.prop edit makes the Enhanced 4G switch show up in the cellular networks menu independent of the VoLTE Provisioned flag showing up in the hidden menu. The logs show that VoLTE Provisioned is true even when the button for it is blank.

On Omni, the hidden menu VoLTE Provisioned button doesn't work unless you turn the radio off first. On Slim the radio off button doesn't work. The commit I mentioned before does make the VoLTE provisioned button show the proper text but since the radio won't turn off I have no idea whether or not it actually works. Either way, it doesn't matter much since it works fine on Omni and simultaneous voice and data is still broken.
[Nexus 6  Original Android Development] Yank555:
Well I don't quite 'deny' any kernel, I mean any shamu kernel should be usable (except CM kernels as I thought to have read those might cause issues).

I've keen making "kernels only" for a few years before building ROMs, so it would be quite strange if I now would not 'support' the use of other kernels than the one coming with my ROM ;)

But if you run into kernel related issues, I won't be able to help as much (will try nonetheless), unless you are running the same kernel I do, as else I can't reproduce the issue (and I'm always running mine obviously ;)). In that case, help should be asked in the kernel thread, or here, of course, but from fellow users running the same kernel/ROM combo.

Slim basically comes with leankernel by default compilation, so imoseyon's is certainly an option, and the other usual suspects kernels certainly are as well.

There is nothing specific about the ROM for the kernel being used, unless you use a kernel that uses "anykernel" flashing method, hence it keeps the ramfs and doesn't bring its own. As in that case, my kernel config script will still be run on boot, with some settings being applied for stuff both the new and my kernel have in commun, and the rest will be ignored.

JP.

---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------

Works fine on my end, I've changed the colors right away to make them fit the dark theme I use.

(I've added a screenshot)

JP.

---------- Post added at 08:26 AM ---------- Previous post was at 08:24 AM ----------

Already on my todo list ;)

JP.

---------- Post added at 08:29 AM ---------- Previous post was at 08:26 AM ----------

If you run my kernel (stock coming with ROM), calibrated 6500K color profile is applied about 30-60 seconds after boot complete, that may be what you see.

Though once you run other kernels, that should be gone, except, as I said earlier, the kernel you use flashes using anykernel methode and has KCAL support, then my config script will still do that.

This has been this way since my first build, though, it's nothing new on my end.

If you want to remove my config script (I don't recommend doing so if you run my kernel !), remove /system/etc/init.yank555.lu.kernel.sh, or, better, simply edit it and remove the color calibration lines (if you run my kernel).

JP.
[Nexus 6  Original Android Development] danarama:
I can't say I know too much about it. All I think I remember is BVoLTE didn't work on any AOSP rom, then the vendor binaries were pulled from a Verizon build and it has been working since. Whether something has changed since then, I'm not sure to be honest.
[Nexus 6  Original Android Development] Yank555:
Did Verizon shamu get a 5.1.x update yet ? Maybe that's the issue then ... that there aren't 5.1.x Verizon blobs available yet.

JP.
[Nexus 6  Original Android Development] danarama:
Not sure. It works on Chroma I'm sure. Again, probably a question for [MENTION=1978554]zephiK[/MENTION] or [MENTION=1050103]sykopompos[/MENTION]
[Nexus 6  Original Android Development] warfenix:
What are these color profiles? I've never messed with the colors on phones. Is there a better setting/profile for our phones?
[Nexus 6  Original Android Development] danarama:
It's subjective. If you think the display is over saturated, you can adjust it if you need. I don't touch mine to be honest. I like it as it is.
[Nexus 6  Original Android Development] warfenix:
Only thing I have noticed is the display it self seem a bit...... Yellow I guess. Not as bright as it should be. I thought I remember reading this is normal for the nexus 6 though. So I wasn't worried about it. Although it is a bit odd looking. ( and I don't mean like overly yellow ) barely noticeable but there non the less
[Nexus 6  Original Android Development] Yank555:
It's compiling, I'll upload it likely in about 1h.

JP.
[Nexus 6  Original Android Development] danarama:
You could definitely compensate for that with a colour profile, if it was annoying you.
[Nexus 6  Original Android Development] warfenix:
Have you noticed the color tint or Hugh (sp) rather. I guess I might look up some profiles and see what it does
[Nexus 6  Original Android Development] danarama:
I can't say I have.
[Nexus 6  Original Android Development] Yank555:
The build is uploading for shamu, hammerhead is compiling.

Filename : "Slim-shamu-5.1.1.alpha.0.3-UNOFFICIAL-20150603-1303.zip"

It has the VoLTE switch commit for settings and a commit in device shamu (this one), and the updates in frameworks_opt_cards for the more "material" SlimRecents.

Not tested myself yet, so a nandroid is always a good idea.

Please report back if this helps, we'll push it to gerrit and try to get it merged.

JP.
[Nexus 6  Original Android Development] DroidIt!:
What I usually do is lower red and green by about 5% and for me that seems to make the whites ever so slightly whiter without really ever affecting the other colors appearances too much. I don't use profiles, just lower the red and green a bit. ;)
[Nexus 6  Original Android Development] Blaiser47:
Def works on stock as I have tried it. Also works on all other asop based roms I have tried so the solution is out there trick is finding it. I'll keep my eyes open for things and ask around.
[Nexus 6  Original Android Development] warfenix:
I will try that thank you
[Nexus 6  Original Android Development] Blaiser47:
Awesome thanks. I'll edit that file and see how we go. Also see dt2w disabled here so I can adjust that, good to know!

---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------

After looking into Yank's start up script (init.yank555.lu.kernel.sh located in system/etc/) I see dt2w is disabled. If you want to use his kernel or other kernels with the google implementation of this try removing those lines and I bet it will work.

Edit. Just tried with HC and it worked. Dt2w is back.

---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------

Great I'll give it a shot. Just fyi on the current build (2-june) I now at least have the volte toggle in cellular networks but doesn't work, as expected probably.
[Nexus 6  Original Android Development] Yank555:
You can also just download my kernel zip and flash it (link is in my OP in builders collective), everything in there is generated to your liking through an Aroma installer (and you can also only update the config), if you want to run my kernel, that is. The ROM just comes with my personal kernel settings pre-installed ;)

To activate dt2w (the stock google one) you need to :

echo AUTO > /sys/bus/i2c/devices/1-004a/tsp

If you use a different kernel, chances are VERY high that my script

will not get executed

. It is run from my init.rc in the ramfs that comes with my kernel.

So unless the kernel you use keeps my ramfs (anykernel flashing method), that file will just do nothing at all once boot.img is replaced as that will replace init.rc as well and thus not run the script.

JP.
[Nexus 6  Original Android Development] Blaiser47:
Great info thanks. I found with HC your script must have ran because colors were changing. Thanks for the info about customizing with your aroma installer, I'll try it out. Your help, support, and attitude are impeccable! This is why I love the slim community.
[Nexus 6  Original Android Development] rignfool:
[MENTION=2033478]Yank555[/MENTION]

Thank you for feeding my addiction...

I was almost cured... Then the 5.1.1 builds came out... And I fell right off the wagon
[Nexus 6  Original Android Development] franatic08:
Sweet!

Latest and greatest has 2 of my favorite functions added!

Good work.

Thanks!!