yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Yank555:
OK, we're entering kernel territory here, that's where I actually come from, been kernel hacking for years, ROMs are new since about 5 months :D

When you say "well I killed your boot script and that did it for me." what exactly did you do ?

If you removed init.yank555.lu.kernel.sh, then you're running the kernel very Google stock like ... or did you mean sth else ?

If you run my kernel, don't mess with CPU min/max freq in apps, EVER, it's very far from stock kernels and stock freq limit handling ;) If you want to make changes, either edit the config file mentioned above, or download my kernel zip, flash it and you'll get to an Aroma installer letting you change all of the settings which will generate a script to your liking for you.

Apart from faux clock (see screenshot), none of the kernel apps knows how to control CPU freqs in my kernel, because I use my self written CPU hardlimit driver, which controls CPU freqs limits and has its own touchboost implementation.

My kernel uses faux's intelliplug and intellithermal, disables mpdecision / thermal-engine, has no cpu_boost (at all, neither its touchboost, nor migration boost), uses my own configurable 2-step touchboost, screen on/off min/max (for ANY governor), wakeup kick, userspace lockout ...

And what you see at 883MHz is my own touchboost, low level. Whenever you touch the screen, cpu min will go to touchboost low (883 in my config, can be changed) for 1 second (configurable), touch the screen 4x (can be changed) within that 1 second, and it will go to touchboost high (1.26GHz, configurable) for 1 second at least or as long as you keep touching the screen plus 1 second.

CPU min/max cannot be changed, by any app (except faux clock), because of userspace lockout, the kernel will not accept any change (ignore in my config, you can set it to ignore or refuse, refuse gives an error to userspace, ignore will behave as if it accepted, but won't apply), all freqs are controlled in a different sysfs interface : /sys/kernel/cpufreq_hardlimit/*

If you feel comfortable enough, go have a look there in a terminal, I think it should be pretty self explaining, but don't hesitate to ask if not ;)

On the other hand, if you run any other kernel, all of the above does not apply, and there is nothing I could do that would mess with the other kernel, as my config script is just a dead script file lying around, it's not getting used unless you run my kernel. Maybe except if the kernel you run is using "anykernel" to install, in which case, some of the settings will be set, other just give an error because of the missing sysfs interfaces of the other kernel.

Have a look at "/system/etc/init.yank555.lu.kernel.sh" and "/data/kernel-boot.log" to see how the kernel is setup.

Here it is, but it's a "do a lot of things" kind of zip, it will remove some stock stuff, add some other stuff, add layers and a stripped down slim mini gapps... I suppose it's at best likely a base for you to get started with and make your own ;)

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

JP.
[Nexus 6  Original Android Development] _Garry_:
Ah...okay, thx for the explenation. Now i understand your kernel better i think i will again play around with your script.

But I deleted the whole init.yank555.lu.kernel.sh, because I like to test around until i find my personal best setting - and i felt uneasy with with your "default" settings.

Your kernel in SlimLP 5.0.2 was my favorite kernel because of the setup script. Easy to change and to handle....even adding my own settings in the setup script was possible ^^

For changing kernel settings I also use FauxClock. I like this tool because there is everything i need.

And thank you for your script. I was trying to build my own script but it didnt wanted to work the way i wanted it.

But now i have something good to look at and learn from.

Reffering to Slim Gapps i use the Zero Gapps because its slim and only uses the apps which are required. The google apps which i use, well i download them via playstore.

Solong again thank you for your long post and help me understand some stuff better then before.

PS When will there be a new yank release? ^^
[Nexus 6  Original Android Development] knightsh:
Has anyone gotten tap 2 wake to work on Slim5.1? I've been trying with no success. Tried the modified system/lib/hw with no luck. That's the only thing I'm missing. Loving having some Slim again!!
[Nexus 6  Original Android Development] Yank555:
That's the whole point of settings, everyone can make his/her own ;)

I haven't changed anything on my end for a very long time, though, so my Aroma default are pretty the same since the beginning I've made shamu kernels.

Crap, I just noticed that I didn't upload my "new" SlimLP kernel, since the AOSP won't boot anymore.

