LogFox feedback

[drogga]

https://github.com/F0x1d/LogFox @F0x1d, your LogFox app doesn't seem to detect SU on Android 8.1 x86, nor does the UI layout look or works good/as it should, the UX needs to be improved, also adding accent colors picker for below A.12, because it has some default Material tint that I couldn't change, because I don't like it at all, please take a look at those things and improve it a bit, because I would like to have a decent alternative to Scoop (by TacoTheDank), which unfortunately doesn't "capture" certain crashes and has been stale for a while. Thank You !

[F0x1d]

Usually issues are opened in the repo of the app. But ok, 1) what is your device, ROM, any other information which may be helpful? What SU are you using? 2) what exactly UI/UX problems do you face? For me it looks and works well 3) there won't be custom accent picker because it is just hard and useless for such kind of app, where focus should be kept on more helpful features

[drogga]

1. Perhaps you didn't read carefully, where I already mentioned 8.1 x86, you should live boot any of them from here: https://sourceforge.net/projects/android-x86/files/Release%208.1/ to get an idea, I personally use the android-x86-8.1-r6.iso, but you can boot the android-x86_64-8.1-r6.iso one, it it works for you (I use an old PC, but you can use a VM). SU - IDK, it's built-in (Settings > Users & Accounts > Superuser) and IDK which daemon, libs and whatever is using and based on, but the prompt dialog to grant Root assess pops-up (like with any other app that can use Root), I grant it, but LogFox still says that there's no permission and the problem is definitely not on my side, because other "modern" apps use it just fine. It doesn't capture/record/grab any logs btw, unlike any other LogCat apps I tried (Scoop does), so it doesn't work when I grant its permission(s) by other means than the Root method from inside the app. The recordings are empty and when a particular app crashes stays undetected - 0 logs.
2. Try clicking on buttons with a mouse cursor on non-touch screen, especially the right-side Delete one for/on captures (the problem might come form the landscape orientation and the DPI/rez./screen size, but don't force it to portrait because of this, like some devs. unnecessarily do).
3. OK, but it's orange/yellow and I really prefer dark gray, or blue, pure amoled black or whatever else than the current color. Many other apps have an option for accent colors and I'm not a coder, but I think there's a code even here on GH that you can use for this with little effort, because the most is already done and completely free to use (licenses, etc.), but I can't currently provide any links and examples, but I've seen such, which you as a developer should be able to find easily. ;)

@F0x1d 2 & 3 are actually a low priority thing, I can manage with or without, if the logging worked.

[F0x1d]

1) can you check build from https://github.com/F0x1d/LogFox/actions/runs/9749938958? It should fix the issue. Or from https://t.me/f0x1dsshit_ci/557 2) I'm developing the app using Android emulator, got no problems with buttons. Which do you face? 3) Just use Monet, I guess

[drogga]

@F0x1d

1. I've used the Actions/Workflow .apk, since I don't have TG and now using the Root method it let's me in, but nothing is captured that way, using this method unfortunately, granting the permission to read logs manually does make it capture logs/crashes, just not with the root authorization method. Clearly you probably didn't even bother to live boot the x86 image of A.8.1 (Oreo) to test yourself, else you would've saw this.

2. I have to click on them in a certain way with the left mouse cursor to register, but I figured that it works better by using the middle scroll wheel as a button (down pressing it), otherwise for example the 3-dots context menu button in the main logs menu isn't clickable, some others as well, but I doubt you can address/fix this or do anything about it and you probably won't notice this in an Emulator, like the Android Studio images.

3. So I know it's Alpha, but you got rid of the Theme option/preference completely - why ?, that's not a solution to any problem or for anything actually. "Monet" is not an option on lower than A.12 and I don't even have anything with A.12 and I don't even want to, given the current state of android, since 11 everything did go downhill, sure there only a few things that I like, but mostly restrictions and limitations. Also since it's related to the UI - Now I can't even stop the service from the LogFox's notification (the button is simply missing - probably intentional), nor can I open the app from there, so it somehow seems worse than before...

4. Please add exclusion/exception/blacklist (like how "Scoop" has one), so apps that often crash can be excluded from capturing and it won't bother me. Here on A.8.1 x86 the SystemUI crashes when the Recents NavBar button is being used (once I connect it to internet), so such apps should be able to be ignored by LogFox and I didn't see any way of doing so anywhere in the app. Thank You.

