Database Users

System Killing Launcher on every app launch!!

Hi!! I have a problem, I'm currently Running Darky's 10.1 with dark core 2.6... Everything is smooth and snappy, however the system keeps killing my launcher everytime I launch an application whether it be a game, browser, news app... Whenever I exit the app the launcher reloads and it makes the phone really really slow and laggy for 10-15 seconds...
I currently using ZEAM launcher, not sure whats causing this, i've been using this launcher since its launch and only had this problem when i was on stock froyo...
Any ideas what can be done to fix this issue...
Thanks!!

Same problem here.
I am on GigerReal 7.1.3 and the worse thing is when it you try to make a phone call and the bloody thing just restarts the phone every third key pressed.
I can only call using voice calling when this happens...
I am using LauncherPro but it also happens in Ginger Launcher and TW Launcher 4.5

Just out of interest guys, how much free memory is showing for you in Settings > Applications > Running Services ?
I am running stock JVQ and although the phone works fine after initial boot (with around 180mb free) this number seems to drop over time and results in any new application clearing any other app from the memory. This even meant that if I got a text message while using the web browser and replied to it, by the time I went to return to the browser it had to reload where I was from scratch. It was also clear that after playing a game and returning to the home screen, even this was having to reload and "redraw" again.
That in itself is a minor annoyance but eventually it seemed to get so bogged down the whole system froze with the "black screen of death" and I had to do a forced reboot. I'm aware, of course, that JVQ is not an official release so it's not fair to be too harsh on Samsung here...

I seem to have a lot of memory free. It happens after the phone has been up for some time.
I noticed that launcher pro was reloading the widgets every time it starts. Also i seem to notice that it happens when you dial a couple of numbers and it starts giving you suggestions from the contacts. So it could be contact related?

Tepes4 said:
I seem to have a lot of memory free. It happens after the phone has been up for some time.
I noticed that launcher pro was reloading the widgets every time it starts. Also i seem to notice that it happens when you dial a couple of numbers and it starts giving you suggestions from the contacts. So it could be contact related?
Click to expand...
Click to collapse
This is the same that happens on my system... The launcher just reloads all the widgets everytime I close an application... the amount of ram is always close to 243/337.. So its close to 90-100 mb free, which is enough i suppose... Still the launcher just reloads everytime an app is closed... Its really getting annoying...

basicly you must set HOME_APP_ADJ to 0 making home app unkillable =)
am not sure but probably do that
/data/local.prop -> add such line ro.HOME_APP_ADJ=0
and restart - have not tested just pure theory (the .prop location)

$omator said:
basicly you must set HOME_APP_ADJ to 0 making home app unkillable =)
am not sure but probably do that
/data/local.prop -> add such line ro.HOME_APP_ADJ=0
and restart - have not tested just pure theory (the .prop location)
Click to expand...
Click to collapse
Actually, putting the value as 1 worked better for me. My launcher so far has not been killed even once.

ya 1 should work flawlesly
0 is making it bulletproof/unkillable at any state
but 1 should be safest value

I think Spare Parts allows you to adjust the task killer's sensitivity. Maybe have a play with that and relax the settings.

$omator said:
ya 1 should work flawlesly
0 is making it bulletproof/unkillable at any state
but 1 should be safest value
Click to expand...
Click to collapse
Hi Thanks for the advice, however i'm not sure how to set these values, Is there any tool that I can use to do that??

psyren said:
I think Spare Parts allows you to adjust the task killer's sensitivity. Maybe have a play with that and relax the settings.
Click to expand...
Click to collapse
spare parts at least free one does not have such option
also this is not about adjusting memory taskkiller options
not the one that you can setup with this useless juwe script for example
different thing
exjc1986 said:
Hi Thanks for the advice, however i'm not sure how to set these values, Is there any tool that I can use to do that??
Click to expand...
Click to collapse
never came across one

exjc1986 said:
Hi Thanks for the advice, however i'm not sure how to set these values, Is there any tool that I can use to do that??
Click to expand...
Click to collapse
Attached is an APK which adds that line. Make sure you're rooted first. I wrote it in the past 10 minutes, so it's very simple and might crash, but it did work for me.
Just install it, launch it, confirm root and then watch out for a small message. If successful it will directly ask you to uninstall it. Reboot, and done.

