yashsingh1/xdaforums huggingface dataset:
[L Speed] FraggleRockBoy:
Fatal exception

Hi Paget96!

I tried to send from app, but don't have an email app set up.

Bug report:

I just updated to the newest version from github via the in-app update available prompt. The previous version I updated from was 2.12 beta 2. Since I updated to the previous version in Dec 2019, I have been getting the message at app opening "Fatal exception. Please check LSPEED log. " Any version prior to that was issue free. This error message is still present with latest version as well. I did notice after installing latest version that older app wasn't replaced and that both old and new versions were installed. I uninstalled old version, but error message still appears. Keep up great work on this phenomenal app! God bless!

Samsung Galaxy S4(i337)

Goldeneye 53 XXUHOD7 Lollipop 5.01 (XDA's own IB4STiD's ROM)

L'Speed STABLE 2.1.4

Logfile(am newer member so not able to add attachments to post):

[16:41:03:765 25-03-2020] Activating battery improvements...

[16:41:03:824 25-03-2020] LCD power reduce enabled

[16:41:03:843 25-03-2020] Battery improvements are enabled

[16:41:03:861 25-03-2020] ===============================================

[16:41:03:972 25-03-2020] Enabling gaming RAM manager profile

[16:41:04:904 25-03-2020] Background app limit=22

[16:41:04:955 25-03-2020] adj=0,112,224,408,824,1000

[16:41:04:999 25-03-2020] minfree=6912,9216,18432,32256,50688,69376

[16:41:05:016 25-03-2020] min_free_kbytes=3252

[16:41:05:036 25-03-2020] Gaming RAM manager profile for 1807mb devices successfully applied

[16:41:05:052 25-03-2020] ===============================================

[16:41:05 25-03-2020] Enabling CPU multicore power save...

[16:41:05 25-03-2020] Multicore power save enabled

