yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Lennoard:
Nice. They should get an update - Signature is the same and the current version code is greater than the one that the build you installed has.

Oh.

[Lennoard: thinks for 5 seconds...]

:silly: My bad! I will be updating the pages with the Google Play beta channel link :good: ;)
[Android Software/Hacking General [Developers Only]] sliding_billy:
Just got the update to beta from a couple of hours ago. After reboot, the only line in the log is [E] [2019/08/09, 03:54:29] Failed to create app files folder! (MainActivity). Is that right?
[Android Software/Hacking General [Developers Only]] Lennoard:
Weird.

The task seems to start, but never ends, neither throws an exception (i.e crashes), hangs (i.e application is not responding), nor times out in 2 minutes.

Since these logs are way too empty I assume the root shell managed to open? Can you try to deny root access and see what happens?

I will also add a partial wakelock just for sanity's sake. I need to check.
[Android Software/Hacking General [Developers Only]] sliding_billy:
It gets stranger. I denied root and rebooted then re-applied root acceptance and rebooted again. Both times, nothing at all happened in the log. The last thing in the log is the failed to create app files folder message from yesterday morning.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Another update, and it is hardly working on beta. That being said, it was not working on stable either. Of the 5 devices that I updated a couple of hours ago, 1 (T713 running Pie - LineageOS 16 official) gets through to changes applied and sends a notification on boot. The other 4 (Pixel 3 XL on August Pie, Pixel 3 on August Pie, 2 Huawei Mate SEs running Oreo) show nothing. The Mate SEs actually got through all changes with notification on the initial beta install that I did. There have been 2 beta updates since that one that do not work, and they didn't work on stable either. In fact, the only device that ever worked on stable was the T713 both on stock Nougat and on LOS. All 5 devices are rooted with Magisk 19.3 and BL unlocked though technically the T713 did not have a locked BL to unlock. Given the lack of failure notifications or failures in the log and the fact that this goes back to stable, it is highly likely that folks don't even realize the app isn't working. The log is really just a success notification generator and clearly a deeper dive with full logcat info is going to be needed. Let me know how I can help, but we can't just keep spit-balling changes. I didn't even mention that I literally am just using the cleaner function right now since it is not boot driven. Even something as simple as kernel changes don't show despite the fact that the 2 Pixels are running ElementalX custom kernels as is LOS. The Pixel 3 XL one time right after stable install showed available kernel changes, but none have since. I do see in the settings that they all show root patch unavailable and Busybox patch unavailable despite all having up to date Busybox and root as mentioned. For now, I simply cannot trust that anything is working. Sorry for the rant, but this is the support channel listed.
[Android Software/Hacking General [Developers Only]] Lennoard:
Thank you for all that info. I will be sending you some special builds with deeper logging enabled (and some special changes too) as soon as I got time to.

Starting with:

Could you please go to Advanced options > 3-dot menu > Run command > Root shell >

type "id"

Do it again, but now type "busybox which busybox"
[Android Software/Hacking General [Developers Only]] sliding_billy:
Looking forward to testing the changes. The info requested is below. I assume the signature will be the same as the play store on so that I can overwrite without uninstall

uid=0(root) gid=0(root)

groups=0(root) context=u:r:magiskmagisk:s0

/sbin/busybox
[Android Software/Hacking General [Developers Only]] Lennoard:
Yes, the signature will be the same. Based on the output of those commands I can at least say that there are no problems with opening root shells and adding commands to them (at least on the device you tested) and busybox is also recognized.
[Android Software/Hacking General [Developers Only]] sliding_billy:
That was the 3XL. All 5 devices are rooted with Magisk 19.3 and grant SU on HEBF launch, so I'm sure there isn't a problem with it other than it not showing a path in settings. The Pixel 3 XL, The Pixel and the T713 all use BusyBox Pro (Stericson). The 2 Huawei Mate SEs use the osm0sis Magisk module.
[Android Software/Hacking General [Developers Only]] Lennoard:
[MENTION=4609886]sliding_billy[/MENTION]

Here's a build.

Changelog:

Reapplication of changes now has its own execution thread

