Develop Bugs

[Q] Device becomes unresponsive after several minutes of use.

Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN

The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.

KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium

Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.

Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium

Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.

Any news? Was it the battery issue?

[Q] Weird WiFi Issue (Wont Turn On)

Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!

KingKash420 said:
Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!
Click to expand...
Click to collapse
I'm having the same problem. I upgraded to the KK 4.4.2 and now my WiFi won't turn on! I'm getting the Security notice that "Your phone's security has blocked an action that is not permitted. No further action is required." So, I went to the phone security tab to see what my settings were and it is set to Normal and the only other choice is High. So, I don't want to change that setting!

Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk

serio22 said:
Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!

KingKash420 said:
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!
Click to expand...
Click to collapse
Right.. But other than that, the only other thing I can think of is to Odin the 4.4.2 firmware and see if that would fix it, if not then its likely a hardware problem
Sent from my SGH-M919 using Tapatalk

Crazy Touch Screen Not Responding Bugs with my G3

So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot

I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk

@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.

deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).

^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.

Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.

@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?

I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96

Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.

This is happening when the screen is on right? Or is the screen turning off and then not turning I again?

You need to keep Knock feature on, someone already said this. That's why your screen is freezing.

Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug

icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...

Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...

Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...

icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?

Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.

Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.

Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!

[Q] Samsung Galaxy Tab S 8.4 - Screen issues

Hi there,
I was hoping you could give me some advice regarding an issue I've had for a while with my Tab S.
The screen is flickering occasionally and at times it causes the battery to drain very quickly and suddenly it reboots.
I have tried disabling hardware overlay option in the developer settings which seems to be suggested in many forums but that has not made much difference.
This has been getting gradually worse and now I am at a stage where after entering the PIN code to unlock the SIM the screen flashes a few times (white lines across the screen) and then the tab powers itself down.
I should add that I have root access and can flash roms if needed.
I believe the tablet was originally from United Arab Emirates but since I am in France I changed to a French stock rom. Before doing that the phone app kept crashing every time I missed a call...
Your help is greatly appreciated!

poenneby said:
Hi there,
I was hoping you could give me some advice regarding an issue I've had for a while with my Tab S.
The screen is flickering occasionally and at times it causes the battery to drain very quickly and suddenly it reboots.
I have tried disabling hardware overlay option in the developer settings which seems to be suggested in many forums but that has not made much difference.
This has been getting gradually worse and now I am at a stage where after entering the PIN code to unlock the SIM the screen flashes a few times (white lines across the screen) and then the tab powers itself down.
I should add that I have root access and can flash roms if needed.
I believe the tablet was originally from United Arab Emirates but since I am in France I changed to a French stock rom. Before doing that the phone app kept crashing every time I missed a call...
Your help is greatly appreciated!
Click to expand...
Click to collapse
Well I have heard of this, but never seen it. Could you perhaps provide a video of the flickering? I guessing this is an firmware issue as people flashing lollipop said they saw this. The only thing I can think of is going back to KitKat or check if your on the latest update
Sent from my SM-T800 using Tapatalk

DUHAsianSKILLZ said:
Well I have heard of this, but never seen it. Could you perhaps provide a video of the flickering? I guessing this is an firmware issue as people flashing lollipop said they saw this. The only thing I can think of is going back to KitKat or check if your on the latest update
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply.
I am actually on KitKat already, and going back to stock would mean issues with my phone app crashing when I miss a call.
Incompatible firmware seems likely but how do I know which firmware is right for my tab apart from trial and error?
Any other diagnostics? Changing CSC?

It sounds like a battery or loose connection problem to me, does the flickering happen when you move or slightly bend the tablet at all.
Have you tried the Samsung hidden codes to do an battery/hardware test.
John.