there is also ro.HOME_APP_MEM that can be changed to 4096
to follow other oom_adj=1 settings =)

@martino2k6
Thanks a lot dude... The apk installed perfectly... I'm already seeing improved performance from my device... The launcher hasn't been killed once since the install...
Thanks again for all your help... appreciate it...
Sent from my GT-I9000 using XDA App

http://androidnexus.com/guides/fix-home-screen-redraw-lag-in-launcherpro-and-adw-launcher

Try changing the lowmemoty killer setting to something less aggressive. Your phone is trying to keep too much free memory so has to kill off apps.
Download Galaxy Tuner (using memory manaber option)and set the application cache values to the new samsung default as follows:-
fa=10 MB
va=16 MB
ss=20 MB
ha=24 MB
cp=28 MB
ea=32 MB
Make a note of your current settings in case it doesnt help.
You can also use Galaxy Tuner to set JEWE's file system cache
, settings are:-
SWP: 50
VCP: 10
DEC: 5
DWC: 10
DRA: 90
DBR: 5
These work well for me so give them a whirl, you can always put the values back to where they are now.

mate the problem is solved already - please read dont spam those juwe crappy values ok ?

Ok, cool
Sent using geek power

I cannot thank you enough mate!
There were times i could make a phonecall cause it kept bringing me back to the home screen!
You sir, are a gentleman and a scholar!
martino2k6 said:
Attached is an APK which adds that line. Make sure you're rooted first. I wrote it in the past 10 minutes, so it's very simple and might crash, but it did work for me.
Just install it, launch it, confirm root and then watch out for a small message. If successful it will directly ask you to uninstall it. Reboot, and done.
Click to expand...
Click to collapse

exjc1986 said:
@martino2k6
Thanks a lot dude... The apk installed perfectly... I'm already seeing improved performance from my device... The launcher hasn't been killed once since the install...
Thanks again for all your help... appreciate it...
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Tepes4 said:
I cannot thank you enough mate!
There were times i could make a phonecall cause it kept bringing me back to the home screen!
You sir, are a gentleman and a scholar!
Click to expand...
Click to collapse
You're both welcome. That's what [helping out] XDA is for after all

[Q] issue with app closing (not FC)

Hey everyone
using a atrix 4g
at&t branded unlocked on rogers
running cm7 (CM7 official nightly) using faux123 kernel 1.45ghz
i'm having an interesting issue here... and im not sure how to resolve it, hence why i am make this thread.. i have searched and havent found anything
I use an app call issimo (twitter) now when you open it, it loads the timeline as usual you can do whatever...
my issues is after a certain amount of time, (its random) i try to go back into the app and its like i have never opened it... eg has to load the timeline again and isnt where i left it when i backed out...
it runs in the background just fine, its just there are certain times it does that...
i have set my heap size to 48mbs, and such but nothing is solving this...
the dev seems to think its related to the ROM needing more memory so it just closes the app... and like i said its not force closing... just exits itself.
how can i stop this from happening? anyone have any ideas?
thanks!

Try setting heapsize to 64 mb. Also have u used or has someone else used an app that messes with minfree values, or anything else that may adjust how much memory to keep/ free up?
Sent from my MB860 using Tapatalk

Phalanx7621 said:
Try setting heapsize to 64 mb. Also have u used or has someone else used an app that messes with minfree values, or anything else that may adjust how much memory to keep/ free up?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i have previously set the heap to 64 and the dev said to not as i was having issues with it lagging due to to much in the heap... (idk...)
as for the minfree values and etc you mentioned... i dont think so... honestly i'm still fairly new to the android and the hacking/modding... that being said the minfree value is a new term for me and i dont know what that it, or how to change it lol
thanks for the help so far!

High IOWAIT