[16:41:28:110 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[16:41:28:110 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[16:41:28:110 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[16:42:23:848 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[16:42:23:848 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[16:42:23:848 25-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
[L Speed] Paget96:
Hello, please get the beta from the latest post on main thread (the latest post)

I think it'll work fine now :)
[L Speed] FraggleRockBoy:
Fatal exception persists

Paget96,

Thanks for the quick response. I

updated to the latest version 2.15.1 beta1, but the fatal error message still appears. I installed, rebooted, as well as checked Android application permissions to make sure L Speed wasn't restricted, all available permissions(including Modify Settings) were enabled, but the message still appears.

Logfile:

[11:05:33:418 28-03-2020] Activating battery improvements...

[11:05:33:517 28-03-2020] LCD power reduce enabled

[11:05:33:548 28-03-2020] Battery improvements are enabled

[11:05:33:571 28-03-2020] ===============================================

[11:05:34:329 28-03-2020] Enabling gaming RAM manager profile

[11:05:35:979 28-03-2020] Background app limit=22

[11:05:36:024 28-03-2020] adj=0,112,224,408,824,1000

[11:05:36:078 28-03-2020] minfree=6912,9216,18432,32256,50688,69376

[11:05:36:103 28-03-2020] min_free_kbytes=3252

[11:05:36:128 28-03-2020] Gaming RAM manager profile for 1807mb devices successfully applied

[11:05:36:151 28-03-2020] ===============================================

[11:05:36 28-03-2020] Enabling CPU multicore power save...

[11:05:36 28-03-2020] Multicore power save enabled

[11:05:54:256 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[11:05:54:256 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[11:05:54:256 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[11:12:11:692 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[11:12:11:692 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS

[11:12:11:692 28-03-2020] Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
[L Speed] Paget96:
What version do you use??
[L Speed] FraggleRockBoy:
Version of OS? Phone?

Android 5.0.1 based Goldeneye ROM ( IB4STiD's from XDA developers)

AT&T Samsung Galaxy S4 (Sgh-i337) / MDL locked bootloader

Hope this helps.

Thanks in advance!
[L Speed] Paget96:
I will do some checks.
[L Speed] kryoisme:
Samsung Galaxy J2 Core / SM-J260G

Android One 8.1.0

L Speed >= v2.1.2 stable

Since v2.1.2, L Speed isnt responding when I open the app, although previous versions work well for me
[L Speed] Biphuc152009:
Samsung galaxy a6 2018

JynxPure 3.0 - Exynos 7870 | Android 10

Stable

After applied the tweaks,my clock stop automatically update time,please help
[L Speed] zputnyq:
Give it a try for more than one reboot, if it doesn't fix try clear L speed data in setting -> app & re-setting it then reboot.

Hope it could help
[L Speed] Paget96:
Disable cleaner on boot, i think should be fine :)
[L Speed] ponemania82:
because the cpu section changes, although I change the governor tuner, the latter remains the same?

All this on my honor 7
[L Speed] looney_tkp™:
Govtuner doesn't change CPU governor, rather it makes changes to governor tunables of your selected governor.

if you use a kernel tweaking app like kernel adiutor

1. disable govtuner and reboot

2. after reboot check your governor tunables in the kernel tweaking app(eg. kernel adiutor), it's advisable to take a screenshot so u don't forget the tunables and also to refer to verify the changes

3. open l speed && select your desired govtuner profile

4. open the kernel tweaking app(eg. kernel adiutor) again and verify the tunables, refer to your screenshot incase you forget the stock tunables and verify if it's working

this is a CPU governor (govtuner doesn't change this, you make that change yourself)

&& this is the governor tunables (this is what govtuner makes changes to, so check here after you have followed my tutorial to check if it has changed or not)

if you are still confused, let me know...i'll explain better in a pm

Sent from my Nexus 5
[L Speed] LazerL0rd:
I'm guessing the dev will have to add a feature like Naptime's to revert back your settings.

---------- Post added at 12:59 AM ---------- Previous post was at 12:48 AM ----------

Yeah, I'll make a list tomorrow morning but it's just a random set of prop lines that don't set. I think it's the ones that weren't originally in my build.prop so I manually added them. Example after enabling RIL Tweaks:

#: getprop ro.ril.enable.a53
#:
#: setprop ro.ril.enable.a53=1
#: getprop ro.ril.enable.a53
#: 1

And so, it didn't work. I then manually typed it in to the build.prop to save it. Quick question: after an OTA do I have to set the tweaks again, or does the automatic set-at-boot just do it for you?
[L Speed] Paget96:
It already re-enable them :)

Internet is full of useless lines, i also see that people still adding them to own apps and mods.

Make a list tomorrow, we will discuss. ;)

Also you don't have to re-tweak. After devices boot, LS will start and set them up.
[L Speed] ponemania82:
thanks for the explanation, I understood the speech. But I ask the developer [MENTION=5514152]Paget96[/MENTION], since you have created a fantastic application, why not enter this option to change the governor? in such a way as to have a one unit without having to download a different application for this task. Thanks for the attention
[L Speed] Paget96:
It's job of kernel adiutor ;)
[L Speed] anjel05:
im having lag and random fc in game offline after updating to new build with net tcp + tweak

android version: 5.1

Rom: flare excite prime(local brand Philippines)

lspeed setup: cant upload photos i set it up to performance(enabled all except fast boot) cache reclaim doubled , oom killer and cache allocation default

thanks more power
[L Speed] Paget96:
Force close in games are not related to net tweaks, you can have a lag, but not fc.

Try build uploaded hour ago
[L Speed] veez21:
Set profile to balanced, and try turning oom killer to disabled, and cache reclaiming to default
[L Speed] Paget96:
Cleaner bug, debugging thread opened

https://xdaforums.com/apps/l-speed/cleaner-bug-execution-stuck-boot-t3564842
[L Speed] ash001:
I think aggressive doze is broken in latest beta..

Anyone else experiencing this?:eek:
[L Speed] Paget96:
What kind of problem, describe it :)
[L Speed] ash001:
It's taking more time to kick into doze.almost 5minutes
[L Speed] Paget96:
Pushed small change on play, will be available in 10mins ;)

Thanks ;)
[L Speed] Jyjieng11:
I don't know if anyone else is experiencing this. I have Greenify Aggressive Doze on and when I activate L Speed Aggressive Doze as well I think it breaks my ambient display. On Lineage OS with the Moto X Pure. Dont know if its a bug or not but I thought I would mention it. Great app btw :)
[L Speed] xdarkstar:
Use aggressive doze of one app only both work same
[L Speed] mittalanmol22:
So i enabled fstrim and there are 2 problems i noticed.

1. In log it shows 24 mins instead of 24hrs

2. Then after checking logs i again checked fstrim and it disabled itself
[L Speed] ash001:
Iam also experiencing this
[L Speed] Dims_Camper:
me too, also, once i saw a blank toast after applying new inteval tweaks. i saw it only once tho.
[L Speed] Paget96:
Empty toast or snackbar?

Here, try this attached APK.

Thanks for reporting. ;)
[L Speed] Dims_Camper:
toast, i'm sure about that
[L Speed] Paget96:
That's happened because of no root :) I mean, root isn't granted at the moment of execution. That's happening with CM root, mostly.
[L Speed] Dims_Camper:
hmm makes sense, i'm using magisk atm
[L Speed] Paget96:
In my opinion SuperSU is still the best one.
[L Speed] mittalanmol22:
It's all working good now:)
[L Speed] Paget96:
Good, thanks for testing :)
[L Speed] Dims_Camper:
i'm using magisk due some things, anyway, thanks for the reply..
[L Speed] DB126:
Minor bug w/beta9: no pop-up info panel for Boost Scheduler.
[L Speed] Paget96:
Try this one ;)

https://xdaforums.com/showthread.php?p=71408518

Added already.
[L Speed] DB126:
Same build I was running; problem persists. Other pop-ups working fine. Not a big deal...reporting FYI.
[L Speed] Paget96:
Ok, thanks, no problem, i didn't merge the changes ;)
[L Speed] holymoz:
model asus ze551ml

android stock mm 6.0.1

lspeed stable 1.4.8. and previous

net tcp tweaks seems to "weakens" the data connection (not wifi it seems, not sure), so navigation interrupts or become slow and I have to reboot phone to make work again.

this only happen when enabling this tweak but not suddenly, it happens at some point dont know when.

before I tried this tweak when you add it and do the same.
[L Speed] Paget96:
Ok, thanks for report, I'll check where is a problem, and will give few versions to test, stay tuned. I'll quote you in post ;)
[L Speed] Paget96:
Take a look :)

https://xdaforums.com/apps/l-speed/net-tcp-tweaks-bug-problems-data-t3576280
[L Speed] Skull97:
This is just a minor bug. How to reproduce: press wipe battery stats and quickly go to other sections (eg: dashboard), the app will be forced close.
[L Speed] Paget96:
Fixed for next beta release ;)

Thank you :)