[F0x1d]

1. You are right, currently i do not have enough time and will to spend it with x86 image of oreo, but it looks that i'll have to
2. Not reproducible in Android Studio emulator, yeah. So, it looks as your emulator problem (the second one, btw). Can you share me some instructions about booting your image?
3. I do not like this preference. Completely. There is system preference for theme, why would you override it? I really like the way it is done in iOS. Most apps just follow system theme and have no such preference in them. Older iOS versions just not support it. Yeah, older iOS versions are only on really old devices, but the same can be said about Android nowadays. Even the cheapest gadgets today support A12+. And about limitations: you are right, they are annoying, but you won't be able to avoid them the whole life. There are a lot of apps today that have even Oreo as their minSdk. So, it is just better to adapt to changes and enjoy the latest cool features.
4. Button "Exit" stops the service. Now you can't run the app without service, as the logic was moved there. If it annoys you - disable service notification in system settings, there is deeplink for it in logfox notifications settings. You will be able to open app from it, this is a known issue
5. 3rd reason to think about this image being stable? This feature is on TODO list, will be implemented soon

[drogga]

1. Yes, please do so when you have time/asap.

2. It's technically not an "Emulator", nor a VM, it's just a Android boot on a PC x86 arch. CPU hardware. The problem is not only mine, but a global one when android is being exclusively and strictly told that there's no touch support, but instead it should only rely on a mouse & KB, when the emulators are used on a touchscreen, you can operate that way, no problem, but it also emulates touch support by just using a mouse, unlike x86, which knows that I have a display/screen and that it's definitely not a touch one, with/in some other Material You apps (like: InstallWithOptions & TranslateYou) the mouse can't even be used to long press and drag up-down, left-right to scroll menus/lists, instead only the mouse wheel works for this, this is a bad coding IMO, whereas in a VM (VirtualBox), you have the option to choose if it should emulate/simulate a touchscreen, where the problem shouldn't exist. You seem more focused on this point/remark, than the rest, but as I said previously - it's a low priority, I can get around this in your app, simply by using the middle mouse button instead, so don't spend much time on this, the other things are way more important and the vertical (here with a landscape orientation) main buttons on the left side are clickable with the left mice button anyway. Sorry, I didn't exactly get what you meant by "(the second one, btw)"... "Can you share me some instructions about booting your image?" -> Nothing specific... USB Drive with "Ventoy" and the .iso file there, so I'm booting to it from/with the quick boot option menu [F4 in my case, no UEFI or GPT support btw] > normal method, not grub and choosing the option to skip the setup wizard from the advanced ones (or whatever are exactly the labels, I'm currently using it to test your app, so I can't exactly quote them).