The issue started when rotating my Nexus 7 from portrait to landscape mode. I have the lcd_density set to 177, so the homescreen rotates. Today, the homescreen icons started disappearing for 20-30 seconds when rotating. I enabled "Show CPU Usage" in the Developer Options, and noticed that the IOWAIT (blue bar) is really freaking high whenever I rotate. So I connected through ADB, and ran TOP. IOWAIT was shown between 33% and 77% right after rotating.
So I ran "
Code:
echo 1 > /proc/sys/vm/block_dump ; cat /proc/kmsg
" to view what was causing the iowaits. It appears that "launcher-loader" is writing a ton of data.
I am out of ideas of what to do. Anyone have suggestions?

Don't use the dpi change. Just use paranoid android for proper tablet mode.
Sent from my LG-P999 using xda app-developers app

redmonke255 said:
Don't use the dpi change. Just use paranoid android for proper tablet mode.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I don't think the LCD Density is the cause of the IOWAIT. I have been using it at 177 DPI for months.

Maybe it's related to the LAG issue? How much do u have in storage?
I met same and turned out IO performance so poor due to low storage (<3G)

merrywhq said:
Maybe it's related to the LAG issue? How much do u have in storage?
I met same and turned out IO performance so poor due to low storage (<3G)
Click to expand...
Click to collapse
You know, it did get slow once I went under 3 gigs free. However, I have now deleted stuff, and it is back up to 4.7 free, and IOWAIT is still high.
EDIT: I installed the Franco kernel, hoping that would fix the lag issue, but it did not. I am starting to wonder if the flash memory is going bad.

cmbeid said:
You know, it did get slow once I went under 3 gigs free. However, I have now deleted stuff, and it is back up to 4.7 free, and IOWAIT is still high.
EDIT: I installed the Franco kernel, hoping that would fix the lag issue, but it did not. I am starting to wonder if the flash memory is going bad.
Click to expand...
Click to collapse
if you check the LAG thread, you should find once you get below 3G free, it WON'T come back even you free some space, a factory reset does work however.

merrywhq said:
if you check the LAG thread, you should find once you get below 3G free, it WON'T come back even you free some space, a factory reset does work however.
Click to expand...
Click to collapse
Crap. That does not make any sense!
Thanks though, I read through a few pages of the LAG thread, but at 48 pages long it is a lot to catch up on.

Google is already investigating this. Maybe there will be a fix...

cmbeid said:
You know, it did get slow once I went under 3 gigs free. However, I have now deleted stuff, and it is back up to 4.7 free, and IOWAIT is still high.
EDIT: I installed the Franco kernel, hoping that would fix the lag issue, but it did not. I am starting to wonder if the flash memory is going bad.
Click to expand...
Click to collapse
Did u disable fsync?
Installing Franco kernel by itself won't fix the issue. U need to install then disable fsync using the Franco kernel app or a script.

dwang said:
Did u disable fsync?
Installing Franco kernel by itself won't fix the issue. U need to install then disable fsync using the Franco kernel app or a script.
Click to expand...
Click to collapse
Hmm, the kernel said it was disabled by default, so I didn't even bother to check. Lag issue fixed. Just am afraid about this data integrity issue... oh well.

cmbeid said:
Hmm, the kernel said it was disabled by default, so I didn't even bother to check. Lag issue fixed. Just am afraid about this data integrity issue... oh well.
Click to expand...
Click to collapse
It used to be disabled by default, but was changed in a future update to be enabled by default. Can be disabled with a script:
Code:
#!/system/bin/sh
echo N > /sys/module/sync/parameters/fsync_enabled

espionage724 said:
It used to be disabled by default, but was changed in a future update to be enabled by default. Can be disabled with a script:
Code:
#!/system/bin/sh
echo N > /sys/module/sync/parameters/fsync_enabled
Click to expand...
Click to collapse
I ended up just doing it through ADB to test. It feels good to finally have a fast tablet again.

Use pencil or any metal object as stylus on Galaxy S2 [Just like S5/Z Ultra/ Z1]