Edit: [MENTION=7248227]Skull97[/MENTION]

Try it :)

https://xdaforums.com/showpost.php?p=71648547&postcount=26563
[L Speed] DB126:
Evidence L Speed govtuner works...and possible problem report with 1.4.12.

After updating to 1.4.12 allowed device to reboot as recommended. Couple hours later notice active drain rate was 2-3% above established norm. Quick check revealed govtuner settings were not applied even though log said they were. A quick toggle between disabled and battery fixed problem. Refresh interval is set to (2) hours but normally my device retains whatever settings are applied at boot. First time this has ever happened.

Schedule tuner settings and all others did get applied correctly at boot. Will continue to monitor and report as needed.
[L Speed] Paget96:
Ok, waiting :)

Thanks for reporting.
[L Speed] Paget96:
Please check.

https://xdaforums.com/apps/l-speed/bug-app-cache-junk-cleaner-crash-t3595144
[L Speed] DB126:
Same thing happened after updating to 1.4.13-beta2 and then rebooting. LS log reported govtuner battery profile had been applied but stock settings persisted until manually applied from LS (toggling to disabled then back to battery). LS delay is set to 30 sec to allow device to stabalize after boot before applying LS tweaks.

Another user reported similar behavior [url="https://xdaforums.com/apps/l-speed/tweak-l-speed-v1-0-02-02-2015-t3020138/post72029877]here[/url].
[L Speed] Paget96:
Does L Speed runs after KA and other kernel manager apps?
[L Speed] DB126:
Yes, it does. There is actually a 15-20 sec 'quiet' period after booting between the time EX Kernel Manager and other boot activity completes and LS runs. Strange as everything appears to be ok - just nothing happens - at least with regard to applying governor tunables. All other LS settings are applied as instructed.
[L Speed] Paget96:
Good, will do a check tomorrow morning :)

Check other mention on main L Speed discusion
[L Speed] DB126:
After several more reboots I can confidently confirm LS govtuner settings are not being auto-applied on boot (see prior posts for background/context). This behavior began with 1.4.13 beta1 and continues with beta2. The settings are easily applied from within the LS app.

This fault is not a big deal for me as I can easily clone the settings in a kernel manager and have them applied at boot using that tool.
[L Speed] Paget96:
Will take a look. Try one more thing, set interval to 3 mins, and change governor to Ondemand if you are using interactive already. After that, wait for few mins and check parameters does they changed. Also it will be really nice if you can provide me a screenshot of SuperSU log, when GOvTuner scheduler works. I have to check something.

Try an apk from here also:

https://xdaforums.com/apps/l-speed/bug-governor-tuner-applying-parameters-t3597274
[L Speed] DB126:
Feedback (bulleted for efficiency):

- updated beta2 build from linked thread made made no difference

- switching to ondemand govonor (interval still a 2 hours) made no difference

- setting interval to 3 min with interactive govonor DID WORK; parameters were not set following boot but were sucessfully applied after expiration of the first interval (~3 minutes after boot)

- on my primary device I use the root manager integrated into the ROM; it isn't immediatlely apparent if logs are maintained. It does show L Speed has root permissions with the time of last execution properly shown (± a few seconds).
[L Speed] Paget96:
When the device boot, you have to wait 3 mins, because of the scheduler. If that works, we are ok, just use build from this thread and comparr with beta 2
[L Speed] DB126:
Ok - let me test again waiting a few min before checking. I actually like that design as there is no hurry in applying govonor tunings after boot. Better to allow the device to stabilize after working through all the other boot activity (minimal on my device but not everyone has such a clean house; I'm kinda anal around limiting startup bloat).

---------- Post added at 09:35 PM ---------- Previous post was at 09:02 PM ----------

Unfortunately, did not work. So far only setting interval to 3 min within LS app allows settings to be automatically applied shortly after boot. Confirming I did install the updated 1.4.13 beta2 LS app from linked thread
[L Speed] mittalanmol22:
Boost scheduler doesn't work.

Or at least doesn't notify :/

Using 1.4.13-beta2
[L Speed] Paget96:
Guys, try beta3 ;)

I hope problems are resolved :)
[L Speed] martyfender:
Nextbook Ares 8 Intel x86 Baytrail tablet

Android 5.1.1

After some hours of very intermittent use of my tablet, I did see another toast for boost. So it appears that boost scheduling is working in the alpha build. Trim scheduling appears not to be working, unless it is not updating the trimlog.

I had enabled trim on boot, before the last reboot and the trimlog has the of that time, 7 hours ago. Also posted in the test beta thread. should I be posting here from now on for bug reports? I see that you closed the alpha thread.

Thanks
[L Speed] martyfender:
UPDATE: Apparently scheduled trim is working. I just saw a toast flash on the screen very, very quickly. Sorry I missed it earlier as it is brief. In KA and Apps2sd, you can set the interval in seconds, of the toast message. I think a persistent notification might be better, unless it causes other issues.

Thanks
[L Speed] DB126:
Would rather not see persistent notifications for any reoccurring event unless there is an option to disable (event/category specific; not an app level block).
[L Speed] martyfender:
Yea, I think you are right, now that we now know that the scheduler options work.
[L Speed] martyfender:
Hi, I didn't install any of the three test builds you released about a week ago, but I believe the two I/O options I enabled were the cause of my lag that I noted in the swappiness test thread, which is now closed. After testing swappiness at 40 and 60% and zram swap size of 250mb, I reverted back to the rom default of 100% swappiness and 400 mb, both for zram. It is very hard to tell, but I think the default is better in my case.
[L Speed] Paget96:
Good, use defaults then ;)
[L Speed] martyfender:
I would like to report that the latest beta version of lspeed is working very well with my device, with no known issues.

Thanks!
[L Speed] zputnyq:
I have 2 problems on my device

1.Start page option

Getting loop on start page option after choosing dark and / or amoled theme, L Speed can't reach its finish tab but choosing light theme it's ok. It happens since 1.4.13 beta 4 untill alpha 20170516

2. Restrict system update

Actually I'm not really sure what causes it but restrict system update can't stick on my device.

I check my device related function, I saw that systemupdate service in google service framework is disabled by default but system update service & system update gcm task service are enabled in google play service.

Overall it's nice, thanks for your hard work mate

I really appreciate it :)
[L Speed] DB126:
Similar observations here, re: item #2
[L Speed] zputnyq:
Yes also the same here & its slider too.

It seems google won't let it be disabled even I have tried disabling it using MyAndroid tools, its non active/disable state is last min only for a few hours, max for a few days but idk for custom google play service.
[L Speed] DB126:
Google Play Services reenables disabled components on a periodic basis. That behavior can be blocked via MyAndroidTools Xposed extension. However, it's not a granular solution impacting every service, broadcast receiver and activity under the Google Play Services umbrella. So far this has not yielded noticeable side-effects for me but a few data points across several devices doesn't necessarily reflect outcomes for the larger community. I would use caution with this approach (using MyAndroidTools Xposed to 'freeze' Google Play Services enable/disable settings).
[L Speed] zputnyq:
Yes, I see it.