No notification will be shown on boot. (for now)

Debug mode is on: logs will be collected (heavily collected TBH)

Su and busybox path should be shown correctly

PS. Every root operation is being loggeed, this will have performance impacts. You can seach the logcat for "RootShell". Other commands logs are in the app log, like before.
[Android Software/Hacking General [Developers Only]] gurwinderr84:
Will this work on my rooted k20pro???
[Android Software/Hacking General [Developers Only]] sliding_billy:
I'll get it running ASAP. I am confused by the double negative in your 2nd statement. I assume you meant there will be no notifications shown on boot (either success or failure). Thanks!
[Android Software/Hacking General [Developers Only]] Lennoard:
No notification will be shown*

lol

---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------

It should work. If you're not confident about it, try it slowly.

Ps. Please don't quote the whole thread :p
[Android Software/Hacking General [Developers Only]] sliding_billy:
Definitely better results based on the logging. Of course I figured out that as I expected there would be no notification on boot and all devices are showing SU and BB path now. There are some differences compared to the log you attached, but you would know them better than I would. All 5 of these HEBF logs were taken immediately after reboot (so the last set of log items with that time stamp is the reboot one) time though not immediately after installing the test version. I wanted to give it some real time running the device where pretty much all of the stamps today start with installation of the test version. The very obvious thing I saw in the log and in real life pwerformance was running the cleaner. That was the last thing I did on each device before reboot. Not sure if it is just the logging taking so much time or if it is now doing something properly that it wasn't doing before. The SE A one I thought maybe I for got to press the "I know what I am doing" button since it was taking so log and it looks like I ran cleaner twice. Hopefully this gives you enough information at least for install, cleaner and boot since I still have a pretty stripped down HEBF profile on these devices.
[Android Software/Hacking General [Developers Only]] Lennoard:
Thank you. From what I saw in these logs it seems that on all 5 devices the app core is working: commands are being executed. Good.

I can see, only on Pixel 3XL the app tried to reapply its changes, fsync it is. On all other devices, the app had nothing to do (apparently)

So now I'm going to re-enable notification on startup, I suspect that maybe there is something broken with the framework notification API - which therefore interrupts application execution, so I'll be using the support library.
[Android Software/Hacking General [Developers Only]] sliding_billy:
OK, that is odd. The Pixel 3 and Pixel 3 XL have the same kernel (ElementalX) and both show the same things in HEBF kernel options. Apply on boot off, Fsync on, DoubleTap2Wake off. Neither have Fsync enabled in the kernel settings according to the EX Kernel Manager. So 1) Why the difference in the log between the 2 devices, 2) why does it show enabled as on in HEBF when it is not on in EX, and 3) is HEBF actually doing something on either device since apply on boot is off?
[Android Software/Hacking General [Developers Only]] Lennoard:
1) HEBF will only reapply changes once you interact with it. If the app finds fsync "on" for the first time, if you don't interact with it (e.g turning it off and on again) when the device is rebooted (and you checked apply on boot) HEBF stiil won't do anything (because you didn't do anything). I believe you've toggled that switch some time in the past.

2) There are actuallly 3+ different fsync paths, maybe bacause of this?

3) I double checked and found that I accidently removed the condition check when I moved to the new thread approach. Should only affect Kernel Options though. And sorry for that. Attached below is a build with a fix for this.
[Android Software/Hacking General [Developers Only]] sliding_billy:
1) I am sure I never had it turned on either in HEBF or at the kernel itself.

2) Possibly. Is there some way to manually check which is being read vs which is set?

3) Good deal. Is this the only change in this build? No notifications or anything, right?
[Android Software/Hacking General [Developers Only]] Lennoard:
1) Ok then, I'll put it under investigation.

2) I don't think I got it. But here's what we're doing: the app checks 3 paths, if at least one of them exists, the app shows the "fync toggle". At this point we could just save the path of the existing one somewhere and be cool when the app gets to reapply changes but this way if the user changes to another kernel it would possibly be broken again, not to mention that you can actually download configuration files from other people and apply them. So when toggling fsync we add a condition bundled to the command that checks if the file exists before changing its content. It's done for 2-3 of the fsync paths. You can in theory, check it yourself:

/sys/kernel/dyn_fsync/Dyn_fsync_active

/sys/module/sync/parameters/fsync_enabled

/sys/devices/virtual/misc/fsynccontrol/fsync_enabled

3) Yes, that's pretty much the only change
[Android Software/Hacking General [Developers Only]] sliding_billy:
That makes better sense about #2 Fsync checking path. Thanks for looking into #1. I've got this build loaded on all the devices. Is there anything specific you would like checked, or just run as normal for a while and save some settings as needed to real world test? At least now we know it is working on boot even without a notification.
[Android Software/Hacking General [Developers Only]] Lennoard:
Thank you. I'll enable notifications again soon and then I'd like to do some more testing. Right now I want you to use the app as you would use normally.

But if you're really into testing, could you try the new Window Manager? (please don't be too wild with it, you can literally lose access to your screen) (fixable with USB debugging) (the app will try its best to avoid it)
[Android Software/Hacking General [Developers Only]] sliding_billy:
I will take a look at it. I assume it modifies system and not user. Nice thing about the google phones is the ability to flash without losing user and then just get root back, TWRP if you want it and any modied system files like props withing minutes. I would do any playing on my 3XL.
[Android Software/Hacking General [Developers Only]] Lennoard:
[MENTION=4609886]sliding_billy[/MENTION]

Please check the notification with this build

Changelog:

On Boot notification enabled again

Using Kotlin Coroutines!

Reduced APK size

Small bugs fixed
[Android Software/Hacking General [Developers Only]] sliding_billy:
Thanks. I'll get it loaded tonight.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Reboot notifications worked on all devices. I have not done much regression testing, but I cleared my logs after installing so that they were clean. The only thing I noticed was on the last device that was set to reboot (the 3 XL). I used all of the device normally after installing but before rebooting and used the cleaner on all of the devices immediately before reboot. It was fairly quick on all devices I assume because of the empty log. It had been crashing during the last two test builds while cleaning. Sometimes, it would take multiple runs and even reopens with a notification that it had closed unexpectedly. I figure it is do to the extra logging that is happening in the test builds. Only the 3 XL didn't complete without failure. I pulled logs after all the reboots that will include that for the 3 XL, and I will send them shortly.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Here are the logs. As I hoped for, everything after the reboot is identical except for the occasional order of events (of course). A quick look through the app, and everything that should be showing as an option or information looks right. Besides the logging (assuming that is what is causing the cleaner issue - you can obviously see a ton of log entries as well as some restarts of cleaner/app unil it finished successfully on the 3XL), I see nothing that isn't working other than settings specific stuff that can't be QA'd properly without test cases and expected outcomes, etc. I see the app has an option to turn off device logging. I assume that is blocking the logcat from writing, but is there a way to disable HEBF logging temporarily to confirm that the cleaner issues go away and are not related to needing to open shells during cleaner operation for example?
[Android Software/Hacking General [Developers Only]] Lennoard:
1. You're right. That option stops the Android Log Deamon

2. Currently not. I may add an option (new build in 6hrs or so) to toggle it in runtime but I'll surely output everything to the default logcat. Redirecting to the app's private log file has proven to be quite an expensive operation, especially with extended logs in these test builds.

In the meantime, I tried the cleaner myself to see if it crashes but apparently it didn't. Although I have found weird behaviors in the scrolling after the cleaner succeeded. Worth investigating.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Yeah, sometimes it doesn't fully crash (with system message to close app) it just just returns to main screen or closes the app without finishing the operation or fully deleting junk (open again and toggle all of the things to delete and the number went down but it is still not complete). I did make sure to use the device and pretty much every app intensely to fill up the temp data areas before running it. It is pretty obviously different in how many times it needs to open shells when some of the temp areas have no data. Is the build later today going to the Beta channel or is it another sideload?
[Android Software/Hacking General [Developers Only]] Lennoard:
I think I can publish it in the regular Beta channel with some adjustments.