As you all know, Samsung has made a list of hidden features and one of them is where you can enable a pencil as stylus for you phone. This was USP of Xperia Z Ultra too and was also enabled via root on Xperia Z1.
But it looks like this feature will work on S2 too.
Requirements: [This was tested on SlimSaber running 4.4.2]
Any of the following:
1. Any AOSP based ROM which has the Galaxy S2 device setting included. OR
2. Any Sammy based ROM with Galaxy S2 device setting included (anyone confrim this is possbile?) OR
3. Any custom kernel which has option to change screen sensetivity (someone kindly suggest if this too is possbile)
What should be done? - Basically we need to increase the screen sensitivity
1. Open up the device settings. This can be in the app drawer depending on your ROM or integrated to the system settings. For example, in the in SlimSaber it is under: Settings - Advanced options - Device
2. Go to the "Screen" tab
3. Under "Touch sensitvity" change the value to "10"
4. Now try with pencil or any metal objects and have fun.
To quickly revert to default sensitivity turning off the screen does the job. This could be a bug.
Issues:
1. The sensitivity reverts back to default after screen off. At least in SlimSaber 4.4.2. The value will remain on 10, but i will need to tap on it again manually.
2. This will not work when the device in plugged into charger.
2. You need to go to all the way to the device setting screen each and every time. The screen is hyper sensitive for fingers when it is set to 10.
3. Of course, the screen is not as good as you to write down notes with handwriting like in Galaxy Note phones. But it is kinda cool to show it off.
3. The screen will get dirty Please don't use the phone while having food. Lead is bad for health
Video:
I am not sure whether screen sensitivity option is available for other phones like S3, S4 or other OEM too. If anyone know a way and have tried, let us know in the post.
Have you felt good about still holding on to Galaxy S2 yet?

Discovered so late

Awesome working .. Really appreciated dev works.
Just a question can we use it in stock s2 roms ?

kachrukamble said:
Discovered so late
Click to expand...
Click to collapse
I would not have discovered it if S5 hidden feature list was not announced. I have been using the high screen sensitivity option in AOSP from long time. Who knew it would do the trick

exynoss said:
Awesome working .. Really appreciated dev works.
Just a question can we use it in stock s2 roms ?
Click to expand...
Click to collapse
Yes. All credits go to the CM team who developed the Galaxy S2 device settings back in ICS days. This would not been possible the easy way without their app.
I have not used the stock ROM for a long time. The device settings was an app back in ICS days. Someone can try sideloading the app to stock ROM and see if it works. Or may be any custom kernel has this screen sensitivity feature?

Harsha Raj said:
Or may be any custom kernel has this screen sensitivity feature?
Click to expand...
Click to collapse
Ye right i guess I saw somewhere that screen sensitivey option in Kernel tweakers app. Will search for it

Eureka!!! After 2 yrs of s2 use, u have discovered something in it
Sent from my SM-N900 using Tapatalk

The DeviceSettings app writes the value selected for touch sensitivity to the following file to be picked up by the kernel:
Code:
/sys/class/sec/sec_touchscreen/tsp_threshold
Maybe some sort of scripting utility or tasker could help with rewriting the value to the file when the screen turns on and possibly save you having to go back in to force the update through the app??

AuSSiELaMbChOpS said:
The DeviceSettings app writes the value selected for touch sensitivity to the following file to be picked up by the kernel:
Code:
/sys/class/sec/sec_touchscreen/tsp_threshold
Maybe some sort of scripting utility or tasker could help with rewriting the value to the file when the screen turns on and possibly save you having to go back in to force the update through the app??
Click to expand...
Click to collapse
Thanks for the heads up. I'm no developer. I hope someone can make this, if possible. Tasker plugin app would be a best bet because I think scripts are good only at time of boot.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
Thanks for the heads up. I'm no developer. I hope someone can make this, if possible. Tasker plugin app would be a best bet because I think scripts are good only at time of boot.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I was thinking a little different to a addon.d script I believe Script Manager allows you to save a script then run it via a widget, there are probably other options as well but I remember SManager from using it a longtime ago.
Sent from my GT-I9100 using XDA Premium 4 mobile app

Harsha Raj said:
3. The screen will get dirty Please don't use the phone while having food. Lead is bad for health
Click to expand...
Click to collapse
its graphite/carbon, not lead. its not bad for your health.

