Hey guys, I have tried to stay away from changing the dpi on my devices because I have heard of crappy issues with it, I tried out SlimLP (note its unofficial for my device) for the first time on my galaxy tab 2 10.1 and I noticed under the settings I was able to change my dpi (must be a slimrom thing) its default was at 160 and I bumped it to 200 which made everything a little larger, I bumped it down to 180 and had a happy size for me, is there any downsides to changing the dpi? As in, battery life issues, display issues, performence issues, will I brick it The future?
Trozzul said:
As in, battery life issues, display issues, performence issues, will I brick it The future?
Click to expand...
Click to collapse
Hi, regarding battery life, no worries. I do DPI downsize on my S4 since 3 years without any issue.
However your hardware has limit. Better to look around the web to know how far some user did some experimentations.
But in any case, I recommend to get any nandroid backup before changing any DPI value, or don't be afraid about reinstalling the rom again.
baudbox said:
Hi, regarding battery life, no worries. I do DPI downsize on my S4 since 3 years without any issue.
However your hardware has limit. Better to look around the web to know how far some user did some experimentations.
But in any case, I recommend to get any nandroid backup before changing any DPI value, or don't be afraid about reinstalling the rom again.
Click to expand...
Click to collapse
Thanks for the reply, Good stuff to know! reason why i asked is because it just looked so professional on how it was added in and how easy it is to change it, im going to make a backup but i think i will be fine with bumping it up a tiny bit ( i tried googling the original Dpi of the tab 2 10.1 and i couldnt find any information :silly Would changing from the default 160 dpi to what i have it on now (180 dpi) be a drastic change?
Trozzul said:
Would changing from the default 160 dpi to what i have it on now (180 dpi) be a drastic change?
Click to expand...
Click to collapse
I don't think so as you already test with 200.
Related
Hello all, i rooted my tab today. Installed Superuser, Set CPU and Titanium backup. I froze a few of the pre loaded Samsung apps that came with the Tab. What other things can i do to speed up performance now that i am rooted? Any suggestions?? Thanks!
(Also if anyone else is currently using Set CPU on their Tab7 +, what settings work well for you? )
decaffviper17 said:
(Also if anyone else is currently using Set CPU on their Tab7 +, what settings work well for you? )
Click to expand...
Click to collapse
Which model? (There are at least 4 different ones.) Are you willing to give up battery life for that speed? What do you want to use your tablet for?
garyd9 said:
Which model? (There are at least 4 different ones.) Are you willing to give up battery life for that speed? What do you want to use your tablet for?
Click to expand...
Click to collapse
I have the Wi-Fi_GT-P6210. I guess my main issue with Set CPU is what are the limits i can go to without locking up the device. I have Set Cpu on my EVO 4g so i am familiar with it. I guess i was just seeing what advantages rooting gives me. I have my EVO rooted so i know the benefits on my phone, but what about the TAB. What apps can i remove without effecting performance. Thanks
If you want to overclock or undervolt, you'll need a custom kernel (see my sig.) At that point, you can OC to 1.4GHz. (I didn't include support for 1.6GHz has the processor in my own 7+ wouldn't stay stable at that speed, so I can't test it properly - it was also extremely easy for me to only add 1.4.) For voltages, you are also kind of going to have to experiment. I'm stable with 1300/1225/1125/1025/950/900 on my tab plus, but I can go much lower on my SGSII (which has the same processor.) You can search on the SGH-i9100 and SGH-i777 subforums for what other people have done with voltages.
As for which apps can be safely frozen, there's a post or two on that from a couple months back... I'd suggest searching for the full list. Nearly anything that looks like bloat really is.
I'd never suggest actually removing stuff - much better to just freeze it... then if you figure out that you really needed it, it's trivial to defrost it.
Good luck
Gary
I will slowly be adding more tweaks as I come across them so check back once in awhile.
Standard disclaimer: Use at your own risk!
Basically disabling the scrolling cache will reduce lagy and chunky scrolling. You won't notice a huge difference unless your scrolling through something your phone usually has a hard time with. Anyone that has Rom Toolbox would understand chunky scrolling on the first page of the app. So if you have the app, test it there. In general, icons will appear instantaneous and everything will run a bit smoother.
So here is what to do...
Use your favorite build.prop editor and add a new line.
persist.sys.scrollingcache
Set it's value to 3.
Reboot.
If you really want to make things extremely more responsive then adjust your vm.stat_interval. I do believe the default is 10. If someone could verify it before you change it let me know. Setting the value lower will increase the responsiveness of your phone a very good amount! Start at 8 and slowly work down. There is a chance you will become unstable so use caution. I can say I have set it to 1 (lowest setting) without a single issue.
Do not expect to increase your benchmark with this because it will actually drop a little. This is a perfect example of the whole benchmark debate. Your phone will be flying but quadrant won't show it.
Use the "SCOL" app to adjust vm.stat_interval and save your value. There is no need to reboot and the results of your changes are instantly applied.
Yes. It is most likely going to effect battery life.
48 65 6c 70 20 6d 65 21
will this work on JB roms?
JAYNO20 said:
will this work on JB roms?
Click to expand...
Click to collapse
Absofreakinlutely!
48 65 6c 70 20 6d 65 21
Hi everybody,
I have 2 questions:
1.Doesn't one have to do something in framework.jar to disable scrolling cache?
2. What do you mean by "set it's value to 4"?
mani1999 said:
Hi everybody,
I have 2 questions:
1.Doesn't one have to do something in framework.jar to disable scrolling cache?
2. What do you mean by "set it's value to 4"?
Click to expand...
Click to collapse
Wow I thought this got buried deep in the archives to never be seen again! Anyways, at the time I wrote this it is my understanding that basically...
1=cache on always
2=cache on certain times
3=cache off certain times
4=cache off always
Not like I haven't been wrong in the past though.
razz1 said:
Wow I thought this got buried deep in the archives to never be seen again! Anyways, at the time I wrote this it is my understanding that basically...
1=cache on always
2=cache on certain times
3=cache off certain times
4=cache off always
Not like I haven't been wrong in the past though.
Click to expand...
Click to collapse
So if I want scrolling cache off, it looks like this, or?:
persist.sys.scrollingcache=4
Thanks for your fast reply
Yup thats it
Does disabling the scrolling cache also negatively affect battery life?
Sent from my SCH-I535 using xda premium
Amphibliam said:
Does disabling the scrolling cache also negatively affect battery life?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks
Shouldnt effect the battery
My ROM Toolbox scrolling seems the same after applying this. Did I do it correctly?
Sent from my SCH-I605 using xda premium
Yes
razz1 said:
Use the "SCOL" app to adjust vm.stat_interval and save your value.
Click to expand...
Click to collapse
The wut now?
Gnarfsan said:
The wut now?
Click to expand...
Click to collapse
CM10.2, Neak Kernel => Tried, saw no improvement.
Wow,thank you, this tip made my scrolling smoother, and it was so simple.
sorry for coming to such an old post,
but isn't scrolling cache meant to improve scrolling performance as it builds what it has to show next in the cache?
i just wanna understand the technical side of things.
mainly because if enabling it reduces performance, why do manufacturers enable it?
cheers
razz1 said:
I will slowly be adding more tweaks as I come across them so check back once in awhile.
Standard disclaimer: Use at your own risk!
Basically disabling the scrolling cache will reduce lagy and chunky scrolling. You won't notice a huge difference unless your scrolling through something your phone usually has a hard time with. Anyone that has Rom Toolbox would understand chunky scrolling on the first page of the app. So if you have the app, test it there. In general, icons will appear instantaneous and everything will run a bit smoother.
So here is what to do...
Use your favorite build.prop editor and add a new line.
persist.sys.scrollingcache
Set it's value to 4.
Reboot.
If you really want to make things extremely more responsive then adjust your vm.stat_interval. I do believe the default is 10. If someone could verify it before you change it let me know. Setting the value lower will increase the responsiveness of your phone a very good amount! Start at 8 and slowly work down. There is a chance you will become unstable so use caution. I can say I have set it to 1 (lowest setting) without a single issue.
Do not expect to increase your benchmark with this because it will actually drop a little. This is a perfect example of the whole benchmark debate. Your phone will be flying but quadrant won't show it.
Use the "SCOL" app to adjust vm.stat_interval and save your value. There is no need to reboot and the results of your changes are instantly applied.
Yes. It is most likely going to effect battery life.
48 65 6c 70 20 6d 65 21
Click to expand...
Click to collapse
Can I know how to get the Rom Toolbox app?
Krishu said:
Can I know how to get the Rom Toolbox app?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
spazzy1912 said:
sorry for coming to such an old post,
but isn't scrolling cache meant to improve scrolling performance as it builds what it has to show next in the cache?
i just wanna understand the technical side of things.
mainly because if enabling it reduces performance, why do manufacturers enable it?
cheers
Click to expand...
Click to collapse
I had the same thought. If setting it to 3 is so much better, then why would anyone (companies included) want to set it to something else?
Sorry for posting a year too late but THANK YOU SO MUCH <3
Hello,
I have noticed, that the load* (not the CPU%) under several CM10 (or higher) based roms is very high, i.e. >2.
This is true for PACMAN, JellyBam and the CM10 nightly.
Can someone please have a check by activating the CPU-Stat-Overlay and post the line that looks like 2.7/3.0/2.0?
Is this a known problem? I once had a nightly of CM10 on the Phone, which ran very well. I do not think, that it had this problem...
I do not have this Problem with OptimusRS which is based on the Official ICS. Here, the load is lower by a factor of 10.
*in contrast to the CPU usage (%), the load also captures if the system is blocked by something other than the CPU (I/O, ...)
Greetings,
Hendrik
Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom
svvv said:
Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom
Click to expand...
Click to collapse
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik
henfri123 said:
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik
Click to expand...
Click to collapse
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.
svvv said:
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.
Click to expand...
Click to collapse
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik
henfri123 said:
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik
Click to expand...
Click to collapse
I come back to CM-Based rom today...and i noticed that in Jellybam and also Bernie's rom the CPU usage is really high...the cpu stays every time at the higher frequence and the back of the phone is really hot! I noticed this problem also with MIUI rom that are also CM Based, i need to change kernel for trying correctly Bernie rom! With Pesach kernel for CM10.1 the thing seems good..but the phone stucks ever at the minimum frequence...and it never go on deep sleep!
Is really strange! I tried bernie's also when it came out some time ago but it hadn't this problem! I think that is a recent problem!
Install wakelock to see who do that. put wifi to sleep when screen is off. Uninstall the programs that you do not need.
Take a look here
http://forum.xda-developers.com/showthread.php?p=42778421
Sent from my LG-P920 using xda app-developers app
Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although I suspect it would be the latter since I have used Tegra 2 based phone before (hacked, of course), and it's surprisingly smooth so there may be explanation somewhere in either second-stage BIOS or in the kernel for the 3D phone and no I am not pointing the finger at any developers here as there are variables that have to be checked down.
Sent from my XT907 using xda premium
Dr. Mario said:
Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although
Click to expand...
Click to collapse
I don't understand, what you are saying...
For me, it is not yet clear, whether this problem exists on every phone, and whether it is on every rom.
When I started using CM10, I did not have this impression. Does someone have an old version on CM10 and could check?
What about the others? What are your LOADs?
There must be more users...
Greetings,
Hendrik
CM10 only load the values which are in the kernel which you can install separately, and some kernels have better CPU values. Not to mention there is 410 MB assigned to CPU.
However in some case, BIOS is what make or break this phone (BIOS boots up first and displays red or silver LG logo depending on whether BIOS is unlocked or not, and is responsible for loading Linux kernel, thus booting Android OS up). So it's hard to say but I might want to try assemble the BIOS on my own and see if problem persists in some OS images (FYI, BIOS development is much harder than Android OS development).
Sent from my XT907 using xda premium
Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik
henfri123 said:
Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik
Click to expand...
Click to collapse
You're not the only one...some days ago i went back to CM-Based roms and i noticed that they never go in deep sleep! And the phone goes hot...the only rom where i hadn't this problems is the Baked Blackbean by kidkoala...also MIUI roms have this problem!
Hello,
is there anything new on this topic?
Can anyone using CM10 or higher confirm, that he does NOT have this problem?
(to check:
Settings-->Developer Settings (very bottom) --> Display CPU Usage (far down)
let the phone rest some Minutes.
An Overlay is shown. The first three lines are of interest
--> Are the values low, around 0.1? --> no Problem, all good.
--> Are the values high, around 1 or higher --> you have the Problem.
Greetings,
Hendrik
As many of you are most likely aware, the Quarks have a 1440p display. This resolution is higher than the standard 1080p a few years ago.
This creates lots of battery drain and CPU and GPU strain as the device must drive all of those pixels. Our devices can do it with relative ease, however I seek a way to downgrade the resolution to 1080p. This would help battery life as well as performance.
It's possible on an LG G3, so I was wondering if it is on Quark.
Any ideas?
http://forum.xda-developers.com/droid-turbo/help/root-try-to-change-res-to-1080p-t3080313
Answer for the Quark. Yeah, it's over in the Droid Turbo forum, but was posted when we were all one big forum.
ChazzMatt said:
http://forum.xda-developers.com/droid-turbo/help/root-try-to-change-res-to-1080p-t3080313
Answer for the Quark. Yeah, it's over in the Droid Turbo forum, but was posted when we were all one big forum.
Click to expand...
Click to collapse
That seems to only work on a per app basis. I guess that's the only solution.
Thanks; are there any other ideas?
Latiken said:
That seems to only work on a per app basis. I guess that's the only solution.
Thanks; are there any other ideas?
Click to expand...
Click to collapse
Yes, I found this solution some time ago, when I was looking to save battery. But let me tell you that I haven't noticed any improvement. Anyway, you need a rooted device, install a terminal emulator app, and type:
su
wm size 720X1280
Click to expand...
Click to collapse
You will also need to change screen density, you can change it with this command:
wm density xxx
Click to expand...
Click to collapse
With "xxx" being the wanted screen density, I have tested with 300 and 280.
To restore original values, you have to type:
su
wm size 1440x2560
wm density 560
Click to expand...
Click to collapse
Hope that helps.
Enviado desde mi Moto MAXX mediante Tapatalk
And? Battery drain is better with 1080p?
Latiken said:
That seems to only work on a per app basis. I guess that's the only solution.
Thanks; are there any other ideas?
Click to expand...
Click to collapse
The only app I had scaling issues with is the moto display screen. No matter what DPI I set I could not get it to look correct (or unlock from it, had to hit power to get to the normal unlock screen) at 1920x1080. Also, the DPI editor in that app did nothing and you MUST change the DPI when going to a lower res. I always use the build.prop editor in ROM toolbox to change DPI. I had a good experience with it personally but I like the convenience of picking up my phone and swiping to unlock without having to hit the power button. Could've been placebo but the phone did seem a touch snappier and I broke 8hr SoT a few times when running a lower res. I assume that can be chalked up to using less power in any rendering tasks. I do probably average around 7hr SoT on stock res.
In short, if you like not having to hit the power button to unlock your phone, changing res isn't for you. If you don't mind I say it's worth a test run at the least as it is easy to undo.
Thanks for the information guys; gonna be trying this out over the next few days.
Polarisfff said:
And? Battery drain is better with 1080p?
Click to expand...
Click to collapse
Theoretically, yes. I need to test out the battery life as well as performance before I can make a conclusion, though.
EDIT: I've done a factory reset and it stays the same. there is no intertia when scrolling. even at first step, when choosing the phone langage at first setup.
Hello everyone, hope you can help.
The scrolling is very slow compared to any other phone, I borrowed a samsung phone from a friend to show the difference. There is not inertia, it's really annoying, I have to scroll 10 times to see a long webpage. It is really a software issue, the screen is working perfectly.
The only place where the scrolling is smooth it's in the settings/developer options, see video.
Thanks all in advance.
crazypixel said:
Hello everyone, hope you can help.
The scrolling is very slow compared to any other phone, I borrowed a samsung phone from a friend to show the difference. There is not inertia, it's really annoying, I have to scroll 10 times to see a long webpage. It is really a software issue, the screen is working perfectly.
The only place where the scrolling is smooth it's in the settings/developer options, see video.
Thanks all in advance.
Click to expand...
Click to collapse
I've never encountered this issue on stock ROM nor on MIUI EU ROM which I've flashed on this phone. See if switching between 120/60hz screen mode changes anything. Seeing as you have developer options enabled maybe you've selected so etjingnin there shouldn't have too - try disabling that. Have you tried factory resetting to see if that fixes it? Obviously backing up all your data first.
1qazwsx4 said:
I've never encountered this issue on stock ROM nor on MIUI EU ROM which I've flashed on this phone. See if switching between 120/60hz screen mode changes anything. Seeing as you have developer options enabled maybe you've selected so etjingnin there shouldn't have too - try disabling that. Have you tried factory resetting to see if that fixes it? Obviously backing up all your data first.
Click to expand...
Click to collapse
Hello and thenks for your answer, I've just got a brand new phone. It's been happening from the beginning, even before enabling developer options, I've seen other people having the same problem, thought it was a rom problem (i'm using stock rom updated to 13.0.5)
https://www.reddit.com/r/Xiaomi/comments/laay68
tried that fix as well of corse and didn't help
Can you run Geekbench on your device when this happens and post the scores here?
Thanks for helping, below both CPU and COMPUTE Benchmarks
Xiaomi 2201116PG - Geekbench
Benchmark results for a Xiaomi 2201116PG with an ARM ARMv8 processor.
browser.geekbench.com
Xiaomi 2201116PG - Geekbench
Benchmark results for a Xiaomi 2201116PG with an ARM ARMv8 processor.
browser.geekbench.com
Although I think is not a matter of bad performance it's just the ROM itself Im afraid. It's a feature let's say.
PS: I've done a factory reset and it stays the same. there is no intertia when scrolling. even at first step, when choosing the phone langage at first setup.
If you've watched videos of this phone in use and you can see the scrolling works alot better than yours - if I were you, I'd return my device. If the issue was ROM wide then it could perhaps be a digitiser issue. If it's only some screens then I'd think it was a setting somewhere... Since you've factory reset your phone I'd say you can rule out a setting applied on accident. Haven't seen anyone else mention this issue yet
1qazwsx4 said:
If you've watched videos of this phone in use and you can see the scrolling works alot better than yours - if I were you, I'd return my device. If the issue was ROM wide then it could perhaps be a digitiser issue. If it's only some screens then I'd think it was a setting somewhere... Since you've factory reset your phone I'd say you can rule out a setting applied on accident. Haven't seen anyone else mention this issue yet
Click to expand...
Click to collapse
Hello, thanks for your answer.How does the benchmark look? Strangely the scrolling is super-smooth and has inertia with some apps or setting, for example in the developer settings and in the settings area in general is butter-smooth. My phone came with MIUI 12 and unfortunaly I've updated it straight away so can't really compare.
I've seen other people complaining:
https://www.reddit.com/r/PocoPhones/comments/lsoh67
Why does MIUI 13 (Android 12) feel so sluggish and generally-speaking slow on X3 Pro?
Hi everyone, I was thrilled last night when my X3 Pro showed an upgrade to Android 12-based MIUI 13 was available. I downloaded the thing (all 3.1 GB of it...), install went without a hitch, ditto reboot, but I'm severely disappointed so far...
forum.xda-developers.com
Xiaomi Community
c.mi.com
-
crazypixel said:
Hello, thanks for your answer.How does the benchmark look? Strangely the scrolling is super-smooth and has inertia with some apps or setting, for example in the developer settings and in the settings area in general is butter-smooth. My phone came with MIUI 12 and unfortunaly I've updated it straight away so can't really compare.
I've seen other people complaining:
https://www.reddit.com/r/PocoPhones/comments/lsoh67
Why does MIUI 13 (Android 12) feel so sluggish and generally-speaking slow on X3 Pro?
Hi everyone, I was thrilled last night when my X3 Pro showed an upgrade to Android 12-based MIUI 13 was available. I downloaded the thing (all 3.1 GB of it...), install went without a hitch, ditto reboot, but I'm severely disappointed so far...
forum.xda-developers.com
Xiaomi Community
c.mi.com
-
Click to expand...
Click to collapse
To be fair, I've never cared for benchmarks unless I've run flagship devices so I haven't bothered testing this as it runs smooth and has good batter life. Which benchmarking app would you like me to test for you? Will post results
1qazwsx4 said:
To be fair, I've never cared for benchmarks unless I've run flagship devices so I haven't bothered testing this as it runs smooth and has good batter life. Which benchmarking app would you like me to test for you? Will post results
Click to expand...
Click to collapse
Sorry thought was you who asked me to post my Benchamrks results, it was ajaynumb
instead
Click to expand...
Click to collapse
Thread 'Redmi Note 11(spes) CPU throttling issue with Android 11 based MIUI 13' https://forum.xda-developers.com/t/...-issue-with-android-11-based-miui-13.4433093/
I asked to run Geekbench to know if you face the above issue. Sometimes, my Redmi Note 11 caps peak CPU frequency to 1.1Ghz (instead of 2.4Ghz) and it never peaks till I reboot!
Juste wanted to check if it's prevalent across MIUI 13 irrespective of device.
Hi! This happened to me on freshly flashed xiaomi.eu ROM.
I was able to fix it by changing default wallpaper to something else
Crimento said:
Hi! This happened to me on freshly flashed xiaomi.eu ROM.
I was able to fix it by changing default wallpaper to something else
Click to expand...
Click to collapse
I did change the WP but didn't help either. Just seen a MIU 13 update has been rolled out. I'll wait a few days to seee if it's buggy and install it. Thanks
1qazwsx4 said:
I've never encountered this issue on stock ROM nor on MIUI EU ROM which I've flashed on this phone. See if switching between 120/60hz screen mode changes anything. Seeing as you have developer options enabled maybe you've selected so etjingnin there shouldn't have too - try disabling that. Have you tried factory resetting to see if that fixes it? Obviously backing up all your data first.
Click to expand...
Click to collapse
I have the exact same issue so send text or WhatsApp messages is a nightmare, I often just send half completed messages as a result. I raised this with Xiaomi support who just refunded me without troubleshooting suggesting it's a known fault
stedoc said:
I have the exact same issue so send text or WhatsApp messages is a nightmare, I often just send half completed messages as a result. I raised this with Xiaomi support who just refunded me without troubleshooting suggesting it's a known fault
Click to expand...
Click to collapse
Does it lag while typing yo mean? Never had that problem, jut the scrolling. I'm using another keyboard app though.
crazypixel said:
Does it lag while typing yo mean? Never had that problem, jut the scrolling. I'm using another keyboard app though.
Click to expand...
Click to collapse
Not so much lag but when want to move the cursor or scroll for editing it freezes. I am very tempted to buy another one as they're not cheaper and hope for the better. Same on gbord and swifkey using text and whatsapp.