Edit: It will take some more time.
[Android Software/Hacking General [Developers Only]] sliding_billy:
No hurry.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Is there something wrong with the update that pushed to the Beta channel yesterday? I took it as an update to the test version on one device and although it installed it did nothing when I tried to open it. Rebooted the phone and the notification showed up that changes were applied. Tried opening it again. Still nothing. Uninstalled and reinstalled from the app store (so the Beta). Nothing thing. Tried installing the test version which would not install (since there was a newer version in place). I uninstalled and then installed the test version which installed and opens. I just needed to reset all of the settings since I had to uninstall everything. Now, that device along with all the others has a pending play store update waiting. Thankfully, I have automatic updates turned off in play store on all devices.
[Android Software/Hacking General [Developers Only]] Lennoard:
Fixed.

It should be up in ~2 hours.

Edit: it was a bug in the splash screen, you can skip it using luncher shortcuts if you are not sure your devices got latest update.
[Android Software/Hacking General [Developers Only]] sliding_billy:
I only did the one device and I can wait until the fixed one is up since I have already reverted to test. I didn't even think to long press it, but good idea. I almost never use the launcher shortcuts in apps.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Got the new beta installed all around (build 130). Everything is looking good. I saw a deprecated option under advanced, but it wasn't anything I was using so no big deal. Does this build turn off the deep logging?
[Android Software/Hacking General [Developers Only]] Lennoard:
Nice :good:

Shouldn't it be 131? :confused:

We will remove the Sysctl option in HEBF soon, it wasn't really being used. For those who actually use this option, I am developing a separated, more complete open source app that we will eventually redirect users to

I forgot to mention. It's optional (and disabled by default). You can opt-in in the app settings. The output of "debug" ( [D] ) level logs will not be redirected to the app's private folder.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Definitely v2.2.8 b6 130. I actually just did the T713 since the device was off earlier and confirmed in settings.

Sysctl was definitely the deprecated one I saw. Too much trouble for most users to get into.

I see the 'enable extended logging' toggle now. Perfect. I will know for sure if the cleaner still exhibits any lags/crashes when I run it overnight (especially on the 3XL since I will have filled up the temp files by then).

Thanks for getting these changes close to prod already.

[MENTION=6652564]Lennoard[/MENTION] - The cleaner issue was definitely being caused by the verbose logging. Running it on all 5 devices last night without turning the extra logging on has no crashes and immediately showed that it was complete and very quickly refreshed the page showing the new zero to be cleaned next to the appropriate areas. It does seem to be doing more cleanup than the prod version or earlier beta for sure but not to the detriment of performance.
[Android Software/Hacking General [Developers Only]] Lennoard:
Production-ready flag perhaps?

I'll make a last beta for the v2.2.8 only with coroutines replacing thread allocations when possible and to inform users about Sysctl.
[Android Software/Hacking General [Developers Only]] sliding_billy:
I don't think it impacts prod at all. It notes that it is for testing purposes, and that was exactly what it did. Maybe if it wasn't in such an easily accessible place like general settings but was in advanced or only accessible in Chuck Norris with a detailed risk or crashing beyond just slowdown. Short answer to me is if you aren't willing to capture a log and properly test, don't use that function.
[Android Software/Hacking General [Developers Only]] Lennoard:
v2.2.8 Released. Codename: Viena

Changelog:

Viena

Updated LMK profiles

Added confirmation dialog to Window Manager

Added reset notification to Window Manager

Added boost button to Game Booster notification

Added do-not-disturb mode to Game Booster

Added custom LMK profile to Game Booster

Added extended logging option (for level 3 users, optional)

Fixed app crashes in older Android versions

Fixed app theme in older Android versions

Fixed Game Booster and VIP Battery Saver not stopping apps (root)

Fixed bugs while reapplying changes

Removed Scripts Runner

Removed Sysctl (see here)

App will no longer doze-whitelist itself upon install :good:

Using Kotlin Coroutines

Download:

Android File Host | Google Play
[Android Software/Hacking General [Developers Only]] sliding_billy:
[MENTION=6652564]Lennoard[/MENTION] It looks like the app has disappeared from the Google Play Store. I noticed that it wasn't in my Beta list, and I looked at the store to see it gone completely.