AuSSiELaMbChOpS said:
I was thinking a little different to a addon.d script I believe Script Manager allows you to save a script then run it via a widget, there are probably other options as well but I remember SManager from using it a longtime ago.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the app looks like it has many features. Hope someone can make it.
At default 50, my S2 screen has sensitivity issues o occasionally. Even if I decrease the value it's only until screen off.
The Jack of Clubs said:
its graphite/carbon, not lead. its not bad for your health.
Click to expand...
Click to collapse
Apparently my school teacher years back had different opinion. I stand corrected
Sent from my GT-I9100 using Tapatalk

Couldn't find the setting in Carbon Rom, musn't have included it. Too bad.

Pyvesb said:
Couldn't find the setting in Carbon Rom, musn't have included it. Too bad.
Click to expand...
Click to collapse
Maybe you can ask in the ROM thread if its buried somewhere else. Here is the device settings apk link from google search. But it did not install in mine, nor it worked when i side loaded it. https://code.google.com/p/slimics28/downloads/detail?name=GalaxyS2Settings.apk

Tried this one in NeatROM (Stock JB-Based) with Apolo Kernel and it worked, but it's seems too uncontrollable...
I made a script of the tsp_threshold value changing to 10, ran it, and tested my regular ballpen on it (empty, of course) and it worked, but most of the time, it won't detect the ballpen when I tried tapping it to type on a soft keyboard.
But when I do gestures like sliding and dragging, it works, though.
Is it safe to change the threshold to 5? I can't do it because I'm scared I might mess up some sh*t.
And also, I think when observed, that the threshold resets from 10 to 40 (my default) when screen turns off, since when I tried screen-off, then on, the touchscreen won't detect my ballpen anymore, and I have to re-run the script to do it again...

Harsha Raj said:
Maybe you can ask in the ROM thread if its buried somewhere else. Here is the device settings apk link from google search. But it did not install in mine, nor it worked when i side loaded it. https://code.google.com/p/slimics28/downloads/detail?name=GalaxyS2Settings.apk
Click to expand...
Click to collapse
Nope, app doesn't even want to install on KitKat. I'll try asking on the main thread as you recommanded.

souler456 said:
Tried this one in NeatROM (Stock JB-Based) with Apolo Kernel and it worked, but it's seems too uncontrollable...
I made a script of the tsp_threshold value changing to 10, ran it, and tested my regular ballpen on it (empty, of course) and it worked, but most of the time, it won't detect the ballpen when I tried tapping it to type on a soft keyboard.
But when I do gestures like sliding and dragging, it works, though.
Is it safe to change the threshold to 5? I can't do it because I'm scared I might mess up some sh*t.
And also, I think when observed, that the threshold resets from 10 to 40 (my default) when screen turns off, since when I tried screen-off, then on, the touchscreen won't detect my ballpen anymore, and I have to re-run the script to do it again...
Click to expand...
Click to collapse
It's not even as stable as I showed it in the video?
Can you make that script using SManager app? That way the script can work even after screen lock or something. I think this is the app https://play.google.com/store/apps/details?id=os.tools.scriptmanager
And I have no idea what happens when it's set to 5 try it out. Nothing bad might happen.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
It's not even as stable as I showed it in the video?
Can you make that script using SManager app? That way the script can work even after screen lock or something. I think this is the app https://play.google.com/store/apps/details?id=os.tools.scriptmanager
And I have no idea what happens when it's set to 5 try it out. Nothing bad might happen.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
About the video, yes, it's not that stable. But I guess it's the ROM's/Kernel's fault, since it's unstable changing the thresholds, they don't bother fixing it...
As for the script, have a look atTasker for that. When it screens-off, the threshold reverts back to normal (the bug on the ROM, maybe?), right?
Then when you do screen-on, use Tasker and it will automatically run the script, and will change the thresholds to the desired percent...
for the script commands I just created a script file:
Code:
#!/system/bin/sh
#Change Touch Sensitivity Script
#Default Sensitivity is 40 on NeatROM
echo 10 > /sys/class/sec/sec_touchscreen/tsp_threshold
Then put it on /system/xbin, changed it's permissions to 777, then ran it on Terminal Emulator.
To test, run this on your Terminal Emulator:
Code:
$ su
# sh -x /system/xbin/<name of the script>
It must echo your desired sensitivity. Then if all's well, try your pen now...

