yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Broooooook:
If the "lockscreen lag" we are talking about is the delay of screen lighting-up after pressing the power button, then yes I see noticeable improvement with the latest test build. On the Aug. 25 build, the screen lighted up 0.5~1 second after pressing the power button. The Aug. 28 build, however, has a shorter response time. It's nothing annoying really, but I do see the difference.

Also a minor problem, under settings-sound&notification-other sounds, there are two "volume slider sound".

Thanks for the excellent ROM btw.
[Nexus 6  Original Android Development] liquidreign:
Running for 48 hrs with no lag.
[Nexus 6  Original Android Development] Yank555:
The lag is more a hesitation between first frame til device is usable (jank in the unlock animation).

So you see an improvement in powerup time ? Kay, will have an eye on thay, but that was not what we were chasing ;)

Thx, indeed I've seen the two slider, hope I'll not forget to remove that derp on the next build ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2a kernel.
[Nexus 6  Original Android Development] _Garry_:
I think it's more a kernel/CPU stuff why the lockscreen is lagging.

Using your latest test build from August in combination with despair kernel r29 cfs uber build, gov. is Lionheart and fiops sched, hotplug is intelliplug.Ofc i deleted the init.yank script.

Solong I had no lockscreen lags.

And to top it more I flashed xposed and xtrememusic.

Uptime of Rom is now +73hrs.

I added some Screenshots with my settings. The rest of settings are untouched.

BTW I changed Lionheart to be more aggressive, currently I don't look and care for battery but for smoothness and gaming ^^

Sent from my Nexus 6 running latest SlimRom
[Nexus 6  Original Android Development] PerfectSlayer:
I recently flash the latest test build too. I'll report in some days if lags come back. Thanks!
[Nexus 6  Original Android Development] Yank555:
Kernel is certainly not linked since this happens accross devices, and for sure that excludes kernels.

Also my kernel has a feature in my own cpu hardlimit kernel driver which kicks cpu min to 2GHz on wake, so CPU on my kernel will always be spinning at 2 GHz or more for 3 seconds when turning screen on. I don't know of other kernels doing this (don't think hardlimit has spread), they will rely on the governor to first see load and then rev up CPUs, which will always be slower as it's a reaction to load and on my end it's a reaction to screen on.

I've been mostly free of jank, uptime 91:20 ... but I'm not using my phone as I'd use it at home since I'm on vacation (no BT as no handfree, WiFi off mostly, no mobile data, thus not many notifications etc.).

I suppose this janking lockscreen issue will be solved eventually, as it's beeing worked on, but it's hard to catch since it's not reproducable at will ... thus it takes a tad more time.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2a kernel.
[Nexus 6  Original Android Development] Yank555:
Good run so far... (~95h uptime, almost never happens for me ;))