If you want to change the settings in the script without manually editing the file, you can just reflash the kernel and select "Config only" at the end of the Aroma menu, I've uploaded the kernel zip right now : http://yank555-lu.net/viewtopic.php?p=9286#p9286

Anyways, whenever you have a question regarding those settings, just let me know ;)

What I do as well, I'm still using older gapps, dunno if back then there were "less than mini" ;)

Not until some time next week, been on HH today, trying to get it going without using too much of CM, but no luck, and out of house all WE, real life and stuff (still preparing that car meeting due the last WE of this month) ;)

JP.

---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------

Just put this in an init.d script :

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

You will have a slightly higher battery drain, though.

JP.
[Nexus 6  Original Android Development] Tylog:
Edit : I see you got a answer, two days no xda and Tapatalk starts kidding me
[Nexus 6  Original Android Development] PerfectSlayer:
Impressive release [MENTION=2033478]Yank555[/MENTION] !

To all using this release: is-there a way to calibrate screen colors?

Note: I have sounds in double (with some times event the same name) ;)
[Nexus 6  Original Android Development] Yank555:
Yep, the kernel has KCAL support, fauxclock and fauxdisplay allow it, and I suppose there are other apps.

My default config uses the calibrated 6500K values found in imoseyon's thread :

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] Tylog:
Tomorrow I have a free day, then I have to renew completely the OP.

Edit: I had to replace my day off, I'll come until Tuesday to do .
[Nexus 6  Original Android Development] the.emilio:
Sheesh what is your DPI set at? Those icons in your screenshot was extremely small lol
[Nexus 6  Original Android Development] Yank555:
Hardcore 400dpi ... for now at almost 44 my eyes still playing along :D Guess I'll switch gradually up as time will go by ;)

JP.

Sent from my Nexus 9 running Yank555.lu AOSP 5.1.1_r2
[Nexus 6  Original Android Development] eBoody:
Is there a technical reason we can't do the status bar brightness control while adaptive brightness is set?
[Nexus 6  Original Android Development] danarama:
I use 400 too.

Though I usually set chrome lower.
[Nexus 6  Original Android Development] Tylog:
400? My eyes are to old for this size, I need XXL glasses then :)
[Nexus 6  Original Android Development] danarama:
The only issue I get is when you pull down the as tiles, the battery icon is hard to press. But Xposed fixed that.
[Nexus 6  Original Android Development] franatic08:
Does 400 DPI suffer from the half black screen when rotated to the right (power/volume buttons facing down)?
[Nexus 6  Original Android Development] Yank555:
For me yes, if I turn the device right to landscape (buttons facing down).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] franatic08:
Im still looking for a low DPI without the half screen issue. At 440 its also there. I'll keep looking and trying.
[Nexus 6  Original Android Development] danarama:
I just turn off 270 rotation because I like buttons at top anyway.
[Nexus 6  Original Android Development] Yank555:
What he said, same here ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] franatic08:
Very true, i seldomly rotate to the right too. But, its the feeling something's not OK. Although not all apps suffer. I only notice if I try, the rest of the times I rotate the device to the left.

Thanks for the feedback!
[Nexus 6  Original Android Development] the.emilio:
So I'm running the latest by [MENTION=2033478]Yank555[/MENTION] and I noticed when using Play Music and the screen off, there is about a 5 second delay/silence when skipping tracks. With the screen on there is no delay so that leads me to believe it is something to do with the phone being in a sleep mode. Right? Is this something I can adjust in the kernel? Thanks.
[Nexus 6  Original Android Development] Yank555:
If the phone is playing music, it will not be in deep sleep, but when screen is off, the device will work in single core mode and CPU max freq is limited to ~1,4GHz.

You can change the freq. either by editing my kernel init-script (/system/etc/init.yank555.lu.kernel.sh) or downloading my kernel zip (link in post 14 in the collective) and reflashing it, you'll go through a user friendly Aroma setup where you can set it higher (stock = screen off max is same as screen on freq).

That is if you use my kernel (comes with the ROM). If you use a different kernel, the above will does apply and you'd need to check how the kernel you're using handles screen off.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] liquidreign:
Just put this in an init.d script :