3. Like it or not, it's the only way to change the theme on lower than A.9 Pie, where there isn't any option or quick tile to do this and your app runs on A.7+, so now how I'm supposed to change the theme if I don't use apps for this or edit the android database tables (with SetEdit) to add the "night" one, which tells the apps without a theme preference to go dark ? IDK if you considered this, but some people prefer to use their devices with a different theme, than the apps, in A.13+ there's even s system setting to choose / override the app's themes (diff. from the one in the developer options) and YouTube is toggled on to use its dark one by default, even when the system one is not set to dark, or at least that was the case the last time I checked, which was a few days ago. There are just some devices with still powerful hardware that can't be updated to 12+ (I blame the manufacturers and Google) for one or another reason or people like me (power users) that don't want to update, if there wasn't the planned obsolescence, those devices will still be good for many more years, besides there are many non-phone or tablet "smart" devices that run android, don't have updates and you don't replace your fridge, oven, car head unit or whatever regularly if you don't have money (I'm poor AF), for example a friend's car head unit is a third-party / off-brand one just over a year old and it runs A.11, no OS updates and it doesn't even have the system "Files" app, so no file picker, what can it be done in this case, who to contact to update/add it in China when it's the latest one for that model, bought from eBay or AliExpress and it wasn't cheap - no one can do anything, so yeah... Also the limitations and restrictions overweight the goodies in 12 and up, sure I will have to use newer ones sometime in the future, but until then - I won't. I agree that iOS looks better.

4. The service notification doesn't annoy me and I know that I can change the priority to basically hide it or disable it from the system app's settings (power user here, remember ?), but I'm not familiar with Deep Links, but you probably meant that it will open the system preferences for me, acting as a shortcut, tho I don't get what you mean that it's a know issue...

5. "3rd reason to think about this image being stable? This feature is on TODO list, will be implemented soon" -> I'm afraid I'm not following..., what being stable - x86 ?, no it doesn't seem to be, probably it will be more if I boot it in a VM or from a CD/DVD, instead of using Ventoy. What will be implemented soon - the exclusions / blacklist ?, can you please mention that ToDo internal list in the ReadMe ?

...I feel like we might've made a bit of a mess with the numbered list here... Sorry for the essay btw.

[drogga]

Btw it seems like the service suddenly started by itself out of nowhere without reboot (I've used the "Exit" button from the notification before it happened and noticed the icon in the status bar while typing the prev. comment)...

[F0x1d]

1. https://github.com/F0x1d/LogFox/actions/runs/9822059838 I would kindly ask you to test once more
2. Ok, I got it, ty
3. On these versions there was a toggle in developer settings (on A9 was, others may not have it), but, still, my position is the same. Why would you have different themes for the system and apps? It is just weird to see bright icons in launcher, bright quick settings and then enter dark-themed YouTube, it even sounds weird. I completely just don't understand it and want to "improve" the situation, trying to show people (using LogFox, Sense, DNSManager) that it is not OK to have different themes. Just, like, WHY? Really small amount of people is using something lower than Android 10, I guess, they got used to light themes. If your device is not officially updated any more, then just install custom ROM, that's a usual situation for any Android user. I've had OnePlus 6T (last official Android update was 11) for a long time, ended up using it on Android 13 with custom ROM. And I repeat myself, noone will remove limitations, you just end up with no apps on your device. It's time to adapt and enjoy Monet
4. Known issue was about "nor can I open the app from there, so it somehow seems worse than before...", it is fixed now
5. Yes, "exclusions / blacklist" for notifications. Also already implemented using system notifications channels. However, there is no public ToDo list available

[drogga]

I will test asap, probably tomorrow. Thanks.

My daily driver is with 8.0.0 because reasons. I work in a repair shop/service and you won't believe how much users are using the white theme when there's a dark one available (which I prefer, but can't use on mine). It's obvious that you don't get the concept and believe that every app should just use the device one instead and take away the option/choice from users, but the fact is that now if you haven't added the theme preferences back, I'm stuck with the nasty damn white one to blast me at night when I switch apps, I hate apps that don't have a theme picker, I use other devices with various Android versions, most are with below 9 for reasons, some don't have ANY rom/recovery support (not even Lineage) and are with locked bootloaders that can't be unlocked, you might suggest to develop myself roms and recoveries, but that's not realistic, nor I have the knowledge (know-how), but this might be hard for you to imagine or believe, so I don't know what else I can type to explain & prove how wrong you are about the theme thing. I have basically 3 options: 1. Not actually using your app, because when I get a crash, I'll prob. have to open your app to clear it or whatever, which won't be in dark and can't be made to. 2. Use some of those Dark Theme apps that change the sys properties DBs. or 3. Mod it to make it always dark, which is what I did with Scoop and some others and is way easier than having to fork it, mod it and compile it (I don't have an IDE, so I will have to play around with GH actions, but I'm not good at it, because I can't code). I won't actually be enjoying Monet, this is aweful IMO, I hate those sys. accent bs, changing themselves based on the wallpaper or whatever, thankfully there is a app that can use Shizuku to make this nonsense/mess somewhat manageable in 12+. Also on A.12+ everythime the device reboots, the read logs permission gets denied, so it has to be granted again and I'm not even going to mention the other nonsenses in 12+, those new OS versions are not actually usable for a power user like me, so please don't try to convince me that they are any good and that if I want a dark theme (which you removed) I have to update, which is not an option for me for many-many reasons, also I can't afford a new device, all the money goes to medical expenses and other important things, than having the latest gadgets, which aren't even better than what I have.

Notifications channels aren't very manageable in lower OS vers. and I meant a blacklist for apps, which logs don't have to be captured at all, but ignored, not just their crash notifications, I really hope that you implemented the thing I meant, not just ignoring their notifications as you described. Also it seems that even with the option to resend the missed crash notifications ("Show only logs which have appeared since the app launch") enabled, the app keeps sending and stacking past, already ignored (swiped away), checked and deleted crashes and the worst part is that they can't be cleaned at once from the notifications tray, but I have to swipe them away one by one, because they stack like a discussion chain under the same main notification and I don't find a way to fix this, so I hope that you did....

[F0x1d]

Got you, i'll think about returning dark theme switch.

But you can already ignore specific apps' logs just using filters?

And I didn't get the last part about too many notifications

[drogga]

OK, pls. do this, I will reAppreciate it. Thank You in advance ;)

I couldn't find those filters, is it because a button doesn't show up or I can't access it - IDK, but I will really appreciate if you can please show me an example in the form of a screenshot (or multiple), video recording or a guide on where exactly I can find those filters and how to use them (thanks in advance).

There's usually a Clear All button at the bottom/end of the notifications tray for Non-persistent notifications that CAN be swiped away (to ignore), using it does what it's supposed to - clears the notifications at once, but LogFox has and uses a persistent notification, so the crash notifications for separate apps show under LogFox's main (service) notification, not as new, hence they can't be cleared from that button, which doesn't even show up for them. I hope you got what I meant, because currently I can't even show examples, nor explain it better (I don't currently have access to LogFox and I'm tired from working whole day, will go 2 sleep soon), I can probably show an example as early as tomorrow or you can test and see for yourself on A.8.x if you can't wait.

[F0x1d]

Got it, but strange behavior for notifications, I'm not sure that I can fix it, maybe you can just hide service persistent notification?

About filters: https://github.com/drogga/TextWarrior/assets/39910552/b9b3bd98-5628-4bb2-9489-1b342aead0f0

[drogga]

It now works and reads logs with Root - Thank you for fixing this.

The filter is only for, available and applied to the main [LogFox] activity/menu tab, where all the device logs are listed and I want/need and meant one that can applied globally and works in the [Crashes] tab as well to not list or store the crashes of the excluded/blacklisted/filtered app, nor show a notification for, the "Crashes" doesn't even have any sorting or search filters by app label/name, package name (for just uninstalled apps that crash) or inside the crash entries, so I can search for a particular line, like "Caused by" for example, instead of having to do that outside or externally. Please check https://github.com/TacoTheDank/Scoop and implement the options, buttons and settings that are missing in LogFox. You can probably also implement in future a long-press menu or Gestures (swipe to delete without confirmation and others) in the Crashes tab.

The notifications stacking is inconsistent, sometimes the crashes are as individual separate notifications (I've changed the priority so the SystemUI crash doesn't pop-up, on some of my other configurations I've globally set the HeadsUp Notifications to False, because I actually hate those pop-ups and LogFox uses by default the highest Urgent importance priority for the crashes, which not only is as a pop-up, but also with a sound and a vibration), sometimes they are stacked inside the main service one. IDK if hiding/disabling the "Logging status" one (under "Other") as you suggest won't eventually make the system optimize and kill/freeze/put to sleep/disable LogFox.

Please also add an app language picker preference/settings option, because just like the theme one - I can't change this per-app basis (only systemwide if not as preferences in the app - many apps have such) and the language and regional date/time format system preferences of a particular app are A.13+ thing (if implemented by the apps developers).

[F0x1d]

1. Oh, I got it. Will add search and I'll think about blacklisted apps' crashes.
2. Notifications stack when there are a lot of them from one app. So, if you hide notification which can't be removed, then you'll be able to use "Clear all" button
3. Haha, omg, now language picker

[drogga]

1). Let me know when you implement any of the two ;) 3). Yeah... 4). When I pause the main logs, clear and go to another tab or out of the app and back, the logs are still there, shouldn't it still be empty, given that it's still paused and wasn't resumed ?

