Develop Bugs

bug touchscreen

hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded

wave1990 said:
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
Click to expand...
Click to collapse
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.

Protonus said:
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Click to expand...
Click to collapse
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?

wave1990 said:
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
Click to expand...
Click to collapse
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.

Protonus said:
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Click to expand...
Click to collapse
I do not know if you develop .... but you could create a fix that recalibrates the driver every tap on the screen!
is an idea =)

Opening different apps than the one selected. Bug?

Okay I don't know if this is a bug in every Android version that still hasn't been fixed or is it an app that's causing it.
What happens is when I would be using an app like for example Google talk. I would try opening YouTube it would open calculator. And if I try opening messaging it would still open calculator. No matter which app I'd open it would open the wrong app. And I either have to kill all apps or restart my phone
I had this issue only my G2, my Nexus S, Anyone else having this?
Can't recall if I had it on my Sensation or not...
Sent from my Galaxy Nexus using xda premium

This has never happened to me. Are you completely stock?
Sent from my SGH-T989 using xda premium

I have had a similar error on multiple versions of android where you hit the back button and it starts to cycle through several different apps.

Yup happens to me on a few occasions. It just cycles like axion said

If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium

I've seen this once on my Galaxy Nexus only, never on a Nexus S, of GS2. A reboot seemed to resolve the issue. I've not seen it again since.

joshnichols189 said:
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium

jonathan3579 said:
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.

thequinox said:
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
Click to expand...
Click to collapse
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium

Happened to me too. Usually helps to get rid of all alps in multitasking menu.

jonathan3579 said:
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.

krohnjw said:
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
Click to expand...
Click to collapse
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210

Lowtrash said:
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Click to expand...
Click to collapse
No, I've just backed down the stack. I am curious as to the trigger for the behavior though as it is a rather uncommon occurrence.

krohnjw said:
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
Click to expand...
Click to collapse
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that? To add to that, if a device pre-ICS did have this problem... Would it not be considered defective? *Keeping in mind that most people don't have the problem.* I have absolutely no issues no matter the number of apps I have open. So is my device defective because everything opens as it should? As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...

jonathan3579 said:
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that?
Click to expand...
Click to collapse
Where do you see this claimed to have happened on any pre 4.0 rom?
I had this issue only my G2, my Nexus S, Anyone else having this?
Click to expand...
Click to collapse
jonathan3579 said:
I have absolutely no issues no matter the number of apps. As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
Click to expand...
Click to collapse
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....

krohnjw said:
Where do you see this claimed to have happened on any pre 4.0 rom?
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
Click to expand...
Click to collapse
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.

Yep I know what you mean, happens to me on Google Music.
Th easiest solution I found was to force stop the app that's bugged out.

I've had this too. Swiping away the app I'm trying to open and the one it is opening instead has fixed it for me.

jonathan3579 said:
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Click to expand...
Click to collapse
Defective software I have no issue with - that's a harsh classification for a bug, but not incorrect.
Your statement of "Return it" followed by "most of us do not have these issues" seemed to imply a belief that the physical unit must be defective (in comparison to a unit that did not experience this issue) rather than a behavior or set of behaviors causing as software issue as most users do not experience this. Thereby returning would resolve the issue.
Given the symptoms present when this occurs I can't imagine this to be true i any way, shape or form. Especially given that this bug has existed since 4.0 hit AOSP and on builds for the Nexus S as well (hence why it's absurd to blame this on a singular hardware fault of a single device).
I am interested in reproducing the issue, or capturing a logcat the next time it occurs (it only seems to happen when I am in the car unfortunately) to see if the WindowManager of ApplicationManager are supposedly starting the proper activities or the issue might lie with the package manager.

I've had this happen when i open a lot of apps without closing them and use the multitasking button to switch between apps.

Is device unlock slow after January update?

Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...

This is a known issue if you took the update by sideloading the OTA

ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
Reboot your device once or twice and it should work normaly.

This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153

I did factory reset, had no delay. As soon as I rooted. Had the delay.

ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.

DoctorB0NG said:
This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
Yes, turning always on seems to be the fix as of now

