yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] TJKV:
You sure you were on the correct modem etc? A few posts above the one I linked to someone says ds works fine.

If you have made sure nothing is wrong on your end, then why not reply to prbassplayer there and let him know?
[Android Builders Collective] ArjunSindhya:
whoops. tapatalk linked to the top of the thread. will try now XP
[Android Builders Collective] morfances:
[MENTION=2033478]Yank555[/MENTION] Last build test not work . bootloop

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] diegocr:
Thanks, can flask ukm and install synapse for kernel tweaks

info.... simply a slimlp build with [MENTION=2095315]ezio84[/MENTION] updates, [MENTION=3685904]ak[/MENTION] kernel and [MENTION=1228651]fusionjack[/MENTION] slimota, repo synced & build, next ones will upload changelog :good:

Nothing new, only repo synced to r9 , reboot menu too seems stretched
[Android Builders Collective] TJKV:
A clean install of the hh build gives me systemUI FCs on bootup. Tried to logcat -v long but device doesn't show up on adb at that stage of boot, or usb debug is disabled by default on your build :p The download is fine, md5 checks out.

Yeah, that's why I don't use tapatalk for anything except giving out more than 8 thanks per day.
[Android Builders Collective] Garrykd:
Damnit! I dirty flashed the hh build so I thought it was just the mako build that derped. :( Thanks for the heads up:good:

The recent av commits required a make clean, which I neglected to do the first time:o

New builds are up and they should be fine now.:fingers-crossed:
[Android Builders Collective] TJKV:
Works fine for me.

[MENTION=2033478]Yank555[/MENTION] Why not move the time to the left of the date when the latter is turned on in Statusbar->Clock and Date? Would look better IMHO

Haha awesome, will try it out now. BTW you on 999 posts! Make the next one worthwhile ;)
[Android Builders Collective] Yank555:
I'm away from PC today ... could do tonight or tomorrow night, but please PM me if I forget ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] martinoff:
Hi fellas

Is anyone here building wirh V4A ?

need a little help how to do it :fingers-crossed:
[Android Builders Collective] Yank555:
Flash a different kernel right after the ROM before first boot.

JP.

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

---------- Post added at 04:54 PM ---------- Previous post was at 04:52 PM ----------

Already im my head to add a switch, but my spare time ran out today ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] colida:
Never had any lags with your 05/07 build!

And still don't have any :)
[Android Builders Collective] Mikulec:
Ok, I will just shoot some questions to discard some options/apps that could cause the lags.

What DPI do you use? Do you use hangouts? Do you have enabled the option to "Prevent accidental wakup" under Display settings?
[Android Builders Collective] ca110475:
[MENTION=2033478]Yank555[/MENTION] bootloop confirmed even with manual kernel reinstallation on top of completely setup and working rom :/

Looking forward to try your kernel man. Other than that, ROM works like a charm.

:good:
[Android Builders Collective] colida:
I use 360 DPI, I do not use hangouts. I can't find the option "Prevent accidental wakup" in display settings. It was there in Yanks latest build ( I flashed it to check the lag.Did not have any, but the battery drain was high on my phone). But on the 05/07 build from eizo I can't find it.

By the way I do use ElementalX Kernel and Gapps Slim_zero_gapps.BETA.5.1.build.0.x-20150702.
[Android Builders Collective] Yank555:
Well, not sure that'll happen, as I have not the slightest clue why some of you have these bootloops, I never ever had a single one of them, just as many others don't have them :(

So I wouldn't know what to be looking at as I just can't reproduce it...

Something must be different ... just what ?

Which bootloader do you have ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] ca110475:
Agree that the 'spot the differences' approach might give some result.

In my case, bootloader HHZ12h, radio .26.

Coming from a clean installation, meaning everything has been wiped except for internal storage.

You mentioned you would have give a shot building it 'inline' into the ROM, but i'm not sure what exactly it means and what's the difference with the current way it is built.

Don't mean to waste your time anyway. It's a weird issue indeed.
[Android Builders Collective] JaylanPHNX:
Use the zip from here. It even works with selinux set to enforcing, so long as you're using superSU. http://xdaforums.com/showthread.php?p=47858556 Just remember the surround zip is only for N5.