[drogga]

I just tested v2.0.1 and unfortunately there's a still no search inside the crash logs themselves for a particular text (would be nice if Ctrl+F worked at least), only outside in the Crashes tab. There isn't any way to blacklist/exclude logging/saving of crashes in that tab either.

There's now a option to open the crashes tab at launch, but the problem is that the first (device logs) tab button isn't clickable in that case (it is when disabled, which is by default), I can go to it when I go back, but I expect to exit the app, not to go back to a tab I've never been... Also when that option is enabled, the main tab keeps resuming the device logs, it just refuses to keep them paused and empty when cleared no matter what, when the option is disabled, we go back to 4., they remember and stay paused and cleared/empty, until I clear LogFox from the recents, relaunching it still doesn't remember the two, it just doesn't let me permanently pause or even disable them and keep the tab clean.

[F0x1d]

I will add search in crash logs also.

But I completely didn't get about crashes tab by default as it works absolutely fine on my device & emulators.

And also I didn't understand anything about logs not pausing/resuming. If I switch between tabs, they stay paused/resumed, where is the problem?

[drogga]

As I explained - when the second (crashes) tab is set to show by default and I go back once, I should be out of the app (exit it), but it doesn't happen, it goes to the first (LogCat) tab, which wasn't never opened, given that it's set from the settings to open the second (Crashes) tab by default.

