yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
The same with GCam (Arnova's v8.3b1, HDR OFF + FLASH ON), did you look at the black screen problems on the troubleshoots 3rd posts on this topic ?

https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552

Recent versions no longer need a fix for the black screen viewer, if that's your problem or are the images really black after transfer on computer too?.
[OnePlus 3 & 3T Cross Device Development] Dirk:
No, it was never an issue with the viewer. The pictures i added on Jira tell the whole story:

https://jira.lineageos.org/browse/BUGBASH-2032
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
Ok thanks I better understand the problem.

So after retrying on a full dark room :

Snap : OK (maybe a little bit dark but okay to me)

GMod : Nok, pictures are all black, I see nothing on it
[OnePlus 3 & 3T Cross Device Development] Dirk:
interesting. Thanks for testing.

So that information, together with the Caesium report, suggests that:

i) Stock Kernel + Snap is currently a working configuration.

ii) Caesium Kernel + Snap is not working

iii) Stock Kernel + GCam is not working
[OnePlus 3 & 3T Cross Device Development] S4turno:
Flash only works on the modded Google Camera if HDR+ is enabled. It's an old issue but no one talks about it anymore because the main reason to use the port is... Google's HDR. Without it, it's just another camera app with subpar quality.

It's not a LOS issue as the same thing happens on OOS.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Yeah, we know. The aim of the exercise is to have the bug fixed so you can use flash without HDR enabled, or with apps that don't have a HDR mode. It is a LOS bug though. Evidenced by the fact that it's only LOS and LOS based ROMs affected. I've never heard of a similar issue on OOS.

https://jira.lineageos.org/browse/BUGBASH-2032

For those who use LOS and wish to use Snap, this will be good news. But if that's the only working configuration, it still kinda sucks for the rest of us!
[OnePlus 3 & 3T Cross Device Development] S4turno:
I was trying to say that the Google Camera mod itself has a bug were flash doesn't work if HDR is disabled.

On my OP3 running OOS 5.0.5: Arnova's v8.3b1 + HDR OFF + flash ON + completely dark room = black picture. The same thing happens on LOS and OmniROM.

Basically, if you guys want to test this with 3rd party camera apps, you'll have to use a different app (e.g.: Open Camera?) because the GCam port itself is broken.

With this said, I can confirm that Snap + flash works with the stock kernel, but fails (dark picture) if I install Caesium kernel.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
So not everyone is experiencing the same lag and hang problems? I thought everyone had this problem. I suspect maybe it could have to do with encryption. I did a clean flash 2 or 3 builds ago. Oos 5.0.5 firmware, twrp 3.2.3, and whatever opengapps the latest at the time.
[OnePlus 3 & 3T Cross Device Development] S4turno:
My OP3 started lagging after flashing last week's (20180904) build. Animations and scrolling were choppy and not as smooth as before. Then I flashed OOS 5.0.5 to do some Camera testing and when I was done, instead of restoring my old LOS backup, I did a full clean install (erased userdata, which removes the encryption) and had no issues since then.

No idea if what I was experiencing is the same thing you and others reported here, but a clean install did fixed it for me.
[OnePlus 3 & 3T Cross Device Development] okaysee:
We're supposed to be using 5.0.5 firmware? I've been using OB30 the whole time lol
[OnePlus 3 & 3T Cross Device Development] S4turno:
I believe LOS is still on 5.0.4, but 5.0.5 works fine.
[OnePlus 3 & 3T Cross Device Development] okaysee:
How can I know for future reference since OP mentions latest OB.
[OnePlus 3 & 3T Cross Device Development] :
I'm on encrypted f2fs and try really hard for two weeks to reproduce the issue without success. So I'm pretty sure it's not related to encryption.

What do you mean by erased data? If you wipe data encryption persists - if you format data encryption is removed until you encrypt it again from within the rom. Do you refer to "wipe" or "format", when writing "erased"?
[OnePlus 3 & 3T Cross Device Development] S4turno:
"fastboot erase userdata" or TWRP > Wipe > Format Data.

That's what I meant/did.

To be honest I don't know if it's related to encryption or not. counterfeit187 mentioned it and in my case the lag disappeared after a clean install that involved encrypting everything again, but it could be something else.