From my SlimTab Pro 8.4
[Android Builders Collective] Thecrazyskull:
Just a wild guess, maybe different/outdated rom sepolicy? Try forcing it to permissive ;)
[Android Builders Collective] Yank555:
OK, BL and radio are the same :silly:

Building inline means the kernel getting compiled with the ROM. Atm I replace the boot.img file in the ROM zip. I will definately try that, be it alone because it'll be less fuss for me "build - flash the zip" instead of "build, replace boot.img - flash the zip" ;)

It's certainly no wasted time, I'd relly love to understand this, as I hate to not understand and for a kernel of mine making issues, so whatever comes to your mind, just let me know, there's no weird idea, just dump your thoughts :D

JP.
[Android Builders Collective] openlatedotorg:
Ditto here with nexus 5
[Android Builders Collective] Yank555:
Inline building would definately avoid any such change to get missed since replacing the boot.img means replacing the ramfs.

But I'd rule that out, cause if it was that, I should have the bootloops as well.

JP.
[Android Builders Collective] ezio84:
The 05/07 build should be lag free indeed, the problem is it has not the updated BT stuff.

If you don't need BT for streaming, that's still my best working build. If you need BT, you have to use the last build with this damned lockscreen lag lol.
[Android Builders Collective] Yank555:
OK, so the left-side clock plus option so set date left or right of clock is done ;)

Finish compiling shamu and I'll push to gerrit for review.

And upload shamu/ hammerhead builds, of course.

JP.

EDIT :

Hammerhead download link

Shamu download link

EDIT :

Gerrit patches :

[1/2] Settings: Add option for left clock style / position date left-right of clock

[2/2] Frameworks: Add option for left clock style / position date left-right of clock
[Android Builders Collective] Mikulec:
Sligthly offtopic question: Does anyone know what does the option "Apps with usage access" under Security do (especially for Google Play Services)? Does it have anybody enabled?
[Android Builders Collective] Shane_IL:
Long-time lurker here. Running Ezio's build usually. I'm not sure if this has been posted before, I did a quick search and did't see anything.

Basically regarding the lockscreen issue, I have my phone connected to my PC via USB at work, and noticed that many times when I unlock it, the MTP connection is refreshed. Hope this might help find this elusive issue.

Also while I'm posting, thanks to everyone for the hard work.
[Android Builders Collective] colida:
Funny thing....I don't have problems with BT either.
[Android Builders Collective] Yank555:
ROM Update

Mainly again a maintenance update, repo sync'ed last saturday, so it'll include AOSP r9 tag (LMY48I).

It of course also sports my left clock / date position left/right of clock patch.

Note for shamu & hammerhead : This is the very same as the last Test-ROM, so if you're running it, no need to download !

Downloads :

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

JP.

PS: All devices are uploading on both sites still, so it may be another 30-40 minutes until all are up.
[Android Builders Collective] PerfectSlayer:
I even disabled it from trust agents but it didn't reduce the lags :(

I also have different steps of drawing before freezing: drawing only black, drawing only background, drawing background with gray overlay, background + gray overlay + some controls or even background + overlay + hour widget.. =/
[Android Builders Collective] TJKV:
[MENTION=2095315]ezio84[/MENTION]

About your CellularTile commit, secondary button only shows when it is one of the top two toggles right? Those two are WiFi and Bluetooth on Stock, both of which have Secondary Click actions too. Meaning three tiles with Secondary, only two spots. So we have to lose the "show details screen" for one of those tiles

Any way of having three tiles on the top row with secondary clicks? Or instead to automatically switch back the single click action of whichever tile is not on the top row to "show the details screen"?

So that way we do not lose the "show detail screen" of whichever tile becomes the unlucky third one.
[Android Builders Collective] Mikulec:
Yes, I tried that too and it didnt help.
[Android Builders Collective] Yank555:
I tried removed my animated wallpaper in favor of a static background, but it's not really helping, although I think the lag feels shorter. Will keep it a few days to really know if it has an impact.

JP.
[Android Builders Collective] martinoff:
Thanks, that is the zip I'm using

I was wonder if i can build the rom with V4A
[Android Builders Collective] likonvampire:
Hello [MENTION=2033478]Yank555[/MENTION]

Running your latest build on the N5 . I had centered the clock and then i tried changing the date from left to right in the status bar settings. SystemUI stopped errors due to that instantly and upon reboot. Had to flash the ROM again from scratch...