Pausing LogCat (first tab) {as I also explained} - They resume when I exit LogFox and remove it from the recents, please read very carefully what I've wrote, which isn't about switching between tabs, so try to exit, swipe if from the recents screen/menu and open it again. The best would be to record a video to show you what happens, even tho it's pretty obvious, but unfortunately the x86 image I'm using in Live Boot doesn't support and can't make screenshots or video recordings (the experimental Vulcan support boot option probably does, but it doesn't boot on my Core 2 Duo machine) and I don't know if it will act the same in/on a real device (I use Scoop, until LogFox is made better, hopefully soon with all the Scoop's options).

[F0x1d]

That's so minor issue lol, who even uses back button to exit apps?

You completely closed LogFox and expected it to save some state? That's strange. This pause feature applies only to UI, it would be strange to pause logging completely (what for?), as it will stop receiving crashes, for example.

And what are "all Scoop's options"?

[drogga]

Everybody..., because whoever just uses Home to minimize is careless, like never actually closing anything, unless later dismissed from the Recents (I see that you have your own ways of operating with Android).

No, I didn't completely closed LogFox, not at all, as the exit from the notification wasn't used and the app/service and whatever component was active and was capturing logs, if I used "Exit", then it would've been a complete close/exit/shutdown. It's not strange to want to pause or completely disable the constant OS logs and want to save and keep that state, not only because I care about the crashes only, not any other LogCat, but also it might even offload some resources and battery drain (just a guess/speculation).

Like opening the crashes menu at launch, without having to go to the LogCat one upon attempt to go out of the app by going back like a normal person would do and expect to work properly, having exceptions/blacklist of apps that often crash and we don't want the Crashes menu to get filled with those, having a search in the crashes (which you said you will implement), combine or not the same apps/crashes (the later one doesn't actually work in Scoop) and a decent dark grey and maybe even amoled theme(s), without orange tint (the later Scoop doesn't have).

[F0x1d]

Why would you even remove app from recents? It's not Android 2.3.6 and not 2010. Nowadays system can optimize apps in background. But you just waste your time by waiting for cold boot of app every time

You closed UI part of app completely and, as I said, pause plays its role only in UI. If you don't pause and close the app (even with home button), it won't drain your battery as UI is not updated in background in LogFox. So, there is just no sense in saving paused status between sessions

Blacklist and search will be implemented in LogFox. About others I can't give any guarantees now. Because I don't like the appearance of AMOLED themes, but I really enjoy Monet

[drogga]

IDK what to tell you, people don't want to keep apps in the recents, sure newest android may completely pause some apps while they are in the recents (background), but most won't and older Android versions don't haves a great efficiency mode (I'm using an old device with as daily driver, your app requires and supposedly runs on A.7+, which is not as power efficient as the newer OS vers.), not everyone is with A.14/15 and I can tell you for certain that minimized apps in the recents consume resources & battery, compared to when swiped away/removed from there, that's for sure. Some apps are just not written properly and don't create/destroy/refresh activities as they should, so if you want them to work as they should, you have to remove them from the recents, because returning back to it from there or from the icon while still in the recents restores the previous state, which is not always wanted or necessary, play around with InstallWithOptions by zacharee to see what I mean (IMO it should have an attribute to self remove the main activity from the recents: excludeFromRecents to true). If not retaining the paused state no matter what, then please provide a way of stopping or disabling completely the LogCat and maybe even hiding the first tab, but it should not/never go to it no matter what, needless to say that the grabbing/capturing of apps crashes should still and keep working.

Thank You, I would appreciate any ETA for the implementation of the BlackList & Search inside crashes, but you probably can't give any. Given the issue ticket in your repo (in which I commented), it's obvious that not everyone has the same opinion or likes the look/appearance of Monet colors, I guarantee you that many users hate it and even prefer Amoled themes, so I doubt there will be anyone to complain about it if added and made optional. I will use an Amoled one if the accent/tint isn't made optional (even tho I prefer dark grey), because I don't like at all the orange tint, which I can't change on pre-12 and I don't have anything with 12 or up. Maybe you can use Aurora Store as an example of themes and accent colors...

Edit: It's beyond my understanding why anyone would want a sys tool app like LogFox or any other similar for that matter to be kept in the recents, especially when it's not supposed to be used often, but only when an app crashes or if you want to see the LogCat and it has a service, with a persistent notification, it's not like it's being constantly used (unless something crashes non stop, but such you have to stop or uninstall if possible anyway) or an app you have to open multiple times a day, like a browser, communication (chat) app or a social media one.

[F0x1d]

I'm a little bit confused, how am I supposed to pause logging but still notify about crashes which are read from logs? You can stop logging just by clicking "Exit" in notification.

I really feel like I'm being trolled with this themes/recents/pause/emulator. I have never met a person in my life who would have seriously cleaned the recents (even my granny doesn't do it).

