yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Mikulec:
[MENTION=2033478]Yank555[/MENTION] - kernel flashed without problems, altough I have tweaked some of the settings in the installer (max frequency to stock, stock usb charging and I have lower the max screen off freq)
[Android Builders Collective] Yank555:
Kay, I was too slow :D

EDIT : And the ROM is running fine now ? Hmm ... interesting !

JP.

PS: Default CPU max in ROM is stock :

https://bitbucket.org/yank555-lu/sl...93f6dd3297a4012#Linit.yank555.lu.kernel.shT63
[Android Builders Collective] VictorLapin:
Thought about lockscreen lags.
[Android Builders Collective] Mikulec:
yes, running good so far. The default value in the installer was 2,5Ghz so I changed it to the stock one.

If I had a layer, that would be the first thing I would disable/uninstall.
[Android Builders Collective] likonvampire:
Sorry seems like i am the only one getting so many problems. do not want to come across as someone who is always whining and complaining .

I will try to do a factory reset later today if that helps with the data issue ..
[Android Builders Collective] Yank555:
No problem, don't worry. I most definately want to get behind this, just not easy from where I stand ;)

I've written down a few things to check as soon as get to it, hopefully that will help me solve that reboot issue eventually.

JP.
[Android Builders Collective] Mikulec:
last_kmsg and logcat (I had no idea where the logcat got saved so I just copied the last rows to a text file :silly: ) in the zip.
[Android Builders Collective] PerfectSlayer:
Yes I pointed here: http://xdaforums.com/showpost.php?p=62193200&postcount=7104

There is an ANR (Application Not Responding) in SystemUI in logcat if you stack too much input :(
[Android Builders Collective] Yank555:
Standalone Yank555.lu Kernel for Shamu and Hammerhead

In case you want to flash my latest kernels (both built inline now) for shamu and hammerhead, here are the direct download links :

Shamu : Yank555.lu-N6-SlimLP-5.1-v1.2.zip ------------> Changelog

Hammerhead : Yank555.lu-N5-SlimLP-5.1-v1.4.zip ------------> Changelog

Note : these are the latest kernels, compiled last night (one before the other after midnight :D)

JP.

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

I saw it ... any idea how I could manage to reproduce that ? I get a mere split-second hesitation only.

JP.
[Android Builders Collective] PerfectSlayer:
When the lockscreen takes seconds to draw, simply repeatedly tap on the screen to make input.

If your lockscreen doesn't lag, no chance to reproduce it. May be I keep the logcat if you would like I look for it ;)
[Android Builders Collective] morfances:
Your kernel Support multirom,s2s,s2w,d2w?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] Yank555:
Thanks for that !

This at least shows the kernel log just stops, that's a clean "random reboot".

I suspect that heat could be the issue and I wonder if thermal-engine maybe isn't started on HH on boot as maybe stock HH kernel has in-kernel thermal management.

My kernel has, too, but it's disabled by default as I like my kernel to behave as stock as possible unless told otherwise (hence my kernel config script), which would stop thermal-engine to enable intelli-themal_v2, but this happens only AFTER boot complete, which is after optimising the apps.

Since optimising the apps is very CPU intensive, and if no thermal management is active at that moment (intelli-thermal_v2 is enabled only after), this will potentially lead to a reboot to protect the hardware (no kernel panic, just plain "pull the plug", as the log shows).

I'll investigate this, and if that's the case, this could be a thing of the past.

I'd have another "wish" while I look on my end, could you reboot into recovery, wipe dalvik and reboot ... BUT put your device in the fridge a few minutes before doing that, and keep it in the fridge while doing recovery stuff and during first boot.

If that succeeds, you'd confirm my theory.

This could also explain why it's not happening to everyone, we're not all in the same location (ambient temp) and not all devices are equal in brute thermal resistance (w/o management), my N5 has proven an excellent candidate.

Why this wouldn't happen on other kernels, esp. if the keep the ramfs is a good question, maybe they also have in-kernel thermal management enabled by default, or use a different governor on boot keeping the CPUs a tad cooler or or or ... ??

JP.

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

Very much would like to :D

JP.