Edit:

Ps: I was/am on EXT4, not f2fs.
[OnePlus 3 & 3T Cross Device Development] :
ext4 should be even less prune to issues then f2fs (I'm using f2fs not because I belive it's suirior in any regard, but to catch issues - since f2fs is surely more prune to strange issues). Maybe (and I have no clue how to test or proof that, other then formating and redoing the encryption) it depends on with wich rom the encryption is done.

I.e.: if the encryption was done with oos 3.x it will generate lagging with lineage-15.1 - if the encryption was done with lineage-15.1 everything is fine (the versions here are just an example!!!).

A memory leak was also mentioned (and it has seemed plausible to me). From the information in https://jira.lineageos.org/browse/BUGBASH-2258 we can see, it's not a mem leak.

Also: I don't see a trace of heavy io waits (which should be there, if the lags relate to encrypted mass storage). That's one of the reasons, why I've asked for waiting 3 or 4 cycles before capturing top's data (on "top -n1" the startup of top is mainly measured - and if the top's binaries and libs are cached the lagging causing io waits wouldn't show up).

May I ask you to add your observation (lagging gone after format and redoing the encryption from within lineage-15.1) to the bugbash? Thanx.

DISCLAIMER: formating data without redoing the encryption with unlocked bootloader and twrp installed is an easy to avoid security hatzard!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Hot off topic tip of the day:

Just got the Chrome 69 Desktop UI refresh and it's utterly revolting. To revert to previous UI go to "chrome://flags/#top-chrome-md" and set to 'Normal'.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
If someone interesting, I tell you my adventures with lux sensor, the way it was messing around with the auto brightness.

On nlos I was using f2fs for /system and /data. Formatted as usual with factory reset and installed full 505 stock rom. Bootlooped. Thinking what the hell, no errors were while installing. Reformatted system and data with ext4. Booted properly. All sensors are fine, autobrightness works as bee in summer.

Then, installed freshly nlos with same ext4. Autobrightness solid as rock, works as it should be. Restored backups from twrp (system and data) - Bootlooped again :) so guessing some errors came to life because different file systems was used.

Reformatted again as ext4, installed nlos once again, without any restores. Half of the day - all fine, except that proximity sensor, still, on fresh installation and on ext4- active for 5hrs. So, guessing, its Los related.

---------- Post added at 07:17 PM ---------- Previous post was at 07:13 PM ----------

Still waiting for dark mode. Will that happen someday with highly trained monkeys? ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Android? They'll probably add it for five minutes and then remove it again. :p

Considering their recent UI decisions, i think they'd get better results if they replaced their code monkeys with actual monkeys.
[OnePlus 3 & 3T Cross Device Development] :
I see your point, but your guess on the reason would mean everybody running los would have an amoking proximity sensor. Which is not the case, isn't it?

BTW: is autobrightness working for you after clean flashing?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
[ROM][Official][Weekly] LineageOS 15.1 for OnePlus 3/3T

My point about proximity sensor is to ask other people, using los/nlos - is it normal, that proximity sensor is nearly always alive, even if all option coming along are disabled? Does it seen by bbs sensor statistics--running all the time, or max 30min per day (same as calling time) as example?

Yes, thanks, as I have written before, everything is all right, brightness sensor included. Guessing that was f2fs or again, twrp backup/restore error. Fresh installing is time consuming, but works nicely.

Regards.
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
So far so good, build 20180911 is very smooth and responsive after 24h. No Lag/Freeze. No Animation lag too.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
So apple announced new devices. Now will know what to expect from android devices in coming year. And, I must admit, Google still isn't able to compete such miracles, what apple watch is capable with. Maybe next year :)
[OnePlus 3 & 3T Cross Device Development] bassie112:
For me too up till now whereas normally would have massive lag few times a day for many weeks now. Camera (modded Google), Maps, Gboard and/or a bluetooth connected headset seem to trigger the lags most often, but these are also my mostly used apps so not sure if related. However, lag can be removed (temporarly of course) by clearing the running apps right from the default task manager.