You can safely leave LogFox in recents and forget about it, as it does nothing on UI when in background

[drogga]

IDK. Pausing the LogCat in LogFox is just a visual thing right?, like in every other app with the permission to read them, so I don't see any obstacle on why don't make that UI state permanent and to be retained, even after fully quitting/exiting the app, even after a force stop/close from App Info. It can still do its logging, it just won't show it and the field will be empty (it already kind of does this, just resumes it after clearing).

IDK how it's possible to be trolled about Ui, I've never tried it in Emulator. You are probably an ex Apple or also currently users, everyone I know uses "Clear all" in recents at least once a day, that's 4 family members and other people I know, you need to meet more people then (it makes sense your granny to not clear the recents, I doubt she's a power user, testing apps, grabbing logs, roots her devices or contributes in GH or alternative platform repos).

It makes 0 sense to me to keep LogFox in the recents and you can hide the tab if you want (for sure - optional ofc.), but it looks like you don't want to do it and lack the motivation. I don't see any point in digging into this particular thing any further as it gets nowhere, but we might discuss other things when you add the promised things.

[drogga]

So I've tested the latest dev branch actions build, here are a few remarks: The Blacklist it's not scrollable by dragging with the mouse cursor up and down, only the scroll wheel works. The Search doesn't have to be whole field that expands like that to what one might think a whole new menu, but it can be as a top button, among the Sort, Blacklist and Clear ones. For each crash there can be a Blacklist button before the Delete one. Inside a crash there's still no search query, but the button for it should be among the top 3, before all of them (when you implement it), like Search, Information, Notifications, Blacklist, Delete, the crashed app's icon and the 3 button (Copy, Share, Zip) don't have to take so much space (in landscape).

Details

I wish it remembered the paused & cleared state of the LogCat (first tab) when you return to the app (not removed from the recents) after backing out, maybe in future...

[F0x1d]

1) The blacklist is scrollable, just consider using normal device/emulator 2) This is google's Search Bar, all questions to them. Personally I like this style of search 3) I'm not sure this feature is so popular to have button in list, I'll add it in crash details screen 4) It does search inside the crash log, just use the default search on Crashes screen

[drogga]

1). /releases v2.0.1 the Filter (apps list) IS/was scrollable with the cursor, so I thought that the same list of apps, but for the BlackList should be too, but now in v2.0.2 (from Actions) that one isn't too, which is strange, isn't it ?, I get the part of using it on/in a real device, but it's something that was working and now it isn't and it doesn't make sense to not work. It think you should really embrace and implement soon the suggestion for a ScrollBar (FastScroll) in all the lists, which if draggable with a mouse cursor or being with thick enough handle to grab it with a finger will help a lot in the apps lists.