---------- Post added at 08:24 PM ---------- Previous post was at 08:24 PM ----------

multirom : no

s2s, s2w, d2w : hammerhead no, shamu only dt2w (stock)

NB: And no plan to change this.

JP.
[Android Builders Collective] PerfectSlayer:
I send you throw email the full logcat (the mail from Slim builder section in your rom settings ^^')
[Android Builders Collective] likonvampire:
[MENTION=2033478]Yank555[/MENTION]

Just wanted to report no data again , this time i did full factory flash using fastboot commands , backed up stock in twrp , redownloaded the rom and gapps and flashed.

No data again on boot .

P.S : Had to flash a custom kernel to get rid of bootloops.

I totally agree with your idea of cpu intensive tasks running the devices too hot and into bootloops. I have the same bootloops as the other user in which the device bootloops while optimizing apps.
[Android Builders Collective] Yank555:
Perfect, saw it, thanx ;)

--------------

@Mikulec and others running into reboots on first boot :

And we boot without thermal engine, it's "disabled" !!!

Let me try to get that fixed and make a testbuild !

JP.

---------- Post added at 08:47 PM ---------- Previous post was at 08:42 PM ----------

Here is the root of all evil :cowboy:

https://github.com/TheLoonyBin/proprietary_vendor_qcom/blob/lp5.1/hammerhead/device-partial.mk#L33

vendor/qcom/hammerhead/proprietary/thermal-engine-hh:system/bin/thermal-engine-hh[B][U][COLOR="Red"]_disabled[/COLOR][/U][/B]:qcom \

Well maybe not of all evil, but to me right now it certainly is !! :D

JP.

PS: mpdecision is also disabled this way.
[Android Builders Collective] Mikulec:
Well guess what. This exactly was my first guess after I started investigating the bootloops. And what was the first thing that came to my mind? Put it in the fringe. :D lol In the fringe it came further (cca 90 apps optimised) but after that reboot again.

This theory mind be right, cause I was able to flash your kernel after the apps were optimised.
[Android Builders Collective] Thecrazyskull:
Oh, sorry i must have missed your post.

Anyways are you able to get a log? If yes please get one and attach it here, would be appriciated :)

---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------

Mind posting the log here or sending it to me via pm? ;)
[Android Builders Collective] stebu79:
Another observation which would support your theory :I have always the reboot issue with your rom, but one time I flashed your build, as usual elemantalx kernel (otherwise it wouldn't boot) and after initial boot I flashed your kernel and it went all well...
[Android Builders Collective] Yank555:
OK, not certain I caught everything, but could those having reboots (@Mikulec) try this one :

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

And report back ?

Thanx, JP.
[Android Builders Collective] Minux31:
Hi there, back from holidays, and ready to build :D

Just a question : on my last builds for d855, Google play services always FC (even on clean install, during first wizard), any idea of what I have to do to correct this ? I've search, but found nothing interesting ...

Thank in advance :)
[Android Builders Collective] pkelly517:
Shoot!

I thought I made it clear weeks ago when I said I had to put my HH in the freezer to complete optimizing apps.

The first HH I got from Google was terrible at this. Then again, it may have been the kernel. ANY installation of of a ROM would give the same results. Reboot during app optimization. Put it in the freezer, cache rebuild completes. They sent me another (I love Google's support). It hasn't happened again until your recent builds. I put out a message that I put it in the freezer to get the optimization process to complete.

Put in a 60 C thermal limit, and you should be butter. It may take an hour.... :)
[Android Builders Collective] Mikulec:
Downloading, will report when I get to work and flash this sucker. :)
[Android Builders Collective] stebu79:
Didn't work for me though, had to flash elementalx again to get through the boot process. Went into bootloop even before optimizing the apps....
[Android Builders Collective] Yank555:
Kay, then I have no other resort than to activate in-kernel thermal management right on boot, will do this tonight and push another testbuild ... pfff ... we'll get there eventually ! ;)

Thanx for the feedback !

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2 kernel.
[Android Builders Collective] Mikulec:
[MENTION=2033478]Yank555[/MENTION]

OK, here my progress. I have 166 apps to optimize, the rom booted fine, started to optimize the apps:

Optimized 107 apps - reboot - here instead of starting from scratch it continued where it left, optimized 25 apps - reboot - optimized 0 apps - reboot - here I have put the phone on our airconditioning - reboot - and after that it optimized the rest of the apps - booted to the rom - before I was able to touch the phone another reboot. Now I am playing with it little bit, deleting some system apps and it looks like it working.

Soooo, weird behavior. But it finaly booted. :p
[Android Builders Collective] Laggalot:
Is there a way to disable the fullscreen keyboard in landscape mode ? I used to have it before I clean flashed.

edit: nvm Its in the AOSP keyboard settings! found it by myself :D
[Android Builders Collective] diegocr:
Samsung Galaxy tab S T800 chagallwifi, T700 klimtwifi & OnePlus One bacon update.

Latest slim & ezio updates

Update manifest to android-5.1.1_r10

Add option for left clock style / position date left-right of clock

................................... see changelog
[Android Builders Collective] PerfectSlayer:
[MENTION=2033478]Yank555[/MENTION] It still trying your 20150811-1245 test build. I'm facing lockscreen lag mainly due to camera. I saved all logcats for you and I will post it tonight when I get home.

I will post here too so. Just left me time to get home to clean logs before posting ;)
[Android Builders Collective] TJKV:
That makes lockscreen lags sound....pleasant. O.O

Also [MENTION=2095315]ezio84[/MENTION], I spy fix :D
[Android Builders Collective] Yank555:
Kay ... once it's booted, you're good, cause the kernel config will enable proper thermal management in the kernel.

I will change the ramfs to do this early at boot and be done with it ;)

Now I know the problem, I should get past it.

But this means that stock thermal management (on which my kernel relies during boot) is broken on HH :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2 kernel.
[Android Builders Collective] PerfectSlayer:
Ok guys. Here are the logcats you request about lockscreen lags.

Three for today with camera / faceunlock issues, ANR in SystemUI, etc… and an old one (one week ago that the [MENTION=5083850]Thecrazyskull[/MENTION] want).

I hope you could exploit it [MENTION=2033478]Yank555[/MENTION] :)
[Android Builders Collective] Thecrazyskull:
Well, yank send me the log already and it looks like we have fixed freezes at least they are fixed on my side and [MENTION=2033478]Yank555[/MENTION] said that it looks good for him :) still waiting for [MENTION=2095315]ezio84[/MENTION] to confirm before saying its fixed completely ;)

EDIT: Not fixed :( ezio reported lag and yank too seem still fine on my end though.
[Android Builders Collective] Mikulec:
Which freezes?
[Android Builders Collective] Thecrazyskull:
Lockscreen
[Android Builders Collective] Mikulec:
Whaaaaaaaaaaaat????? GIVE IT HERE, NOOOOOOOOOOOOOOOOOOOOOOWWWWWWWWWWWWWWW.

EDIT: just read your edit, this sucks. :(
[Android Builders Collective] Yank555:
NEW HAMMERHEAD KERNEL REBOOT TESTBUILD

Well, on the bright side ... if we still haven't nailed those damn lockscreen lags, I think I should have nailed the reboot with my kernel thing !

So to all "rebooters", could you give this one a testride ?

ROM and kernel are unchanged, only ramfs changed to start in-kernel hotplugging and thermal management right away on boot.

Stability test running for over 20 minutes now (with config script removed, so with on-boot settings).

Yesterday I managed to get mine to reboot on stock hotplug/thermal with stability test after about 5 minutes...

Download Link for ROM

Download Link for standalone kernel

Thanx for your feedback ! If this works, I'll update the standalone kernel as well.

JP.
[Android Builders Collective] likonvampire:
What about the no data issues [MENTION=2033478]Yank555[/MENTION] ? :)
[Android Builders Collective] Mikulec:
I confirm, the reboots are a history. :good: Now to the lockscreen lags. :p
[Android Builders Collective] Yank555:
Can only be an APN thing, it works and as I said, 0 lines of code changed in ROM :(

Check that you only have one APN in the list and check it's 100% correct (all the details, not just the name).

Last repo sync brought a sh*tload of changes to the APN list if I saw correctly, maybe your's got derped ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2 kernel.
[Android Builders Collective] efan3719:
Quick build for Hammerhead and Flo. Sync'd up with Slim as of like an hour ago. Has some more stagefright fixes recently pushed. Links in my sig or post 8 of this thread. and for now i'm just using Dev Host.
[Android Builders Collective] ca110475:
[MENTION=2033478]Yank555[/MENTION]

Hi JP, confirming the bootloop is gone even in this fuxxing hot and humid Milan.

Great work on the bootloop issues, now testing your kernel finally :)

Cheers

Cristian
[Android Builders Collective] Yank555:
Thanx for lifting that weight off of me !! ;)