No layers installed..
[Android Builders Collective] Thecrazyskull:
Logcat?
[Android Builders Collective] ezio84:
Thanks for the report, i'll check that situation too :good:

You lucky :p

Yes it'd be nice to have the secondary click for all needed tiles, maybe [MENTION=1228651]fusionjack[/MENTION] can unleash his magic :D
[Android Builders Collective] kantjer:
Can't you disable the enlarged first row? That will give you 3 spots on it.

Sent from my OnePlus One
[Android Builders Collective] ezio84:
Tried now, you loose the secondary click feature for those tiles.
[Android Builders Collective] kantjer:
I was afraid that would be the case. So the issue is not they should be on the first row. You need more rows with only 2 tiles

Sent from my OnePlus One
[Android Builders Collective] ezio84:
Trying now [MENTION=2033478]Yank555[/MENTION] commits on my build, no FC after following your steps.
[Android Builders Collective] likonvampire:
Wish i could pull one out as my I wasn't even able to unlock my phone after reboot due to the infinite systemui error loops
[Android Builders Collective] ezio84:
If you have time to try again, let it FC and grab a logcat ;)

PS: without xposed installed, if you have it.
[Android Builders Collective] likonvampire:
Will do, never been a xposed user myself :)
[Android Builders Collective] Mikulec:
Regarding the lags:

Do you guy who get the lags use the option to show "Network activity arrows" on status bar? I have disabled it (for science) and the number of lags I get has significantly lowered.
[Android Builders Collective] ezio84:
I've removed them in my last test build (also because we have the advanced network monitor setting) and no luck.
[Android Builders Collective] Yank555:
You can connect it to a pc and 'adb logcat', that will be most helpful.

I tested in many combinations, had no issue so far (have it left with date right atm)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] Mikulec:
Looks like you are still one step ahead of me.

EDIT: it feels like it lowered the number of lags, at least for me.
[Android Builders Collective] PerfectSlayer:
I always use a fix backgound and I also experience lag.

Yes I enable it.
[Android Builders Collective] Mikulec:
Try to turn it off and see if you get less lags.
[Android Builders Collective] Yank555:
I've had them in since I build and always on and set to refresh every 500ms.