No bt, no mobile data, though, WiFi on.
[Nexus 6  Original Android Development] jayden2009:
Yank where can I find your kernel ?

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] fraz14:
Look in yank`s sig :) or flash a slim rom. The kernel is in slim shamu.
[Nexus 6  Original Android Development] _Garry_:
I didn't know you were already this far with problem tracking. But good to know.

When your are back at home and are going to build a new slim version, are you going to update layers too?

Sent from my Nexus 6 running latest SlimRom
[Nexus 6  Original Android Development] Yank555:
That bloody lag thing's been haunting some of us for m... no weeks, it's not quite yet 2 months ;)

Update layers ... aha ? What has happened on that end while I was enjoying some sun ? Will have to check, but certainly I intend to stay on track with layers.

JP.

PS: But I haven't coded that hardlimit kernel thing because of this, that driver is way way older, I started working on it when I was still rocking my Note 3 as a daily, continued working on it while I was using my HH and now shamu, so it's somewhere about 1 1/2 or 2 years old already ;)

This is it's current state : https://github.com/yank555-lu/Shamu-3.10-lollipop/commit/d1c02c8271af42ff622beb30dd2376acd83a7bfb
[Nexus 6  Original Android Development] liquidreign:
Running for about 5 days and still no lock screen lag or freezes. I must be one of the blessed.
[Nexus 6  Original Android Development] PerfectSlayer:
I'm using your test build since several days now and no lag encounter at all :good:
[Nexus 6  Original Android Development] Yank555:
I've checked and asked around, there's no update to Layers past 2.1... All I've added is the commit that allows QS tiles to be themed separately.

So my ROM is (will be) Layers 2.1 plus 2 commits :

- Exposing Settings backgrounds for more theming options, while not impacted stock

- Add the ability to color dashboard title independently

JP.

---------- Post added at 22:53 ---------- Previous post was at 22:52 ----------

This is fixed as well in next build ;)

JP.

---------- Post added at 23:14 ---------- Previous post was at 22:53 ----------

ROM Update

Slim-shamu-5.1.1.beta.0.6-UNOFFICIAL-20150907-2215.zip

- repo sync Mon 7. Septembre 18:28 CET 2015

- (shamu, hammerhead & flounder only) updated kernel to m-preview-2 Google sources (Yank555.lu)

- shamu : disable bcl (2-core & limited CPUfreq on low battery)

- Layers : add QS tiles layers

- CellularTile: Long-click triggers detail view instead

- Show icon of package associated with Toast

- ResolverActivity: reduce elevation to make it flat

- Fix the cell standby mobile radio active issue​

Download Link AFH

Download Link D-H

Full changelog & my BC OP Link

JP.

PS: ROM is still uploading on both sites...

EDIT : I've not included the "lag fix" set of commits in the build as it doesn't look to fix the issue we have on shamu.
[Nexus 6  Original Android Development] elementaldragon:
I think that's the one thing that keeps shying me away from SlimLP at this point. It seems that no matter what i do, there's always a rather high amount of lag with just about everything, ESPECIALLY when it comes to unlocking the screen and such. The JDX version of the Android M previews doesn't have that, and is BUTTER! I'm wondering if the idea of you switching to use the Android M kernel sources might help resolve that... but at this point i'm not sure if i want to try.
[Nexus 6  Original Android Development] Yank555:
The kernel has been android M for quite a bit ...

2015-06-07 : m-preview

2015-08-11 : m-preview-1

2015-09-07 : m-preview-2

I can't say I have any kind of lag except the single lockscreen lag on occasion, and we're talking a fraction of a second hesitation exactly once after screen on. While I agree that it's kind of annyoing, but other than that, it's really no deal breaker imho.

If you wanna know for sure, just try, it's not like it's going to damage your device ;) Nandroid, test ... if not good, restore Nandroid.

As for M, we need to wait for the sources to drop to be able to work on that, and use the corresponding vendor stuff that goes along, which for now we can't use due to lack of ROM-side sources.

JP.
[Nexus 6  Original Android Development] elementaldragon:
I dunno... all i know is last time i tried it (which i think was just the previous build) i'd almost ALWAYS have a lot of lag when it came to unlocking the screen, or even waking the screen up. I'd press the power button to wake the screen up... see the notification light go out.... nothing on screen. press the button again, notification light comes back on, still nothing on screen. Press the button another time, notification light would go out again, and screen would finally turn on. Then the majority of the time i'd swipe up on the screen to unlock, and the screen would freeze for 2-3 seconds before it'd unlock... during that time looking like i never even touched the screen.
[Nexus 6  Original Android Development] Yank555:
Did / do you use face unlock by any chance ?

Not had this a single time ever....

JP.

EDIT : A testbuild with a subset of the lagfix commits in (without hopefully all of the uneeded stuff) is compiling.
[Nexus 6  Original Android Development] MizzouBrent:
I'm down to test!
[Nexus 6  Original Android Development] elementaldragon:
I've toyed with face unlock in the past on my nexus 5, but never used it on my 6.

Maybe I'll try installing it later, and if it still happens, I'll record a video of it.
[Nexus 6  Original Android Development] Yank555:
It's uploading, should be up in the test folder in a few minutes...

JP.

---------- Post added at 01:35 ---------- Previous post was at 01:31 ----------

The testbuild is up :

Download Link

JP.
[Nexus 6  Original Android Development] TonyTurboII:
I was getting the lock screen lag pretty bad as well. I was using a pattern lock, with Smart Lock enabled to keep the phone unlocked whenever my Moto360 was in range. Not sure if that helps find the problem or not.
[Nexus 6  Original Android Development] Yank555:
I use smart unlock with both BT (my car) and "keep on me".

But the testbuilds had been rather good to me...

Worth trying the new testbuild.

JP.
[Nexus 6  Original Android Development] TonyTurboII:
Thanks for the heads up. Ill check the test build out.
[Nexus 6  Original Android Development] Yank555:
ROM Update

Small update, this contains a better bcl fix and the lockscreen fixes (helping with lockscreen lag).

Slim-shamu-5.1.1.beta.0.6-UNOFFICIAL-20150908-0127.zip

- repo sync Mon 7. Septembre 18:28 CET 2015

- updated kernel to m-preview-2 Google sources (Yank555.lu)

- disable bcl (2-core & limited CPUfreq on low battery)

- Layers : add QS tiles layers

- CellularTile: Long-click triggers detail view instead

- Show icon of package associated with Toast

- ResolverActivity: reduce elevation to make it flat

- Fix the cell standby mobile radio active issue

- Keyguard (lockscreen) fixes (helps with lockscreen lag issue)

- better fix : disable bcl (2-core & limited CPUfreq on low battery)​

Download Link AFH

Download Link D-H

Full changelog & my BC OP Link

JP.
[Nexus 6  Original Android Development] panni:
[MENTION=2033478]Yank555[/MENTION]: I'm on your 0.3 version of the SlimLP ROM with your 1.4+ Kernel (hammerhead, sorry for asking in the wrong thread). When I upgrade to the newest 0.6, should I also flash the 1.4+ kernel?

I've seen kernel updates in the changelog for 0.6, but no new version of your separate kernel. Also, will your ROM use the kernel settings I've had before, in the 1.4+ kernel, when I dirty flash to 0.6?

Thanks
[Nexus 6  Original Android Development] Yank555:
The newest kernel comes with the rom, and is not actually available as standalone (no time lol), I do my kernel coding in my ROM repos now.

If you want to change the kernel settings, though, you can use the latest kernel zip and change settings to your liking and select 'config only' at the end of Aroma, so you get your settings with the latest (rom-included) kernel.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3 kernel.
[Nexus 6  Original Android Development] panni:
Ah, thanks! So I've just downgraded the kernel from the 0.6 build apparently.

Great ROM so far, I just had those lockscreen problems, varying from 1 to 5 seconds of lag, with the 0.3. Will report back whether 0.6 fixed that.
[Nexus 6  Original Android Development] Yank555:
Hmmm ... yep ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3 kernel.
[Nexus 6  Original Android Development] hlxanthus:
[MENTION=2033478]Yank555[/MENTION] as of a week ago this bug still persisted. As far as I can tell, it is an issue that only troubles verizon users that have volte enabled and working. Disabling enhanced 4g fixes it but seems like a lot of functionality to lose ?. On a side note, it still happens with official cm too.

If a particular log would be helpful, please let me know and I will provide.
[Nexus 6  Original Android Development] JaylanPHNX:
Just from curiosity, does it happen if you use a third party dialer? Trying one might help narrow it down if it's a dialer issue or a deeper telephony problem. (Or I could be way off, since I've never used a separate dialer app and don't know how they work.)

From my SlimTab Pro 8.4
[Nexus 6  Original Android Development] liquidreign:
Slim-shamu-5.1.1.beta.0.6-UNOFFICIAL-20150828-1844

I have had this installed for probably 2 weeks with no Lock screen problems is this new one worth me flashing.
[Nexus 6  Original Android Development] Smallsmx3:
How did you fix the mobile radio active bug
[Nexus 6  Original Android Development] JaylanPHNX:
There's been a commit floating around that supposedly fixes it, but there's some debate over how effective that fix is. Some say it just fixes the count cosmetically, others say that fixing the count does help other processes that base their functions on that count. My guess is they're both a little right and the fix helps, but not as much as when Google fixes it in 6.0.

From my SlimTab Pro 8.4
[Nexus 6  Original Android Development] MizzouBrent:
So are the mobile radio battery stats with other roms correct or is the reporting just bad?
[Nexus 6  Original Android Development] panni:
I'm running "Slim-hammerhead-5.1.1.beta.0.6-UNOFFICIAL-20150908-0919.zip". All the lock screen issues I've had before are gone.

I suddenly got battery related issues with "bam_dmux_wakelock". Are there any known fixes besides the ones suggested widely? Such as:

- disable google location services

- disable google now

- disable ipv6 (?)

Is that what you're referring to by saying "mobile radio active bug"?
[Nexus 6  Original Android Development] Yank555:
No, bam is bluetooth related if I remember well, long time no see that one...

Do you use anything via bluetooth ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] panni:
Yes I do, but it's not BT related:

(from https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/bam_dmux_wakelock)
[Nexus 6  Original Android Development] Yank555:
Ah correct, as I said long time ago I heard from that one ...

The mobile data commit, which is still being discussed, will only try to correct the wrongfully mobile data active time for apps, but as far as I understood does not have any impact on battery, as the mobile data was not really active that time (so tries to fix an accounting error).

In your case, though, it really seems to be active.

Any app which generates mobile data will trigger that wakelock, anything newly installed lately, or updated (check the recently updated apps maybe).

ROM-wise I haven't seen anything thelike on my end, so I expect it to rather be an app issue.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] panni:
Nothing I'm aware of, no. The weird thing is, this still happens even when WiFi is connected. Couldn't figure out yet how to circumvent that.
[Nexus 6  Original Android Development] hlxanthus:
[MENTION=2033478]Yank555[/MENTION] any thoughts on the unknown outgoing call bug?

http://xdaforums.com/showthread.php?p=62794847
[Nexus 6  Original Android Development] Yank555:
Have you, for test's sake, tried to fullwipe and check if that happens on a clean setup (no apps etc, just setting app google and WiFi) ?

Or course after a nandroid, so you can easily get back to where you are now ;)

JP.

---------- Post added at 17:25 ---------- Previous post was at 17:21 ----------

That's going to be a tough one on my end, I don't have VoLTE service over here, nor enhanced 4g (no clue what that is, what you'll lose) :(

Can you describe this whole thing as precisely as possible (either here or via PM) ?

Also, can you grab a logcat while you place such a call (record log while it happens) ?

But I'm rather unconvinced I will be finding much as I can't reprocude on my end, but it's still worth a shot ;)

JP.
[Nexus 6  Original Android Development] panni:
Not yet, but will do. I've just dirty flashed 0.6 over the 0.3 version of your SlimLP build. I didn't think that it would have any negative effect, as I've always dirty-flashed minor-version SlimROM updates before.
[Nexus 6  Original Android Development] Yank555:
Agreed, I also always flash dirty on my end.

But well, once it starts misbehaving a loop to clean is always a good idea ;)

There should be a 0.7 available tonight, though, so you may wanna wait for that and try it first ? (been running it for about 24h now, kernel WiFi changes...)

JP.
[Nexus 6  Original Android Development] jayden2009:
[MENTION=265093]yank[/MENTION]555 since im still not on your ROM ( I'm sorry ?) is it possible to only flash your kernel on benzo ROM ?

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] panni:
Nice, will wait for that. How regularly do you update your GApps packages? Do you look for the newest slim zero gapps every time you flash a new ROM version, or less often?
[Nexus 6  Original Android Development] hlxanthus:
Enhanced 4G is essentially the larger service that VOLTE is a part of, and allow simultaneous voice and data (which is why it is rather important to not have).

But I can certainly grab a log for you possibly this evening and will provide a detailed description as to what it is and isn't doing properly when I give you the log.
[Nexus 6  Original Android Development] Yank555:
I update every now and then, no real rule, simply if I feel like it or I think something's off with the one I use.

JP.

---------- Post added at 18:56 ---------- Previous post was at 18:54 ----------

You'd need to download my latest standalone kernel zip, download latest SlimLP and replace boot.img in the kernel zip with the one in the SlimLP zip to have the latest, I haven't updated the standalone kernel lately due to lack of time...

Also, it my work just as it may not work, depends on what benzo ROM would expect in the ramfs, my kernel will have SlimLP ramfs.

JP.
[Nexus 6  Original Android Development] Yank555:
The ROM is up (fell alseep yesterday evening :angel:) on both sites :

https://www.androidfilehost.com/?w=files&flid=31092

http://d-h.st/users/yank555/?fld_id=45173#files

Changelog will follow later today...

JP.
[Nexus 6  Original Android Development] LuRock:
Thank you! About to flash this baby, what gapps can I flash with this rom? Read something about 5.0? Or is any updated gapps OK to use?
[Nexus 6  Original Android Development] Yank555:
I always use Dankoman's :

http://xdaforums.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

JP.
[Nexus 6  Original Android Development] hlxanthus:
[MENTION=2033478]Yank555[/MENTION] This is the log you asked for in regards to the unknown outgoing caller bug (unknown_outgoing_call_history.txt).

To better describe the issue, when placing a call either from the dialer or from a contact, all outgoing calls read as unknown in the call history after ending the call. If I disable settings > wireless & networks > more > cellular networks > enhanced 4g lte mode, the bug disappears. But then no VOLTE or simultaneous voice and data. Also, as far as I can tell it doesn't matter if actually connected to LTE or not, just that enhanced 4g is enabled or not. Also, as near as I can figure, this only affects users on the Verizon network (as tmobile users don't seem to have this issue). This bug has been present going back to the beginning of June when I first noticed it in both slim builds as well as cm and a few others. I believe the issue popped up at or just after 5.1.1 was originally released.

The log above is from a clean install of the sept7 build with supersu and tk gapps full modular (in the past I have tried various gapps packages or adding google dialer with zero change) installed, nothing else. Booted, logged in, and let it sit 10 min before taking log. Placed a call with wifi and enhanced 4g enabled and call was shown as unknown in the call history. Turned off wifi, placed another call and it showed as unknown in the call history. Turned off enhanced 4g, placed yet another call, and the call history showed that call correctly (just that one, the others still read unknown).
[Nexus 6  Original Android Development] Rd. Vortex:
I recently switched from OnePlus One to Nexus 6 since the OPO died. As soon as I had a case and SIM for my new N6 I installed SlimLP on it.

There's one bug though that seems to have followed me from OPO to N6. On some apps parts of the GUI are sometimes hugely magnified, up to the point that it breaks usability. As said before, I had this same bug on the OPO builds but it usually wasn't bad enought to bother me. Does this happen to anyone else? I'm using the default DPI of 493.

This is how GPS Test Plus looks like when I initially launch it.

When I rotate screen to landscape and then back to portrait the issue is fixed.
[Nexus 6  Original Android Development] Yank555:
Interesting, never seen that behaviour before...

Try setting the dpi in build prop to stock 560, and use display dpi menu to change it to your liking (though 493 won't be in the list, it's in steps of 20).

JP.
[Nexus 6  Original Android Development] Rd. Vortex:
Thanks, that seems to have fixed the issue for now. Changed back to 493 from build.prop. How come 493 isn't on the dpi menu since it's the default that the ROM ships with?
[Nexus 6  Original Android Development] hlxanthus:
493 is the actual PPI of the device. 560 is the stock DPI.
[Nexus 6  Original Android Development] Yank555:
If it's the default the ROM ships with, then I need to fix that, it should be stock 560 :D

JP.

---------- Post added at 20:24 ---------- Previous post was at 20:20 ----------

ROM Update

Small update, but interesting, as it is now easier to switch to whatever kernel (anykernel flash) you like without deleting anything. The bootprocess will be full stock (using mpdecision / thermal-engine...) and only if the kernel installed is mine will it switch over to my kernel stuff once boot is complete.

Also WiFi was wonky, so I reverted the bcmdhd (WiFi) updates that came with the 2 latest m-preview kernel source updates.

Changes :

- repo sync Mon 14. Septembre 11:42 CET 2015

- RRO: idmap: fix sorting of overlays.list

- base: add back rotating back button when keyboard is shown (may be wonky atm)

- kernel: revert bcmdhd wifi driver to m-preview (from m-preview-2)

- kernel-config: only run kernel-config script if kernel is Yank555.lu (no more need to delete the file if you run a custom kernel !)​

Android File Host

/

Dev-Host

JP.
[Nexus 6  Original Android Development] Rd. Vortex:
That's the default that was set for me when I initially flashed. Didn't think there was nothing special since basically all Slim builds that I've used have shipped with other DPI than the stock for that device. :P IMHO the 493 is just fine as default DPI for the ROM. Just found it odd that once you change away from it there's seemingly no way to change back unless you edit build.prop directly.

Initially even the DPI setting shows nothing selected since there's no such option as 493 in the list.
[Nexus 6  Original Android Development] Yank555:
Well there's been one change, Slim keeps the base dpi stock now, and uses a different way to change the display dpi, this means also that gapps don't need any dpi fix anymore either.

I'll have a look and switch shamu to stock 560.

You can use 500 or 480, it will be very close to what you have now.

JP.
[Nexus 6  Original Android Development] blakmazk:
As far as I remember anything below 493 dpi would force some apps into tablet mode. Better change it to 500.
[Nexus 6  Original Android Development] TJKV:
Just to add to the dpi discussion, I have noticed too that on a fresh install it is necessary to switch dpi to some other value and then back to the value you want.

Until that is done, some apps display overblown assets (eg keepass4android). Been doing this after every clean flash since a few months [emoji14]