Thanks for this nice info :)
[L Speed] martyfender:
I would like to report that the last two beta versions of lspeed, 1.4.13 beta 5 and beta 6 have been working well on my Nextbook Ares 8, Android 5.1.1, x86 tablet. There are no issues I am aware of, however, I am not using any of the new features, either.

I prefer grainularity in settings, so, for example, I use KA for vm and some other settings because I can see exactly what settings are changed.

Furthermore, the op has not been updated to revise what each setting does.

Is there a way, with a root file explorer view where changes are made so I can see the exact changes that are made. Obviously some changes made in lspeed can be seen in KA. The only change that I know the location of changes is the govtuner: /sys/devices/system/cpu/cpufreq/interactive/.

At the very least, when you have time, would you be able to update the op with what each tweak does and remove the ones no longer in the app?

Thanks
[L Speed] DB126:
Have to second this comment while recognising many users favor one button simplicity and never read supporting documentation. Lack of granularity and transparency on recent additions serve as the greatest obsticles toward broader personal use and recommendation to various communities. OP really needs to be updated.
[L Speed] Paget96:
Thanks for this.

Logging in L Speed will be updated, so everyone can see what's changed, and tweak explanations will be removed since we have one inside the application.
[L Speed] DB126:
Excellent - thank you!
[L Speed] kchaisu:
Hi Paget96,

Yesterday, after I got your PM concerning boot loop on my device, HTC Desire S, Saga, RAM 768 MB, Lineage OS -13 sagaopt. I download the cGroup test version and got boot loop as well, Probably, I download the same copy of build because I just downloaded and installed the test version prior to PM you about resulted in boot loop. My suspect was CPU tuner section which was turned on the beta version.When updated to the test version still turned on by default of L speed update function. Thanks for you and your team kind commitment.
[L Speed] kchaisu:
The latest beta today build is working for me. Thanks.
[L Speed] Alexurso:
Good night friends!

After installing this new version 1.4.12, my screen is not blocking automatically. What could it be? Is there a wrong configuration? Could anyone give a detailed explanation?

Thank you.
[L Speed] Paget96:
I don't understand what's happening with your screen?
[L Speed] chuootj:
I think the problem is related to the "Aggressive doze" option, you should try to turn off that option.
[L Speed] Paget96:
You mean screen lock don't working?
[L Speed] chuootj:
Yes, it appears in version 1.4.12, and the first beta versions of 1.4.13. However, the latest beta version fixes that problem.
[L Speed] Paget96:
Good. :)
[L Speed] Alexurso:
Not a Aggressive doze problem.

I did another setup following the advice of a friend and solved the problem.

But the Aggressive doze are still connected.

Version 1.4.13 also presented this same problem. It must be some incompatibility of some feature. I do not know what it can be.

Follow the video link with the configuration that gave problem:

https://www.youtube.com/watch?v=KG91qEPmfEg
[L Speed] Paget96:
New version is on the way, expect some new stuff and again, a video on youtube ;)

Thanks for reporting :)
[L Speed] kchaisu:
Hi Paget96,

I got boot loop on RAM Manager test. Thanks.
[L Speed] Paget96:
Mmm, I'm not sure it's possible. Device can work with disabled LMK at all.

It can be your ROM last update if you are on Lineage nightly. :)

Can you please screenshot the LMK values you get on balanced ram profile with the testing apk 1.0
[L Speed] kchaisu:
The only Lineage OS-13 I got is a snapshot, so there is no thing change on the ROM.

When I updated to testing apk 1.0, then it rebooted and hang on Lineage OS forever. So I am going to reflash ROM and Gapps and start over again.

So I do not know how to LMK values. and it is going to be after finishing set up my device. Thanks.

If it is only me who report this issue, please ignoremy aged device. Thanks.
[L Speed] Paget96:
That's why I'm saying there is no chance to bootloop, parameters set up after devices boot :)
[L Speed] kchaisu:
It might be the ROM itself. Thanks.
[L Speed] Alexurso:
Ratifying, really what is preventing the screen from getting stuck after it is turned off is Aggressive doze.
[L Speed] Paget96:
Yes i know that. :)
[L Speed] veez21:
[MENTION=5514152]Paget96[/MENTION]

If you install l speed for the first time/wiped data, you'll get into the starting page and if you change your theme from there, it'll go back again to the "Get Started" page ?
[L Speed] Paget96:
It's fixed in some of the experimental/test builds. :) Not yet pushed on playstore.