If that hadn't worked, then I'd have had to throw the towel and accept it, and I really would have hated that :D

JP.
[Android Builders Collective] kantjer:
I need some help here, when I add mediaserver.te \ to sepolicy.mk my build fails with secpolicy errors.

Without the commit the build is OK but I can't install the v4a driver on a clean flash. Any tips?

http://hastebin.com/ineyisoguq.avrasm

NVM: found the issue
[Android Builders Collective] likonvampire:
[MENTION=2033478]Yank555[/MENTION] .. OK so finally up and running on your build. No boot loops with the kernel changes. As far as the data issues , I had to define MVNO value in my APN to get data up and running . Never had to define MVNO ever and none were required on many other ROMs/stock .
[Android Builders Collective] Yank555:
Glad that kernel issue (which wasn't a kernel issue, but a vendor repo issue, but nevermind, it's finally solved ;)) is gone ;)

Can you post (or PM) the full APN detail (screenshot), so I can fix it in the APN-file and push it through gerrit to fix that ? Must have been a derp with the recent changes in Slim.

JP.
[Android Builders Collective] likonvampire:
This is first time MVNO definition was required although I am not on a MVNO .

Attached are APN screenshots and also the APN details recommended by the my carrier
[Android Builders Collective] Yank555:
Quick look in the repos, here is the current APN default for your network in slim :

https://github.com/SlimRoms/vendor_slim/blob/lp5.1/prebuilt/common/etc/apns-conf.xml#L1394

Will have to check if all the details are correct.

JP.

EDIT: mvno stuff is missing...

Maybe a recent change on their end ?

Here latest change for your network : https://github.com/SlimRoms/vendor_slim/commit/b2dfbba23d9e467df720b94b642a6c4e42f1d2e4

14 days ago, so new in my last repo sync.
[Android Builders Collective] likonvampire:
Hmm interesting , never had to setup MVNO settings while on any other ROM and the APN's look exactly the same..
[Android Builders Collective] PerfectSlayer:
[MENTION=2033478]Yank555[/MENTION] At each time I have a big lock screen lag, I notice huge load from several kworkers (about 5) which take almost 100% of load (in kernel)

Do you have any idea of what it is?
[Android Builders Collective] reS28raM:
Glad you sorted it out. :D

It seems to me the old commit which enabled AwesomePlayer in lieu of NuPlayer in Developer Settings is still necessary despite the fact Google says that option is obsolete so I'll add that one too. Jush hoping Google is not going to remove AwesomePlayer in a near future. [emoji33]
[Android Builders Collective] :
Jay I feel useful again :D

Too much work lately, way too much :( Not enough time to spend here or build
[Android Builders Collective] Yank555:
kworker is a generic name ... could be anything.

JP.
[Android Builders Collective] likonvampire:
[MENTION=2033478]Yank555[/MENTION] to add to this , I am running stock M preview 2 right now. No MVNO definition required to get data working and it has been working perfect since the first boot..

That tells me there have been no APN changes from the carrier end..
[Android Builders Collective] Yank555:
No idea what could be a cause here... how many APN are in your list ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2 kernel.
[Android Builders Collective] PerfectSlayer:
I read it too. But as you made the kernel, I wonder if you already what it could be.

Do you think it could be usefull to dig into ANR traces or CPU backtrace using SysRq?
[Android Builders Collective] likonvampire:
Only one in the list
[Android Builders Collective] Garrykd:
Hey there :),