I always have everything updated to last versions (LOS, open gapps pico, modem+firmware, TWRP) with wiped cache and dalvik before a flash (not clean flash, no time yet). Now, since the build of yesterday no problems. However, I also switched to Caesium kernel (from stock LOS) so that may also have fixed it... Battery seems also to drain much less for my usage which may have to be related to lag, kernel and/or this week's LOS build.

So for people with similar problems just update everything and additionally also custom kernel. Can't hurt :)

Currently: LOS 20180911, Open Gapps pico 20180911, modem+firmware 5.0.5 stable and kernel Caesium DramaticDate. Still fine after 2 days :)
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
I think I may have talked a little too soon, I had my first lag. So during the lag time I was able to run the top command as requested.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
I'm experiencing the same issues since a few weeks. I'm using MindTheGapps and always the latest available stable firmware (now 5.0.5). My issues do not seems related to Maps as I read in other messages. I installed Franco Kernel mainly for another reason (trying a kernel with a wakelock blocker because of a "video2" wakelock probably caused by Arnova Google camera port) and it did not help for the lagging issue.

I did not wrote a "me too" post before, because I never got something useful to add, until (maybe) today: a few hours ago, I experienced serious lags again, while using Whatsapp, Chrome and Amazon Shopping since maybe 10 minutes (opening a few Amazon links received in Whatsapp).

During the lags I received an unresponsive app warning from Chrome and system UI, I choosed the wait option, then I was able to do a full logcat using the Syslog app, could it be useful?

After the logcat, I was able to open the Systempanel2 app and kill all the processes, and all the lags ceased immediately.

I'm getting similar lags since a few weeks and usually the only option for me is to force a shutdown via power button.

Thank you
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
Thank you for your comment. On which LineageOS build date are you?

I think you should upload it to the bug ticket, it can't hurt : https://jira.lineageos.org/browse/BUGBASH-2258

Some information may be relevant for solving the problem.
[OnePlus 3 & 3T Cross Device Development] :
Lagging

Sidenote #1: I've run out of thanxs - but I appreciate evry usefull information on this ugly lagging issue!

Sidenote #2: I don't think it's maps - at least not alone. But I found maps is a real resource burner! I've never used maps for navigating. I've never used navigation apps in my car without connected to the car dash charger. Until yesterday... If running on battery (no charger attached) maps takes about 18%/h. Navigon (discontinued, but my favorite navigation app) takes only about 11%/h.

[MENTION=2718364]Xzorg6[/MENTION]: thanx for the top-output. firefox is known to put some load on the cpu, but 105% doesn't seem extraordenary. The wait states and both of the irq values catch my eye, though. The cpu is loaded, but not that much, that lagging would be explained, but the 76% iow (other then cpu, which adds up to 400%, iow is max 100%) can make a device laggy: processes have to wait til data is loaded to ram. (@S4turno: now I'm sure the description ofmyour expirience is valuable!)

Considering all this it's possible we encounter some fs issue here, which is triggered by heavy io load generating apps (I would count maps as well as firefox or chrome in this category).

[MENTION=3986617]ciarpame[/MENTION]: all logcats taken while device is lagging are valuable. Please add that to https://jira.lineageos.org/browse/BUGBASH-2258 , together with your expirience with killing apps makes device useable again. May I ask you to try killing apps one by one, to see which app exactly is triggering the lags - if the device is lagging again.

[MENTION=9350973]All[/MENTION] suffering from this lagging:

Currently my best guess is, that something's going wrong on heavy io load with accessing the mass storage. The solution may be formating data and redoing the enfryption from within los. (With current official twrp-3.2.3-0 and 5.0.4 or 5.0.5 fw. If somebody wants to reformat with f2fs [ext4 is highly recommended]: https://xdaforums.com/showpost.php?p=75688089&postcount=4 [replace 3.2.1-0 in the posting with 3.2.3-0 ;) ])

We're getting closer... ;) Again: all logcats and top (wait 3 or 4 refreshes) outputs taken while lagging are worth to add to https://jira.lineageos.org/browse/BUGBASH-2258 !

Thanx to everybody providing information on this!

---------- Post added at 11:40 ---------- Previous post was at 10:53 ----------