Given the code is the very same since the beginning, I've never considered it a suspect.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] Mikulec:
Might be just a placebo effect. :(
[Android Builders Collective] Yank555:
I have better and worse moments, even when I don't change anything on my device, which makes this hell to chase.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1c kernel.
[Android Builders Collective] reS28raM:
I started writing an HOWTO on it for the thread some days ago, then I had the insane idea to refresh the code on my github to publish the actual code then wtf my repo got corrupted on PC and code was deleted from github. If you keep an eye on my gh in the next days I'll push the whole code with all needed commits. Hopefully lol. [emoji6]
[Android Builders Collective] likonvampire:
Just to report I have been running twisted beta build which is slim based , no lockscreen lag as yet.
[Android Builders Collective] fraz14:
[MENTION=2033478]Yank555[/MENTION] - clock and date works fine :good: thanks
[Android Builders Collective] mslatter:
LG G3 D850 update - repo last night.

Clock placement Left / Right / Center (Thanks again JP!)

CM Navigation Ring Targets (JP)

RRO layers (Ezio84)

Add alternate WebView provider package

SlimHeadsUp: Add a global 3-way switch

Flip to Mute (enable in call settings)

Accidental Wake up OFF by default

Latest Kernel, G3 and D850 commits from arcardinal

1. Full Wipe (am told dirty flash works)

2. Flash Rom

3. Flash Gapps (I used Slim's gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu

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

MD5: ef58d6766989a949761fcdea061de764

Changelog is all new merges since last build from this link:

https://review.slimroms.eu/#/q/status:merged

Huge thanks as always to the following for making all this possible:

Slim Team - for a great ROM

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!
[Android Builders Collective] reS28raM:
[MENTION=2143933]martinoff[/MENTION]

ViperFX code is fully pushed (I think), here are the passages:

[1] - Fork/Pull the viper4android_fx module. If you prefer to fork the original thereafter apply the commit on my repo. The important thing is to place it at 'packages/apps/ViPER4Android'.

<project path="packages/apps/ViPER4Android" name="reS28raM/viper4android_fx" remote="github" revision="cm-12.1" />

[2] - Browse all modules in my repos and cherry-pick any commits that contains 'ViPER4Android'. Double-check if you need or not this one on Slim (it doesn't hurt if you miss it anyway): https://github.com/reS28raM/android_vendor_cm/commit/64e257bb6816f4179a50e0891161f36a1c90b0c0

[3] - Cherry-pick device_lge_hammerhead to the device(s) you're building for

[4] - Warn users they must install the driver after a clean flash, no actions required on subsequents dirty flashes though.

I prefer to leave to the user which driver to install. Please let me know if I forgot anything
[Android Builders Collective] Yank555:
SHAMU TEST ROM Update

Could those running into the lockscreen lag please run this build, and NOT change the kernel, and report back if the still run into those lags ?

Run the build at least for 12h+ uptime to validate...

Download Link

JP.
[Android Builders Collective] Mikulec:
No love for hammerhead? Did you find out the culprit?
[Android Builders Collective] Yank555:
No time for more than 1 build, was at work ...

Although not certain, it's been a lot better, but there still is a slight hesitation.

Hammerhead will come soon to test.

JP.
[Android Builders Collective] Garrykd:
Have any of you guys experiencing lags tried a clean build with just gapps and no user apps? Just for testing?

Like I said before, I don't have any lags, no matter the build. I don't think it's in the rom, I think it is app/user settings related.
[Android Builders Collective] Yank555:
I do agree on that.

What bugs me, though, is that I haven't changed the apps I use, and it started happening, so I do think at some point the apps are the trigger, but that cause has to be in the ROM...

Testing clean empty builds is certainly a good idea. My HH is mostly clean, and even with 3-4 days uptime, I NEVER had any lag, and on shamu with all my apps I do (talking lockscreen lag only).

JP.
[Android Builders Collective] ezio84:
The lag could be triggered by an app, but my old build (05 July) hasn't it so it should be something in the code :(
[Android Builders Collective] kantjer:
That lag thing is keeping you guys busy

Sent from my OnePlus One
[Android Builders Collective] ezio84:
I'm near to throw the phone out of the window, lol.
[Android Builders Collective] kantjer:
That would definitely fix it [emoji33]

Sent from my OnePlus One
[Android Builders Collective] ezio84:
Indeed :D
[Android Builders Collective] Mikulec:
I was thinking the same this morning.
[Android Builders Collective] Thecrazyskull:
I just discovered something...

When the lockscreen starts to lag keep trying to interact with it (touch it pull things up/down like statusbar etc.) and then sysui should fc (happened with me at least and i can easily reproduce it if i get the lag)

I dont have a pc next to me so cant take a log now but if someone has the opertunity do try and post the log here, hopefully something interesting will come up :)
[Android Builders Collective] ezio84:
Good catch! Right now this trolling son of a +++++ isn't lagging, I hope to be able to make a logcat of the fc asap.
[Android Builders Collective] Thecrazyskull:
I just got my hands on a laptop and now it doesnt lag lol
[Android Builders Collective] Yank555:
It's hiding, it knows you're coming for it :D

JP.
[Android Builders Collective] JaylanPHNX:
I'm so glad this isn't happening on the bacon. [emoji56]

From my SlimTab Pro 8.4
[Android Builders Collective] Yank555:
HAMMERHEAD TEST BUILD

This is for those gettings bootloops with my kernel, this is 100% the same as the current build, but the kernel is now built inline (with the ROM).

Can you please test it and let me know if you still run into the bootloops ? Thanx !

Download Link

JP.

PS: [MENTION=653788]Mikulec[/MENTION] : I'll try to make another one tonight with what I hope will help (not necessarily solve) the lockscreen lags.
[Android Builders Collective] ca110475:
Thanks a lot JP, will test it tomorrow and post my findings here [emoji106]

Tapatalked via Nexus 5
[Android Builders Collective] Mikulec:
No need to hurry my friend. You know how its said: Good things come to those who wait (or something like that).
[Android Builders Collective] Yank555:
Kernel is updated to the latest m-preview ... compiling right now ...

I'll give it a quite test while uploading it for you to test ;)

JP.

---------- Post added 12th August 2015 at 12:19 AM ---------- Previous post was 11th August 2015 at 11:33 PM ----------

Here is the ROM with the kernel updated to latest m-preview sources (Hammerhead) :

Download Link

Let's see how this behaves with the lockscreen lags...

JP.
[Android Builders Collective] likonvampire:
Downloading it now and will let you know if I can boot straight from your build.

Edit : Not able to boot had to flash a custom kernel . Also I cannot get data on my device . Have selected my correct APN and BTW this was a clean flash three times just to be sure enough ...
[Android Builders Collective] Yank555:
OK, that is very unlogical...

The ROM is 100% identical to the last build (not a single line of code changed) !?

Plus the kernel is not involved in data, that's ROM - RIL - Radio, and if you used a different kernel (to make it boot), absolutely ALL the changes I applied are gone and you have the very same setup as with my last "public" ROM and the kernel you use.

Doesn't make much sense to me :( Or you should have the very same problem with my latest "public" ROM, then it'd be in Slim base and it came in with latest repo sync on Aug. 8th. But then again, I have not seen changes to the vendor or device repo of HH and shamu radio is working fine.

Also, this means I quit with trying to understand why some have reboots and most don't, since I can't reproduce it, it's chasing a ghost :crying:

Especially, that my kernel is purely based on AOSP, so I don't really understand why it would not boot on all HHs...

JP.

EDIT : Are you certain the APN is 100% correct and that you only have that single one in your list. I saw quite an update in the APNs config xml between my last 2 repo sync's.
[Android Builders Collective] Mikulec:
[MENTION=4863880]likonvampire[/MENTION] - no problems with data on the Yanks test build

[MENTION=2033478]Yank555[/MENTION] - the little thing that should helps us in fight against the lags is in the rom or kernel? Cause I am not able to run your rom with the inbuild kernel.
[Android Builders Collective] VictorLapin:
[MENTION=2033478]Yank555[/MENTION] flashed your latest HH build. No lags, no problems, no bootloops.
[Android Builders Collective] Yank555:
Kernel unfortunately, but it did not fix it, just made it a lot more bearable. I suspect it's the delay for wakeupreason that has been shortened that helps, though I can't be 100% certain.

That would be this commit for HH : https://android.googlesource.com/kernel/msm/+/0bc36ff95a876feaca22bc124695300416d1a929^!/

(the very same is there for shamu, that's where I see a difference, as I have no lag whatsoever on my HH, no matter what uptime, but it's pretty much a clean install, only 2-3 apps installed)

But to add that, you need to have a kernel that's base on / updated to m-preview, not LP mr1.

JP.

EDIT : [MENTION=653788]Mikulec[/MENTION]

Can you describe in detail what happens if you boot the ROM with the bultin kernel ? Like up to where it will go, how long before it reboots etc ? It really does bug me some are having these issues...
[Android Builders Collective] Mikulec:
It goes past the boot screen to the "Optimizing apps" and there after few apps it just reboots and starts again. Do you have the last kernel as a separate flashable zip? I might try to flash it now.
[Android Builders Collective] ca110475:
Ciao JP,

tested it from a clean wipe, and ARGH boot loop again, same as before.

With another kernel everything is fine (no data / radio issue as reported by previous user).

This is a fuxxing enigma, really.

I'm not a coder and i do not have coding skilIs.

But i've been working for a decade and half into advanced troubleshooting (for Sun Microsystems first, Oracle now),

and cannot make myself a clue of what could be the trigger here.

Thanks for the attempt anyway.
[Android Builders Collective] VictorLapin:
[MENTION=653788]Mikulec[/MENTION] do you use layers?
[Android Builders Collective] Mikulec:
no, I think I dont even have the app installed now on Yanks build. Why?
[Android Builders Collective] Yank555:
If it goes that far, adb logcat from PC via usb should work already, could you give that a shot ?

If you want to test flashing it standalone, you just use my flasher zip and replace the boot.img with the one in the ROM zip, I'm mobile atm, but can upload it later or tonight.

And / or grab via adb shell this file : /sys/fs/pstore/console-ramoops

That's the new location of /proc/last_kmsg.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2 kernel.
[Android Builders Collective] Mikulec:
Will try when I get home. Regarding the kernel, I already have that prepared but I was not sure if it is possible to change just the boot.img without other changes.
[Android Builders Collective] Yank555:
That's all there is, if you want to go down the easy way, just use "flash kernel only" in the beginning in Aroma Installer, it won't touch / overwrite the kernel config.

But I'll make an updated kernel flasher tonight (if I don't forget at my higher age :cowboy:).

JP.