Latest new builds up. Synced with Slim source beta 0.5. As usual, mostly stock with Layers and a few additions.

http://xdaforums.com/showpost.php?p=55121772&postcount=5

https://s.basketbuild.com/devs/garrykd/Builds/

Still no lags ;) :angel: :p
[Android Builders Collective] reS28raM:
https://github.com/reS28raM/android...mmit/71076824f87bc42c4436c2a97e3eb184a92085ed :D

Not yet tested though, I will after adding Proximity Speaker to the build
[Android Builders Collective] acultr:
ezio84? ?
[Android Builders Collective] Yank555:
Might be worth it, nothing I've done yet, though ;)

JP.
[Android Builders Collective] AirOne70:
Hi everyone !

As builder of Ezio's ROM, today, I need your help..

Since few days, I can't repo sync without that error:

It happens after few seconds, and I can't see how to fix it..

I tried to use "--force-sync" but now, I have more problems:

(and I still can't repo sync)

Is there anyone who can help me, please ? :crying:
[Android Builders Collective] theesotericone:
Google derped repo about a week ago. What a lot of us have to do to sync now is:

repo sync --force-sync

Hopefully they get it back to normal soon enough.:cool:
[Android Builders Collective] ezio84:
Incoming :D (but sometimes still lockscreen lags on my side)

2 ways:

- [MENTION=5451511]theesotericone[/MENTION] 's one

- go into the hidden ".repo" folder, then delete the "repo" subfolder, then run "repo init", then run "repo sync" again and it should work without fetch errors.

PS: local manifest updated right now.
[Android Builders Collective] AirOne70:
Both are working great, thanks ! But then, what can I do about this:

I need to fix this for every repo.. :rolleyes:
[Android Builders Collective] ezio84:
It means you don't have a local lp5.1 branch. So you need the -b flag:

git checkout -b lp5.1

It'll create a new local lp5.1 branch synced with the detached one if you are on it now.
[Android Builders Collective] fusionjack:
[MENTION=2033478]Yank555[/MENTION], concerning https://review.slimroms.eu/#/c/6555/, the changes in slim_array.xml should be redundant right? no where is using it...

edit: wrong alarm, it is used from frameworks/base :p
[Android Builders Collective] AirOne70:
It works, thanks Ezio ! :highfive:
[Android Builders Collective] mistersixt:
Hi Garrykd,

I am using your builds since a while and had no lags whatsoever. Today I did a dirty flash coming from 0.4 (20150812) to 0.5 (20150815) ... and I suddenly had a 2 to 3 seconds lag during the unlock of the screen. So I thought: damn, you have that thing in your ROM, too, now. I then simply flashed your 0.5 ROM again over 0.5, from TWRP, and guess what: it is working like expected again.

Very odd, I know.

Regards, mistersixt.
[Android Builders Collective] Yank555:
ROM Update

Please note that Multi-ROM is

not supported

, although it's in my shamu and hammerhead kernels !

If you run into issues do only report them if you can reproduce them

without the use of Multi-ROM

!​

Not many feature changes, again some stuff went into Slim base, there's been a few changed to the kernel (in the way it boots,

fixes the bootloop some were having on hammerhead, this was due to disabled mpdecision/thermal-engine in vendor repo).

Most visible change (shamu only !), though, is that dt2w is now a simple switch in display settings, so feel free to set it to whatever you like.

(Note this will only work with my kernel, other kernels would need to add a tiny patch to be compatible).

Oh yes ... we're at beta 0.5 now ;)

Changelog :

- Repo sync 20150816-1215 CET

- fixed left clock FC when using small font am/pm and small font date (Yank555.lu)

- (shamu only) add option in display settings to enable/disable dt2w (CM / Yank555.lu)

- (hammerhead only) build Yank555.lu kernel inline (Yank555.lu)

- (shamu and hammerhead only) use in-kernel hotplugging/thermal on boot / disabled mpdecision & thermal-engine (Yank555.lu)

- (shamu and hammerhead only) add kexec to kernel - support for Multi-ROM (Yank555.lu)

Download Link on my BC OP - post 14

JP.

PS: Shamu, hammerhead, flounder & flo are up on both servers.