Related
Hello. It seems like my phone kills swiftkey from time to time. And that makes my phone seem slow when it has to reload it. Any way to keep it in memory? Have to use Samsung keyboard for now... :/
Sent from my SM-G928F using Tapatalk
same situation
just torn off emoji prediction!! it's a bug from swift keyboard
ralmeidao said:
just torn off emoji prediction!! it's a bug from swift keyboard
Click to expand...
Click to collapse
Thanks but that was already off unfortunately.
Sent from my SM-G928F using Tapatalk
mm works for me
Sent from my SM-G920I using Tapatalk
I don't have this kind of problem but I never used emoji prediction. In which language do you use it ? Maybe related to the language?
same here with Swype keyboard @Sgs6
It really seems that it gets kicked off from memory after some time. Is there any way to force it kept in memory?
I don't use emoji prediction either. And I do not have any lags on the keyboard at all!
I'm using UK English, i face randomly shut down swiftkey and other third party keyboard too. I used to owned S6, after upgraded to 5.1.1, problem started to occur... now having same problem with S6 Edge Plus. Sad...
same here (only with swiftkey) on sony z ultra on 412 (cane be bothered updating yet).
emoji etc off. only happened a few updates ago. typing away and keyboard randomly closes. after waiting 30 seconds and repeatedly clicking in text area the keyboard pops back up and works for a while. reboot and same behaviour, same if wipe data etc.
might try wiping data and unlinking from my acc. if not that IMO has to be the app as OS hasn't changed (rooted and no OTA updates).
I ditched Swiftkey because it seems laggy and slow for me. With other keyboards I have no problems.
It's a bug of SwiftKey since 5.4. I have reported it several times with explinations, screencasts etc. They simply refuse to aknowledge they screwed up the app. So I'm using samsung keyboard, which, by the way, uses Swiftkey SDK.
Did you look at the App Optimization system? I have disabled Swiftkey there, to avoid having the system closing it after a certain time, and everything seems to be ok for now.
I noticed it lags a lot on the Edge Plus too which is ridiculous because of how fast the phone is, I have been trying out other keyboards and one that came close to swiftkey for me was Minuum Keyboard it has some really good prediction even for really sloppy fast typing.
I have read on a another topic that this is caused by the Samsung firmware itself. It detects SwiftKey as low priority and kills it whenever possible, even when you are using it (which is kind of ridiculous?)
I've read that if you disable spcm in build.prop (requires root) the issue will be fixed. I hope that Samsung does something with it soon as the same problem has been on touchwiz since the start..
So not only the edge+ that has the issue, I got the International S6 (920F) and I need to live with that issue... Almost considered rooting and voiding my warranty because of this and the terrible ram management.
Source: http://forum.xda-developers.com/galaxy-s6/general/tip-fix-constant-swiftkey-reloading-lag-t3210027
EDIT: (found a working workaround
Try this; it might help you along the way:
zeebish said:
On the S6 go to Settings--> Language and input--> Default keyboard --> Set up input methods --> Turn off Samsung keyboard and Google voice typing. Worked for me.
Click to expand...
Click to collapse
Sent fra min SM-G920F via Tapatalk
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?
A very simple way to solve this problem is by giving priority to the notification that does not receive notification
1 go to setting
2 go to application
3 touch the name of that app to open its setting
4 go to notification
5 turn on the priority
That is all
Do you really think nobody else has already tested this?
themissionimpossible said:
Do you really think nobody else has already tested this?
Click to expand...
Click to collapse
i solved my notification issue by his method plus i have locked the concerned apps in background and now i have not lost any notification
Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...
themissionimpossible said:
Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...
Click to expand...
Click to collapse
I am sorry if this annoyed you.. I am new to Huawei and it is merely to share my ideas with others... Look to it as a brain storming
themissionimpossible said:
Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...
Click to expand...
Click to collapse
alethary said:
I am sorry if this annoyed you.. I am new to Huawei and it is merely to share my ideas with others... Look to it as a brain storming
Click to expand...
Click to collapse
There is one method to solve it though it is not permanent as you have to do it every reboot. But the fix is to disable Android's own Doze.
Enable developer options and USB debugging. Then type this adb command:
adb shell dumpsys deviceidle disable
That will fix your push notifications until next reboot where you have to do it again. This way we can still use Huawei's own "Doze" function.
alethary said:
. I am new to Huawei and it is merely to share my ideas with others...
Click to expand...
Click to collapse
This doesn't mean that you are free not to respect the forum rules as the other members.
Maybe this can help you, look carefully...
https://www.youtube.com/watch?v=JmvCpR45LKA
try it.
dannejanne said:
There is one method to solve it though it is not permanent as you have to do it every reboot. But the fix is to disable Android's own Doze.
Enable developer options and USB debugging. Then type this adb command:
adb shell dumpsys deviceidle disable
That will fix your push notifications until next reboot where you have to do it again. This way we can still use Huawei's own "Doze" function.
Click to expand...
Click to collapse
I can confirm, it works like a charm.
alethary said:
A very simple way to solve this problem is by giving priority to the notification that does not receive notification
1 go to setting
2 go to application
3 touch the name of that app to open its setting
4 go to notification
5 turn on the priority
That is all
Click to expand...
Click to collapse
FAIL
Wi-Fi and data always active in battery settings did the work for me on Simple Google Rom
Gmail native app was the problem before that. It might eat more battery, but I still have about 8 hours sot a day, with Bluetooth on 8 hours too and 2 hours talk time. ?
Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102
themissionimpossible said:
Do you really think nobody else has already tested this?
Click to expand...
Click to collapse
This is the moment that im down to the flor and :crying::crying:
My friend above think that he descover America....
Sorry my friend but this is one of the very first steps that we all have done (incuded so many others) lets hope that the new L29C432B170 has solve the problem with lockscreen on time notifications...I m running it right now, testing it and i think that YES has solve the problems especialy with stock mal app.
Always friendly.
I.also never had any.problems from day one
I have the eu version and I keep seeing all these threads about notification issues. I haven't had any with WhatsApp, snap chat, Skype or any other app. They come through instantly. Even when in deep sleep. What version is everyone having this issue on?
Sent from my HUAWEI NXT-L29 using Tapatalk
Has this been reported? I looked and didn't see anything.
So I didn't realize I was missing this feature until today when I got a scam call and noticed I hadn't received notification that the number had been reported as a scammer. It looks like Samsung has gone back to more of a plain vanilla dialer for Nougat in lieu of their Smart Call Dialer (with all that lovely Whitepages integration) that was present in Marshmallow. This might be no big deal for you or it might be enough of an annoyance to avoid updating. It's your call (no pun intended), but I wanted to at least let you know to expect the change once the thing is out of beta.
By the way, if you're like "what is he talking about" and you're on Verizon, you never had the feature to begin with so no huge loss.
Cheers.
Can you please run antutu without performance mode and post your results? Sorry to hijack but not a lot of people have tHe OTA
The option is still there. It's disabled on some carriers.
The feature works perfectly for me. Maybe it's carrier-related?
Sent from my SM-G930F using Tapatalk
I had Australia Vodafone with Marshmallow that had the Whitepages integration, I just tried updating to Germany Vodafone Nougat and it was missing initially. Someone else had mentioned that they had to perform a factory reset AFTER flashing the new ROM and it will bring back the whitepages integration and I can verify this! After I performed a factory reset I then had the identify unsaved numbers for the Galaxy S7 Nougat Vodafone Germany ROM.
iridaki said:
The feature works perfectly for me. Maybe it's carrier-related?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I am on BTU, language set to German. It is greyed out even so I made a factory reset after the update.
Gesendet von meinem SM-G930F mit Tapatalk
I was able to get it to work if you rooted, I using tmobile USA CSC.
Go into CSC folder and others.xml and look for where it says off,off,whitepages change to whitepages,whitepages,off then reboot.
In settings search for identify and it will lead to toggle to turn on (the setting is in advance settings).
hope that helps.
This issue is a little hard to explain so bear with me. Sometimes when I unlock my u ultra it does the Animation of opening/switching an app. It does only do the Animation though, so there's no new app being opened. My question now is, do you guys think that there's an app running in the background which is being opened for a split second when I unlock my phone? I'm really curious so if anyone has an idea I'll be happy to read it.
Amphibius2 said:
This issue is a little hard to explain so bear with me. Sometimes when I unlock my u ultra it does the Animation of opening/switching an app. It does only do the Animation though, so there's no new app being opened. My question now is, do you guys think that there's an app running in the background which is being opened for a split second when I unlock my phone? I'm really curious so if anyone has an idea I'll be happy to read it.
Click to expand...
Click to collapse
Wow, that happens to me also.
I thought I have some strange app installed I couldn't find the cause of this.
Is someone willing to help?
#me2
I think it's a Boost+ app.
Well i thing i had the same problem too and been able to solve it. Try to
disable "Ok Google Enrollment".
It should be something like this:
Settings >> Apps >> Show System>> Ok Google Enrollment >> Disable Ok Google Enrollment
Enviado desde mi HTC U Ultra mediante Tapatalk
Xardas_Nikolov said:
Well i thing i had the same problem too and been able to solve it. Try to
disable "Ok Google Enrollment".
In english should be something like this:
Settings >> Applications>> System>> Ok Google Enrollment
Enviado desde mi HTC U Ultra mediante Tapatalk
Click to expand...
Click to collapse
I've got an option for "voice match" is that the same?
Amphibius2 said:
I've got an option for "voice match" is that the same?
Click to expand...
Click to collapse
I don't think so. You have to go into "Settings", then in "Apps", then go in the right corner of the top where there are 4 options. Then "Show system". Then find and desable "Ok Google Enrollment"
Sent from my HTC U Ultra using Tapatalk
Xardas_Nikolov said:
I don't think so. You have to go into "Settings", then in "Apps", then go in the right corner of the top where there are 4 options. Then "Show system". Then find and desable "Ok Google Enrollment"
Click to expand...
Click to collapse
Ah okay, I found it
Thank you
Wow thank you Guys!
Had this problem since a couple of weeks and I almost wanted to delete every app I had installed in order to fix this anoying pop up. But battery saving mode also temporary fixed it for me, too.
Thank you very much!
Had this issue since day one and couldn't found the cause.
For me it was even weirder while using Opera Beta, everytime the animation occurred, when I opened the tab view, there was a screenshot from the site I was on and I couldn't see the tabs. Only way to solve this was exiting to homescreen and reopen Opera.
It was really annoying.