souler456 said:
About the video, yes, it's not that stable. But I guess it's the ROM's/Kernel's fault, since it's unstable changing the thresholds, they don't bother fixing it...
As for the script, have a look atTasker for that. When it screens-off, the threshold reverts back to normal (the bug on the ROM, maybe?), right?
Then when you do screen-on, use Tasker and it will automatically run the script, and will change the thresholds to the desired percent...
for the script commands I just created a script file:
Code:
#!/system/bin/sh
#Change Touch Sensitivity Script
#Default Sensitivity is 40 on NeatROM
echo 10 > /sys/class/sec/sec_touchscreen/tsp_threshold
Then put it on /system/xbin, changed it's permissions to 777, then ran it on Terminal Emulator.
To test, run this on your Terminal Emulator:
Code:
$ su
# sh -x /system/xbin/<name of the script>
It must echo your desired sensitivity. Then if all's well, try your pen now...
Click to expand...
Click to collapse
The script is working good manually. But I setup a profile on tasker as "screen on" and then the script. But the script won't get executed when screen turns on.
I tried same profile for music and it works well.
Sent from my GT-I9100 using Tapatalk

Harsha Raj said:
The script is working good manually. But I setup a profile on tasker as "screen on" and then the script. But the script won't get executed when screen turns on.
I tried same profile for music and it works well.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Did you check "Use Root" when assigning the script? cause you need too...

Tip: Fix for that constant SwiftKey reloading lag!

Hey guys and girls!
Having put up with SwiftKey and other third party keyboards being intermittently force closed by all 5.1.1 TouchWiz versions, I've managed to pinpoint and disable the culprit. By looking at my logs, I could see that the system closed SwiftKey because it was assigned the lowest score by a Samsung module/add-on/thingy called SPCM. Now, I don't know what manner of witchcraft SPCM used to arrive at the conclusion that SwiftKey was so worthless, but using any of the standard Android LMK switches to keep SwiftKey running (like setting it to -17 or resident in xposed App Settings) had no effect at all.
However, after disabling SPCM in build.prop I haven't had a single reload of SwiftKey or its dictionary. Instead, it always appears immediately like you'd expect on a high-end device like this. Even better, there has been no downsides or ill effects of disabling SPCM and I'm really glad to be rid of this major annoyance!
TLDR;
To fix the SwiftKey lag/delay/reloading, open your build.prop and change the following line (requires root):
sys.config.spcm_enable=true
to:
sys.config.spcm_enable=false
Please report your experiences!

That's interesting. Maybe this also fixes the Android wear app constant reloading too.

dedei said:
That's interesting. Maybe this also fixes the Android wear app constant reloading too.
Click to expand...
Click to collapse
I've got no way of testing that, but I guess it might. Feel free to try it and report back! ?

Hey, thanks for the fix!
Is it safe to disable this?
Will it affect any other applications or the phone's overall performance?

Swiftkey New update in Google play, maybe they fixed the problem
Enviado desde mi SM-G920F mediante Tapatalk

Gaiosan said:
Hey, thanks for the fix!
Is it safe to disable this?
Will it affect any other applications or the phone's overall performance?
Click to expand...
Click to collapse
Nope, as per above, I haven't had any adverse effects at all. Performance is unaffected.
Apop10 said:
Swiftkey New update in Google play, maybe they fixed the problem
Enviado desde mi SM-G920F mediante Tapatalk
Click to expand...
Click to collapse
The problem is not with SwiftKey but with TouchWiz - it also affects other keyboards such as Fleksy and Google Keyboard.

Change applied. All good for now. Thanks!.

Fruktsallad said:
Nope, as per above, I haven't had any adverse effects at all. Performance is unaffected.
The problem is not with SwiftKey but with TouchWiz - it also affects other keyboards such as Fleksy and Google Keyboard.
Click to expand...
Click to collapse
I've never had it once happen to Google's keyboard; only with Swiftkey. Thanks for the fix though.