---------- Post added at 05:38 AM ---------- Previous post was at 05:38 AM ----------

[/COLOR [MENTION=6652564]Lennoard[/MENTION] It looks like the app has disappeared from the Google Play Store. I noticed that it wasn't in my Beta list, and I looked at the store to see it gone completely.
[Android Software/Hacking General [Developers Only]] Lennoard:
oh, rip... ?

It seems like Google don't want any paypal there.

That's fair. I have removed it in 4 releases ago but I managed to miss (forget) one "paypal" button in a separated layout that might have been caught, that button does nothing by the way, crying out loud ?

I'm submiting another version for review soon. It should be up quickly after that, Google did not raise its ban hammer upon us yet.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Yeah, they are good like that aren't they? ;)
[Android Software/Hacking General [Developers Only]] sliding_billy:
Just an FYI... I upgraded the Pixel 3 to Android 10 yesterday, and everything is working as before. No update for the Pixel 3 XL since I am running Havoc on it at the moment. HEBF is also working as designed on Havoc. I don't know if you have anything in HEBF that modifies system (nothing I have seen or used), but that is a no-go on 10.
[Android Software/Hacking General [Developers Only]] Lennoard:
Thank you, HEBF is not targeting Android 10 ATM, there are too many things to adjust, especially regarding storage. I should address these as soon as I put my hands into a rootable Android 10 device.
[Android Software/Hacking General [Developers Only]] sliding_billy:
Let me know if you need anything looked at.
[Android Software/Hacking General [Developers Only]] SkylinesHD:
Love this app!

So great and it has features i never knew exists.

Any possibility to add a feature that makes wifi prefer 5ghz?
[Android Software/Hacking General [Developers Only]] Lennoard:
Thank you. I'll see what I can do. Right now I'm in an awkward position where I can't use my tools but as soon as I can I'll look for it.

Also [MENTION=4609886]sliding_billy[/MENTION] I got a "working" Android 10 GSI and I'm ready to start working on making the app target API 29 and use the newer platform standarts. Form what I've seen, I'm definitely not a big fan of those lol
[Android Software/Hacking General [Developers Only]] sliding_billy:
Good luck. Looking at the behavioral changes and target API requirements, it appears to be a mess from the dev side.
[Android Software/Hacking General [Developers Only]] Lennoard:
New design

Here's how the app will look like now, also I plan to merge more layouts into a single "card" to improve rendering time.

Not shown here but as for Material specifications, dark themes shouldn't be fully black so that it keeps an "elevation" effect, to address that, cards in AMOLED theme will now have a white border.

Android 10 auto theming will likely be supported too (Dark/Light mode => Light/AMOLED theme)
[Android Software/Hacking General [Developers Only]] El_Diabolical:
Have you guys considered a collaboration with Jeekos Pure Performances Stock ?...

I want to try this out but it may conflict with it.

Maybe a merge patch file [emoji848]
[Android Software/Hacking General [Developers Only]] Lennoard:
When it comes to conflicts, you just need to be aware of what you are activating in both applications, and then make sure you do not enable two equivalent options. HEBF does explain (usually) just below any option. It's been a long time since I've been turning this app into a root toolbox rather than a "tweaking app".
[Android Software/Hacking General [Developers Only]] El_Diabolical:
Ok I'll make a backup and give this app a go ...

I'm to eager ,When in doubt....BACKUP [emoji38]
[Android Software/Hacking General [Developers Only]] Lennoard:
v2.3.0 beta 1 released

Beta changelog:

Codename: Emma

Design updates

Auto dark mode theme (Android 10+)

Improved VIP Battery Saver scheduling instructions

Added Prefer 5GHz wifi band

Pagination in public configurations screen

[MENTION=7761545]SkylinesHD[/MENTION] I'm unable to test 5GHz, could you please help me?
[Android Software/Hacking General [Developers Only]] El_Diabolical:
Ooooo Nightly Builds,You guys stay busy [emoji57]
[Android Software/Hacking General [Developers Only]] SkylinesHD:
sure if i can save my settings somehow.