[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Loc2262:
Hello everybody!

I'm somewhat of a returning user in XDA, been lurking for quite a while now, so please disregard my device info at the moment. ;) In addition to the mentioned Galaxy S2, I also have an S5 and (as expected) an S7e.

First of all, a huge thank you, thumbs up and everything related to ananjaser1211! I've been using this ROM since the second day he released it, and I'm so impressed by what he managed to do in his first version! Yes sure, there are bugs, but those are more than to be expected! :) (I'm a software developer and IT person myself, so I produce my fair share of bugs as well.) Another big thumbs up for the work and effort he's putting into this! Reading through the issue tracker on GitHub, I can see that he's devoting a huge amount of energy and time to this.

Anan, I hope your exams will be or have been okay! :)

As for why I finally decided to write a reply here: Anan, contrary to your warning, I've been doing TWRP backups and restores of both System and Data of FloydQ back and forth to and from my previous ROM (HyperROM Pie) with almost no issues. The only thing I noticed is that the "swipe down on homescreen to pull down notifications" is not working after doing such a restore. But that's not necessarily caused by it, I've been observing this behavior intermittently at other times too. Unfortunately I haven't found a stable pattern for this yet. :( As a workaround I'm using a side-swipe gesture through GoodLock's OneHandOperation+ for this.

Also, I've even done restores of a F2FS Data backup to EXT4 and vice versa... I was actually very surprised that that worked since even TWRP warns about this! I'm using TWRP 3.3.1 MoRo 1.3. Maybe not formatting Data in between caused the problems for you? I was reluctant to do this for quite a while too, but have been doing it now after copying the internal storage contents to my SD card. :)

So much for now. I have some more information soon about entries in the GitHub tracker, I hope it's okay if I post them here since I don't have a GitHub account yet. (Will create one soon!)

Thanks a lot again and kind regards!

---------- Post added at 01:15 AM ---------- Previous post was at 12:52 AM ----------

Hello again!

A few annotations concerning entries in the GitHub issue tracker:

About overnight crashes: I haven't had any of those yet. I use the phone in airplane mode on a Qi charger on my nightstand, AOD on. I have Wifi and BT scanning turned off like the most recent user on GitHub mentioned. Not much help here I suppose, sorry, but maybe this info can be another data point in your struggle to find this bug.

I'd like to add though that like another user there, I had a comparable issue with a LineageOS 16 ROM, when I was using the phone overnight to play "falling asleep" music, with Wifi and BT turned on. Services would at some point stop reacting and start crashing, up to a point when the ROM soft or hard rebooted. Sometimes it got stuck so badly that it wouldn't turn on. So a similar situation like people are describing right now. As I said though I only had that behavior with LineageOS ROMs, so far not yet with Samsung based ROMs (LightROM, HyperROM).

About Bixby Voice: You marked that issue entry as "fixed in next release". When I tried Bixby on my phone, the setup wizard would run okay, but then when e.g. when trying to go to Voice settings and listing the available services, it would delay for like 5 seconds and then FC. Sorry, can't remember the exact procedure, been a week since I tried it.

About Notification Panel Quick Pulldown: As I mentioned in my previous post, I've encountered this behavior too, most notably after restoring a TWRP backup. But not only that, it happened after a fresh test install too at some point. So unfortunately this isn't really going to help, since I couldn't reliably reproduce the cause yet. But just to let you know that the behavior exists and seems quite random. Not a big issue though! Since I discovered OneHandOperation+ I've been using that for most swipe gestures.

---------- Post added at 01:28 AM ---------- Previous post was at 01:15 AM ----------

I've observed that behavior as well. If the GoodLock management app is not installed, both QuickStar and LockStar don't auto-run after a reboot. I noticed that since I use QuickStar to move the clock to the center, and LockStar to increase the lock screen timeout to 30 seconds (so I have more time to read notifications).

I found that QuickStar auto-launches when Good Lock is installed. LockStar does not though, I need to manually enter it, turn it off and on again to have its settings applied after a reboot. I have not tried the latest versions yet though, I'm using those that come with the ROM itself.