Code:

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

chmod 444 /sys/bus/i2c/devices/1-004a/tsp

You will have a slightly higher battery drain, though.

I put this in the etc/init.d folder but still no go with double tap to wake.
[Nexus 6  Original Android Development] Yank555:
To be precise, the file in init.d needs to look like this :

#!/system/bin/sh
echo AUTO > /sys/bus/i2c/devices/1-004a/tsp
chmod 444 /sys/bus/i2c/devices/1-004a/tsp

The file needs to be in /system/etc/init.d and have ideally 755 as fileaccess.

You can do a simple test, just type "echo AUTO > /sys/bus/i2c/devices/1-004a/tsp" in a terminal and test if double-tap works.

Just tested, works for me.

JP.
[Nexus 6  Original Android Development] liquidreign:
Thanks JP this was kind of new for me, but just now figured it out and got it to work. Appreciate your help!!
[Nexus 6  Original Android Development] danarama:
Shouldn't we all be using su.d now?
[Nexus 6  Original Android Development] Yank555:
I've been a SuperSU afficionado for years, I feel a build is incomplete without it ;)

Haven't tested how well built-in su works...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] danarama:
I just mean as a replacement to init.d, I think Chainfire recommends it as it executes after SuperSU
[Nexus 6  Original Android Development] Yank555:
Oh ... then I misunderstood. Never used it, tbh ... well it's very long ago that I actually used an init.d script, I run my kernel config script directly from init.rc.

But to do stuff like actived dt2w, init.d should be fine.

JP.
[Nexus 6  Original Android Development] liquidreign:
Weirdest thing after I rebooted dt2w stopped working. Any suggestions?
[Nexus 6  Original Android Development] Yank555:
New shamu 5.1.1 build available in my OP

There has been quite some activity on SlimLP base, again, so, again, it was time for a repo sync ;)

I've reverted the SlimLP navbar for now and still included mine based on CM. It does have less "options", but for now I prefer how it behaves.

If you want, I could spin a build with the stock navbar, just let me know, but not tonight, it's past midnight here, time to get some rest ;)

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

JP.

PS: devhost & AFH uploading, filename = "Slim-shamu-5.1.1.alpha.0.2-UNOFFICIAL-20150519-0023.zip".

EDIT : Damn, AFH has disabled uploads for the moment ... dev-host is uploading, I'll start the upload on AFH hopefully when I get up, in about 7h...

---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------

Did you do the terminal thing, or the script ?

If you just activate it in terminal, that will never survive a reboot, hence the need for a script.

Just download my kernel zip and flash it in recovery. You will have the option to have dt2w enabled or disabled, leave the rest of the options untouched and you'll have the same config, with just dt2w enabled.

JP.
[Nexus 6  Original Android Development] liquidreign:
I put the script in the init.d folder. I will try the kernel zip.
[Nexus 6  Original Android Development] Yank555:
AFH upload started, should be upmin 10-15 mins.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] warfenix:
I see 2 slimlp on android file host for the 19th is there a difference?
[Nexus 6  Original Android Development] PerfectSlayer:
The new navbar does no more have landscape bug. I had the keyboard arrow and when I was in landscape orientation, I saw random icon when the keyboard is closed (the plus icon, the 3-dots menu, a weird arrow too…).

Now, seems to work nice:good:
[Nexus 6  Original Android Development] Yank555:
The things I prefer with my navbar is the fact that lockscreen behaviour is more sound (back and power will show on pin-lock, animate fall down if you back out of pin-unlock, no menu key in lockscreen, other keys fade in once unlocked etc.).

JP.
[Nexus 6  Original Android Development] _OverKill_:
hi Yank555...slimrom based 5.1.1 r2?
[Nexus 6  Original Android Development] Yank555:
Not yet, SlimLP is LMY47V (5.1.1_r1) while 5.1.1_r2 is LMY47X.

JP.
[Nexus 6  Original Android Development] _OverKill_:
Ok thanks
[Nexus 6  Original Android Development] paour:
Modem and bootloader

[MENTION=2033478]Yank555[/MENTION] you indicate the bootloader and modem must be updated before upgrading to your 5.1 builds, but I have not seen indications of how (or which modem/bootloader). I tried a few (flashed from recovery) and when I boot into your new rom and kernel, I get the com.android.phone crashes and can't unlock the SIM.

Which modem should I use?
[Nexus 6  Original Android Development] Yank555:
The latest which comes with 5.1.x factory images, would be "5.1.0 (LMY47I)" (found here).

It's not a must, but if something doesn't work, update first before you post ;)

JP.
[Nexus 6  Original Android Development] bokuhmin812:
No Volte

Thnak you for the NICE rom But No Volte for VZW users..:p
[Nexus 6  Original Android Development] liquidreign:
Kernel worked although dt2w is still kinda buggy in general. The reason I wanted it is because it's more convenient to use while on the Cardio machines at the gym.

So thanks again.
[Nexus 6  Original Android Development] Yank555:
That's the reason Google didn't keep it eventually ;)

And since it drains battery, I never used it personally.

JP.
[Nexus 6  Original Android Development] danarama:
Very little battery use for dt2w on an N6. (1% per 10 hours approximately). Only issue is N5.. Only n5 drains dt2w
[Nexus 6  Original Android Development] brando56894:
Once this becomes more stable it will probably be my layers based daily driver, I've been rocking Slim on my phones for years, probably ever since the Rezound.
[Nexus 6  Original Android Development] Yank555:
Well I had seen worse than that on my N6 back in the beginning... ;)

JP.

---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------

What exactly do you mean by "more stable" ?

It's been perfectly stable from first build, at least to me, and I suppose others here, as I've no feedback of issues, crashes, reboots etc, well not so far ;)

JP.
[Nexus 6  Original Android Development] tracker01:
i just flash the rom and device don't turn off..

i don't know if i am doing something wrong
[Nexus 6  Original Android Development] Yank555:
Can you be more precise ? When exactly does it not turn off ?

JP.
[Nexus 6  Original Android Development] tracker01:
when you hold the power button - power off. it will not turn of the device.
[Nexus 6  Original Android Development] Yank555:
Very strange, works on my end. Anyone not able to power off the device ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] SFG:
Hey Yank55, on your 5/19 build and I have seen it in prior builds, I have a roaming indicator on my cell signal in all areas where I never roam. I am on Verizon. Any ideas? Is this just cosmetic?

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

Works fine on my end
[Nexus 6  Original Android Development] DroidIt!:
Done and flashed about all your builds :) and never had that issue. ;)
[Nexus 6  Original Android Development] renny083:
Power off is fine running rock solid and stable over here?

Sent from my Nexus 6
[Nexus 6  Original Android Development] liquidreign:
I wonder if quick boot mode is on instead of normal power off in developer options

I tried it to see what it was and when I tried to power off it did absolutely nothing.
[Nexus 6  Original Android Development] elementaldragon:
Only thing i've noticed with the 5.1.1 test builds is that, at least on my device, they seem to get QUITE laggy. Meaning there are times i'll take a picture, and everything will freeze for several seconds.... or i'll press the power button to turn the screen on, and it won't turn on for a few seconds or i have to press it one or two more times.
[Nexus 6  Original Android Development] mr_clean5953:
Turn off proximty check in display settings, and check your cpu max speed, for some reason mine was stuck at around 1200mhz
[Nexus 6  Original Android Development] elementaldragon:
Any way you'd recommend to check/adjust the CPU speed? Never had to really bother with that on any other phone before.
[Nexus 6  Original Android Development] mr_clean5953:
Francos app FKUpdater should work
[Nexus 6  Original Android Development] liquidreign:
T-mobile wifi hotspot