wtherrell said:
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.
Click to expand...
Click to collapse
My OG XL doesn't have this problem at all on the January 5th patch and meltdown only affects Intel x86 CPUs. Spectre affects quite a few ARM, MIPS and x86 chips but I refuse to believe that would cause a device to take 2-3x longer to unlock. Spectre fixes would incur a performance penalty on CPU demanding loads which waking a device up does not qualify.

Supposedly this issue has been fixed with the fix to be released at a future date. They said this in mid December, so doesn't look like the fix made it to the January security update. Hopefully the February one will have the fix

new Firmware 47.1.A.12.179

The new Firmware 47.1.A.12.179 is out:
https://xpericheck.com/device/G8441
in Android-Hilfe.de Thread they write that the firmware includes Android Security Patch is 01. May 2018.

It is the May security patch. Couldn't find any other changes so far.

Good day.
I noticed that wifi now connects intantly.

Good news about wifi, although for me, the issues are so intermittent that it's tough to tell.
SmartLock settings are still blank.
I won't be able to test car bluetooth until tomorrow, so fingers crossed. Although I did discover last weekend that if I pause from the car's headset, it will display the currently paused song after 2, or so, seconds.

snowkeep said:
Good news about wifi, although for me, the issues are so intermittent that it's tough to tell.
SmartLock settings are still blank.
I won't be able to test car bluetooth until tomorrow, so fingers crossed. Although I did discover last weekend that if I pause from the car's headset, it will display the currently paused song after 2, or so, seconds.
Click to expand...
Click to collapse
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.

Covalex said:
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.
Click to expand...
Click to collapse
Doesn't work for very long, two or three days max, then it stops opening and trusted device fails to unlock

As long as it does come with 8.1 I'm not too interested. Whole reason with going with Sony was project treble for faster updates. Disappointing to say the least.
Sent from my G8441 using Tapatalk

ninjazin said:
Whole reason with going with Sony was project treble for faster updates. Disappointing to say the least.
Click to expand...
Click to collapse
You really can't see the benefit of Treble? We get security update each month! I'd never seen such quick updating before Treble, on non Google's phones.
To compare: my Motorola X Force is still on October 2017 security patch :/

Davka said:
You really can't see the benefit of Treble? We get security update each month! I'd never seen such quick updating before Treble, on non Google's phones.
To compare: my Motorola X Force is still on October 2017 security patch :/
Click to expand...
Click to collapse
As my wife's S7 from Samsung also gets monthly updates then it's not really impressing
Sent from my G8441 using Tapatalk

Covalex said:
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.
Click to expand...
Click to collapse
I have to agree with Didgesteve. The only improvement is that the SmartLock screen stays visible - it still doesn't work, but you can see it. The wifi problems came back. And the bluetooth is the same, to possibly worse. Yay! for security updates, but from a user perspective, this update did nothing, as far as I can tell. At least there are workarounds for the problems. It's still a huge improvement over the Galaxy S5 it replaced.

Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.

darklordtom said:
Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.
Click to expand...
Click to collapse
Agreed

darklordtom said:
Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.
Click to expand...
Click to collapse
I've never had this issue. I wonder if it's wifi ap/router dependent ?

Good day.
Because i have been having abnormal consumption with RCS Service, i tried this tutorial and it seems that the wifi problem that it sometimes takes long to connect has disappeared. (https://forum.xda-developers.com/sho...44&postcount=6)
And i now have a better battery life.

@Hansoliv
Hello
The link is wrong. :/

Burn02 said:
@Hansoliv
Hello
The link is wrong. :/
Click to expand...
Click to collapse
Oops, sorry
See this Thread the 6th post
https://forum.xda-developers.com/xperia-xz1-compact/help/how-to-deactivate-rcs-service-rich-t3730605

ninjazin said:
As my wife's S7 from Samsung also gets monthly updates then it's not really impressing
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
And yesterday she not only for the may update but also Android 8.0. so now her one year older phone is more updated than mine, without treble :/
Sent from my G8441 using Tapatalk

I have problems with battery drain after this update. Before the update, the phone could be used for more than two days without recharging and now I have to recharge after 8 hours without much use. Consequently I have deleted almost all apps from my phone and did everything reasonable (yes, stamina mode is activated). No success. Sad.

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).