3). I suggested a top level Blacklist button in the Crashes menu of each crash, so I don't have to go to a sub level in the crash details when they are more than 1 for a particular package, which is more taps, but whatever.

4). But it's basically useless, the whole point is to work as a text editor and highlight the matching text, not to just point to that crash and me to have to still look at all the lines to see the matches based on query. Have you ever tested at all Scoop to see how it does it ? (at least when not in Selection Mode {toggle button on top}), because I feel like you haven't, because I've always meant it like this and I'm pretty sure I've mentioned/described it multiple times. I don't want to have to export/copy the crash log and open it outside with/in a text editor app and then search for what I'm looking for, how is LogCat search query showing and highlighting the text, but the crashes search can't..., that's why I wanted a dedicated and separate Search button inside each crash log, which makes way more and an actual sense.

Btw now it seems like without even pausing the LogCat and back out of the app and return, it goes to a paused state and I can't make it stay resumed and even paused, there are still logs remnants/leftovers and I can't make that window stay clean, only when going tru the tabs, once out, some logs are back even tho it's paused and cleaned previously. IDK man, it's acting out a lot and needs work, I hope you have a break through soon and manage to fix it once and for all to be consistent.

[F0x1d]

1) I refactored it to Jetpack Compose, so all questions to Jetpack team 2) I understood, but I don't think this feature is too popular to place it in list. I can't check it as LogFox is FOSS and people are afraid of analytics 3) Ok, I got your idea only now, implemented on dev branch. I can't test Scoop as it does not work normally on A14 4) I still don't understand the problem with all these states. WHY do you want to keep it paused? LogFox does not update UI in background, I promise, nothing bad happens if you leave it running, really

[drogga]

It's actually more confusing with the numbers...

"I understood, but I don't think this feature is too popular to place it in list." > FastScroll bar ?, it's popular, even tho for some reason is underappreciated and not that usable or available everywhere on Windows, let alone android apps. If you meant the Blacklist button next to, or before the delete one on every crash, before even opening its details, then you are wrong.

"I can't check it as LogFox is FOSS and people are afraid of analytics" > The fast scroll bar library ?, if YES, then Muntashir is using it in his AppManager, which supposedly is also Foss, there are also probably plenty of other implementations, some probably better than others, if you weren't referring to this, then IDK to what - I'm confused.

"Ok, I got your idea only now, implemented on dev branch." > Tested and it's working. Thank You !

"I can't test Scoop as it does not work normally on A14" > Thanks Google for breaking things and the devs that don't maintain their software to reflect on the latest BS and workarounds/sacrifices they have to make. Not that it matters that much now, as this is getting very closer to it as of features and whatnot, but you can/could've tested it on another device/emulator, even x86 live boot like me if you wanted to with older than A.12, so that's actually not a very valid excuse.

"I still don't understand the problem with all these states." > Me neither.... "WHY do you want to keep it paused?" No, now I want to keep it resumed, but once I change the tab it goes to a paused state by itself, odd af behavior and an anomaly, as I've never paused it, this is a clean install on a just booted clean OS, it doesn't retain its states, that's the whole point. "LogFox does not update UI in background, I promise, nothing bad happens if you leave it running, really" > Do you read between the lines, skipping some or what, IDK, but I wrote multiple times that I keep it running in the recents and don't close it at all and it's still problematic. I hope I don't have to repeat myself anymore...

[F0x1d]

I meant the blacklist button in list. I'm not sure about being wrong as you are the first person asking for it. On list there are buttons that provide fast access for commonly used features. You will click this button only once after the setup, why would you want to see it after your click?

I meant that I can't check if blacklist button in list will be popular as analytics are forbidden

You are speaking like my project manager or the person who is paying me money for my work. But keep in mind that I develop this project in my free time and for free, there are even no donations. I don't want to spend my free time on booting android on my PC, why would anyone? And still, I implemented some of the features you requested, even logs search in latest commit to dev branch. So, please, be respectful.

I don't understand your problem with paused state, it works perfectly for me. Can you do a screen recording showing the problem?