...don't ask to get los ported! ;)
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Would you? :)

About mass storage access. With f2fs never had any lags. Maybe read ahead needs to be altered?

Entropy?
[OnePlus 3 & 3T Cross Device Development] :
Lagging

[MENTION=3986617]ciarpame[/MENTION]'s dmesg have traces of a mem leak:

[16306.268236] lowmem_reserve[]: 0 0 0

Does anybody know, how to examine the leaking process(es) only from the logs without checking ps or top? Because I don't.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
lineage-15.1-20180911
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
From my experience, lags always appears while loading heavy app like Firefox/Chrome, Maps/Waze, Games, Taking pictures too.

So I don't think it a specific app issue.

kswapd0 seems to appears on the top during lags and disappears after.

According to some research on Google, there have already been cases in the past on Android and Linux.

Changing kernels has sometimes solved lags, so it seems like a kernel problem.

On the second solution from this post, they suggests to tune kernel parameters :

https://askubuntu.com/questions/259739/kswapd0-is-taking-a-lot-of-cpu

In particular this one (others are already set) currently set to "0" :

# cat /proc/sys/vm/drop_caches
0
# echo 1 > /proc/sys/vm/drop_caches
# cat /proc/sys/vm/drop_caches
1

Could it help to change this setting?

I can do the test to run my phone with this setting some days if it can help :

adb shell su -c "echo 1 > /proc/sys/vm/drop_caches"

As I was at home during my last lag, I made a new top trace (after 48h uptime) I've added to the bugtracker.
[OnePlus 3 & 3T Cross Device Development] felixchris:
Hey guys, I see some bluetooth issues lately here. Did not have any up to the 28.08 build. That was the last I could use, after that broke my phone. Now I have another OP3, flashed the 11.09 build, pico gapps and let google restore from my backup.

Now bluetooth crashes for me when scanning for a new device to pair. Freezes up the whole phone even after a minute or so.