Tinderbox (UK) said:
It sounds like a battery or loose connection problem to me, does the flickering happen when you move or slightly bend the tablet at all.
Have you tried the Samsung hidden codes to do an battery/hardware test.
John.
Click to expand...
Click to collapse
I read a lot of people reseating the battery after having issues with battery draining, I might give this a go.
But before I open up my tab, are there any other diagnostics I can do, what are those codes for testing the phone?
Thanks

I have not tried any myself as you need a dialer and my T800 is wifi only, be careful what you are doing, there are loads of lists of secret codes.
http://www.softwaresenior.com/blog/57-samsung-galaxy-secret-code
John.

Tinderbox (UK) said:
I have not tried any myself as you need a dialer and my T800 is wifi only, be careful what you are doing, there are loads of lists of secret codes.
http://www.softwaresenior.com/blog/57-samsung-galaxy-secret-code
John.
Click to expand...
Click to collapse
You can use activity launcher from Adam Szakowski to lauch the hardware testing apps, just be careful what you launch, you can end with a wiped tablet.

I have now reseated the battery (disconnected and reconnected it) and so far so good!
No screen flickering and no random rebooting.
Thank you for your help!

Erratic ram management in Android 10

Hey guys, I have updated to Android 10 from quite a sometime now(was a beta tester) and was noticing that device practically become usable after a few days of usage. Keyboard stops popping up, apps get killed in background and so on..
This issue gets fixed by a restart though. Has anyone else noticed something similar?

I am also facing issues after Android 10 update. Please let me know if you find permanent fix or solution.

Yes, same here. I reverted back to Pie. I thought I was the only one!
Sent from my SM-G960F using Tapatalk

Nope, you are not alone :crying:
i can confirm the exact same issue since OTA update to Android 10 on S9 (DBT). currently with second minor Update to DTAD build problem still there. Tried different things to work around but yet nothing helped. i assume it has something to do with memory leak on swap partition. memoryinfo & swapcheck app always show 0 byte free swap memory which cannot be freed again when this occurs. As stated before, only reset phone helps, but after 24h its the same. struggling with this since the first Q Update Version. Any suggestions highly appreciated.
Olioaglio

Auto-restart every morning

I didn't find any issue, and I didn't factory reset my device after installing the update. My phone runs quite smoothly, no issues whatsoever.
The only minor bug is that the transition animation of the clock from the lock screen to the always on display is laggy, and sometimes the instructions like "hold your phone more upright" get stuck on the always on display. I hope this will get fixed in the next update.

@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio

Olioaglio said:
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Click to expand...
Click to collapse
Well I am still researching about this issue. I reported this issue couple of times to Samsung during beta testing; they said, they are unable to reproduce this issue neither they are able to see it on logs which I have sent. For me, the issue starts to appear after 91 hours of usage without a restart. Weirdly, using any keyboard other than Samsung Keyboard seems to help somewhat. I tried using Gboard and the issue somewhat mitigated but still annoying enough.
Did you guys tried reflashing the firmware using Odin?

icoolguy1995 said:
Did you guys tried reflashing the firmware using Odin?
Click to expand...
Click to collapse
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio

Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
I have reflash the firmware because it was getting unbearable. It's been 3 days, no issues yet. Will keep you guys updated.

I just cleared the System Chache and my phone is working fine now.

Same issue here. After android 10 update it's laggy as hell. Android auto crashes randomly. Spotify stops working..

Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
No effect of reflashing. Same issue popup up after 4-5 days. I wonder if this is more like a hardware related issue then software?

No, i don't think so.

Got a new update, it made issue worse. Now, instead of 90 hours free of system killing spree I am getting 70 around-ish hours with good ram management. So my workaround for this is now to set auto restart in 3 days interval.

Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
Did you change your default keyboard?

icoolguy1995 said:
Did you change your default keyboard?
Click to expand...
Click to collapse
yeah, i use SwiftKey since ages.

Two updates passed (currently on G960FXXS9DTD7), so far so good (despite no mention in the changelog).