wvcadle said:
I've never had it once happen to Google's keyboard; only with Swiftkey. Thanks for the fix though.
Click to expand...
Click to collapse
My pleasure! Count yourself lucky, I've had it on Google's keyboard myself and others have reported issues with both that and Fleksy.

Thank you sir !
Yup , is working !

Testing it now, so far so good!

Lol weird I don't even have that in my build.prop.

guaneet said:
Lol weird I don't even have that in my build.prop.
Click to expand...
Click to collapse
Ok. If you're still affected, try just adding the false line and I guess it should work anyway. [emoji4]

After changing the line in build.prop (and a reboo) my multi-tasking just went crazy ! If i open like 6 apps and go to the 7th (just an exemple) it will lag like hell !
Changed back to normal and all went back to normal too with the multi-tasking .. so it must have something related to that or maybe it's just incompatible with my rom/kernel (i'm using arter kernel and crash rom)

on XtreStoLite Deo-Mod Edition 2.3 and Arter97 v5 kernel.
working great and been monitoring for about an hour now.
SuperSwiftkey-5.3.8.37

Thanks! Works like a charm

Fruktsallad said:
Hey guys and girls!
Having put up with SwiftKey and other third party keyboards being intermittently force closed by all 5.1.1 TouchWiz versions, I've managed to pinpoint and disable the culprit. By looking at my logs, I could see that the system closed SwiftKey because it was assigned the lowest score by a Samsung module/add-on/thingy called SPCM. Now, I don't know what manner of witchcraft SPCM used to arrive at the conclusion that SwiftKey was so worthless, but using any of the standard Android LMK switches to keep SwiftKey running (like setting it to -17 or resident in xposed App Settings) had no effect at all.
However, after disabling SPCM in build.prop I haven't had a single reload of SwiftKey or its dictionary. Instead, it always appears immediately like you'd expect on a high-end device like this. Even better, there has been no downsides or ill effects of disabling SPCM and I'm really glad to be rid of this major annoyance!
TLDR;
To fix the SwiftKey lag/delay/reloading, open your build.prop and change the following line (requires root):
sys.config.spcm_enable=true
to:
sys.config.spcm_enable=false
Please report your experiences!
Click to expand...
Click to collapse
hi dear friend on note 4 after upgrade to 5.1.1 i have the same problem an in my build.pro i found this line
sys.config.samp_spcm_enable=true is this the same tool and i will change to false it?

tlf55 said:
After changing the line in build.prop (and a reboo) my multi-tasking just went crazy ! If i open like 6 apps and go to the 7th (just an exemple) it will lag like hell !
Changed back to normal and all went back to normal too with the multi-tasking .. so it must have something related to that or maybe it's just incompatible with my rom/kernel (i'm using arter kernel and crash rom)
Click to expand...
Click to collapse
Yeah, that's weird. Can't tell any difference here at all from before/after. Running Xtrestolite and latest UniKernel. As you can see, it seems to be working for others running arters kernel, so either it's a fluke or something's up with that config of yours. If you decide to try again, with or without a different setup, please let me know.
SUNUN said:
hi dear friend on note 4 after upgrade to 5.1.1 i have the same problem an in my build.pro i found this line
sys.config.samp_spcm_enable=true is this the same tool and i will change to false it?
Click to expand...
Click to collapse
No idea mate, but I'm guessing it should work the same. Try it and find out! If it doesn't work, you could try adding our S6 line too. And again, please report back. [emoji106]

Fruktsallad said:
Yeah, that's weird. Can't tell any difference here at all from before/after. Running Xtrestolite and latest UniKernel. As you can see, it seems to be working for others running arters kernel, so either it's a fluke or something's up with that config of yours. If you decide to try again, with or without a different setup, please let me know.
No idea mate, but I'm guessing it should work the same. Try it and find out! If it doesn't work, you could try adding our S6 line too. And again, please report back. [emoji106]
Click to expand...
Click to collapse
Looks like its works. After applying about 2 hours it not killing from memory viber and my watchfaces.

SUNUN said:
Looks like its works. After applying about 2 hours it not killing from memory viber and my watchfaces.
Click to expand...
Click to collapse
Thanks, good to hear! Did you change your own line or did you add the S6 one?