Is anyone else having an issue with tmobile hotspot tethering? I couldn't find any info while searching. I do the thether_dun_required value 0 and I can thether but when I check my tmobile account usage it keeps racking up data. If I use a switcher agent it slows the accumulation down but doesn't stop it. Is ther a new way of getting around this? I am on yank555 build of 5/19 5.1.1
[Nexus 6  Original Android Development] capnkrunch:
In the cellular networks menu there is no Enhanced 4G option and it also isn't in the 4636 dialer menu (there is simply a blank box where it should be). The roaming indicator used to be present for me on Verizon in the pre 5.1.x ROMs but it's OK on stock and Omni since 5.1. For what it's worth my guess is that the Slim repos are missing some commit from AOSP that enabled VoLTE (enhanced LTE, HD calling, or whatever Verizon wants to call it). However, I briefly looked through the device and vendor repos and nothing stood out to me. Maybe it's something more general in the telephony repo or something but I doubt it. Hopefully the Slim Team can look into it for us.

EDIT: A little more browsing through the repos has me thinking it may be somewhere in Telephony that the issue is. The VoLTE provisioned flag needs to be set which is something the IMS manager does but like I said in the 4636 menu there is only a blank button where the set VoLTE provisioned flag button should be. Slim's Telephony repo looks to be pretty much up to date with AOSP though so it's still a mystery to me. If I have some time tomorrow I'll try diffing some of the Slim repos with AOSP and maybe that will point me in the right direction. Since it works on both Omni and stock at least we know there's no need to reinvent the wheel. It should just be a matter of finding the relevant commit(s) and cherry picking/merging them into the Slim repos.
[Nexus 6  Original Android Development] SFG:
Thanks for the in depth explanation. I noticed that the enhanced 4g option wasn't present but I didn't correlate the 2. Makes sense and I'll just press on as if all was normal. :)
[Nexus 6  Original Android Development] capnkrunch:
Yup. Luckily it doesn't seem to affect using data and calling at the same time or calling in general as was the case in with 5.0.x on Verizon (which is kind of bizarre when you think about it). Because of this, I imagine it's rather low on the Slim Team's priorities, especially considering all the work that's going on with layers and whatnot on this device specifically, and Lollipop features in general. It's really just a slightly annoying cosmetic quirk and I'm sure in time someone will figure out the problem or it might even go away on it's own as they merge more AOSP code into their repos.

FKUpdater should work as mr_clean5953 mentioned. Trickster MOD is another popular one, and my personal preference for free ones. FauxClock is what I would normally use but it's a paid app only. Really there's a number of good apps and any of them will get the job done.
[Nexus 6  Original Android Development] Yank555:
Aha ... you might be onto sth. Didn't even know quickboot was in there (not a fan of it anyways).

I'll check that, thanx !

I'd recommend leaving that off in any case.

JP.

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

---------- Post added at 08:12 AM ---------- Previous post was at 08:04 AM ----------

Yup, proximity check most definately ;)

As for the CPU freq, was that on my kernel ? Never seen that happen on my end in ~6 months I'm running it.

To control my kernel, best app would be fauxclock, as to my knowledge, only his includes support for my cpufreq hardlimit driver.

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:
Disable the quick boot option in developer settings, it's disabled by default.

If you enable it, the behaviour you describe seems intended to me given the description.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] elementaldragon:
I installed CPUz to check what the clocks are, and it said a minimum of 300mhz, maximum like 2.2Ghz IIRC.... So that's not an issue.
[Nexus 6  Original Android Development] _Garry_:
Hey yank,

will you build a new release this weekend? I ask because I finally have time to flash my phone around. ^^

Sent from my Nexus 6 running latest SlimRom
[Nexus 6  Original Android Development] Yank555:
Would have to check if enough has changed in the base (nothing new on my end, been working on flounder lately) ...

But if not this WE, then it'll be after june 1st ... real life calling, we organise a pretty big (for the few we are to organize) car meeting on the WE of 30th-31st, so very busy till then, but I should have a little time this WE.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Nexus 6  Original Android Development] Tylog:
Delete. Wrong thread.
[Nexus 6  Original Android Development] x111:
Is anyone have issues with bluetooth connection ?

Since Slimrom Slim-shamu-5.1.1, auto bluetooth connection with car stereo need to be manually reconnected because of constant sound interruption.

Also, reorient volume buttons always turn back to their state in portrait mode.

It's so annoying when increasing sound button swapped to the other button. Why google did that, it's so uncomfortably.