Things i`ve tried: Wipe Cache, Wipe Data of the bluetooth app, reset network settings, Update to the newest build, switch to stock kernel instead of francos.

I can have another try at obtaining a logcat if that is gonna be helpful narrowing down the issue.

EDIT: logcat is here: https://drive.google.com/file/d/130mtLIdiA7itEwzdkw3Igg_44dJ-p_OT/view?usp=sharing

I can provide a log if that helps clarify the issue.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Sometimes backups makes some fun. And that happened to me with twrp backup/restore, titanium backup, Google inbuild backup as well.

Had nearly same fun with restoration from crashed op3t 64GB version to 3t 128GB, a little bit newer one.

Try with clear instalation and afterwards restore all the rest.
[OnePlus 3 & 3T Cross Device Development] felixchris:
Thanks, I might try that tomorrow. My other Oneplus 3 right here with an all clean flash does not have the problem, so its clearly not a bug in the latest build. Its also working flawlessly when booting into safe mode. My some app breaking my BT?!
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Are you on the same hardware firmware on both phones? 5.0.4, 5.0.5 or some older OB firmware?

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] bassie112:
People, I am still without lags now for 2.5 days which I couldn't do for half a day for many weeks. I only changed to the latest weekly build and kernel as I said before. So if people still have lags with the latest build then please flash Caesium DramaticDate for testing. It seems to be kernel related if you ask me.

Currently: LOS 20180911, Open Gapps pico 20180911, modem+firmware 5.0.5 stable and kernel Caesium DramaticDate.
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
Can you check the result of the following command, as you are on custom kernel without bug for now :

adb shell su -c "cat /proc/sys/vm/drop_caches"

Your filesystem is f2fs or ext4 ?

Thanks
[OnePlus 3 & 3T Cross Device Development] bassie112:
Changed to f2fs some time ago, from the partitions I can see data is f2fs, cache ext4, system ext4.

ADB check:

C:\Portable Software\ADB>adb shell su -c "cat /proc/sys/vm/drop_caches"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Just flashed, I will let you know if it works for me, thank you!

EDIT:

About lagging start date: I remember it began just a few days before my vacations in Sardinia (unfortunately I'm not still there...) and, since I was there from August 21, it's likely that 20180814 build can be the first one to have such issue for me.
[OnePlus 3 & 3T Cross Device Development] MagnusT:
Boeffla Kernel has an additional line configured.

CONFIG_MEMCG_SWAP=y

CONFIG_MEMCG_SWAP_ENABLED=y

https://github.com/andip71/boeffla-...mmit/c2313905211540af5a18ae537da838c57a8452bb

I haven't seen the lag problems while using the latest build of Boeffla Kernel either.
[OnePlus 3 & 3T Cross Device Development] :
Not all installations are hit by the lagging. Do you mean you had exzessive lagging with los keenel, and it was gone when using boeffla's? Or do you mean you never suffered from lagging, and after changing to boeffla's the lagging ceased?

The latter would be pointless regarding hunting down the lagging issue.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I'm also with the Boeffla Kernel. I think for 2 months. And I never suffered from lagging.. But I didn't switch to prevent the lagging. But maybe it'll help you a bit, I think also it's a kernel issue
[OnePlus 3 & 3T Cross Device Development] MagnusT:
I've seen severe lag and reboots when using lineageOS builds starting from 2018-08-14. I described this earlier in this thread. The problems wasn't noticable when flashing FrancoKernel v 41 together with t LineageOS builds before mid August, but I saw it while on v42. I haven't seen the problems using Boefflas kernel or Caesiums kernel.
[OnePlus 3 & 3T Cross Device Development] HiBoU974:
The 20180814 build was smoothest than all the next builds for me but I can't revert back.

Now I have some stuttering.

5.0.5 FW

Caesium kernel
[OnePlus 3 & 3T Cross Device Development] :
I can't say if it's the kernel or not - since one expirienced 20180814 as smoothest and an other one expirienced the very same build as the starting of lagging, I'm pretty sure - at least - the trigger has tombe installation dependend. Never forget: the majority of users doesn't expirience the lagging at all...

I just want to exclide the MEMCG_SWAP commit. For that I need a confirmation from one of the "heavy laggers", that the kernel with that commit reverted is lagging.
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
I've just installed the boot.img, thank you, I think I could confirm within 24-48h.
[OnePlus 3 & 3T Cross Device Development] S4turno:
[MENTION=1763460]Dirk[/MENTION]

Have you tried FrancoKernel? I noticed that flash works on Snap with his kernel (r43 - 2018-09-15, also upstreamed). Can it be a Caesium-only issue?
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Hi guys, I know that maybe this is not the best place to ask, because I'm not on LOS right now, but I wanted to ask, whether I am the only one, who struggles with not working calls, sms and contacts after some time?

It happens to me on all Oreo based custom ROMs. It seems that the culprit is android.process.acore dying and not respawning, hence the problems with basic functionality (and I have to restart in order to be able to make calls).

I have no logs though for now, but you can try for yourself - execute

su
killall android.process.acore

and try to call yourselves from other device - the phone will vibrate, but you won't be able to do anything.

Is this process not protected? "top" shows that this process is run as u0_a19 and not root, which I find odd.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Something changed recently to allow Snap Flash to work properly on stock LOS/Kernel. I guess whatever that was aligns with whatever Franco has. Either Franco never had that issue in the first place or the 'repair' has trickled down....but not as far as Caesium. Who knows what that change was though. I guess if you randomly throw together ingredients time after time, eventually you get a cake.

I have updated my comments on the Jira ticket to reflect that Snap Flash has improved. After all, the LOS devs will take the attitude that their responsibity ends with getting their own Camera app to work, in their own ROM, using their own Kernel. The fact that the fix was probably accidental rather than deliberate is neither here nor there.

Personally i'm quite happy having GCam Mod installed and HDR enabled. In truth it makes no difference to me as i don't actually use cameras at all. The only pictures i've ever taken on a phone are test shots to see if everything works. That way i know that the function is available if i need it. (Which hasn't yet). Otherwise i have eyes and a built in memory. I'll go so far as to say i abhor camera culture and find it quite ridiculous.

My investigating into this issue is nothing more than morbid curiosity, and maybe the puzzle solving aspect that accompanies these sorts of problems. That always piques my interest! :laugh: