Database Users

Bell JL2 annoying problem

I have an annoying problem with JL2 sometimes : the contextual menu is coming up by itself without touching any button. When is happening the menu and back button are lit up. It does that mostly on the GO launcher, Market application , Samsung keyboard and more an less on other open application .
Is somebody having same issue ? any solution to that ?
Thanks,

I think it must be a hardware defect. Never seen this problem before.

zorxd said:
I think it must be a hardware defect. Never seen this problem before.
Click to expand...
Click to collapse
You may be right as the phone was coming back from Bell to fix the SD card failure. It came with JL2 installed , but the motheboard is same 10.09

Update the firmware for the buttons. When I get to my computer I'll add the link to how. I had the same problem and it was fixed after updating.
Sent from my GT-I9000m

Kewjoe said:
Update the firmware for the buttons. When I get to my computer I'll add the link to how. I had the same problem and it was fixed after updating.
Sent from my GT-I9000m
Click to expand...
Click to collapse
Thanks . Waiting for instructions.

[Q] Answer sliding lag!

Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...

zanbay said:
Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...
Click to expand...
Click to collapse
Hello,I have the same lag?
Anyone else have noticed this?

Yes, I've got the same problem. It took so long the other day that I missed the call completely.
Sent from my SM-G900R4 using Tapatalk

anyone have an solution?

First thing I would do is a hard reset - A pain I know, but doing so you can check whether it is potentially a Hardware issue with multitouch/touch etc.
Once you've done that, if it's still exhibiting the same behaviour check your screen behaviour on touch reactions on normal day-to-day use. There may actually be an app for it. (the Note 3 suffered some touch problems, not saying the S5 has them but have to check to be sure) .
If it is deemed a software glitch and a reset fixes it then you should be OK. - However if it's a touch screen bug I'd suggest returning/swapping it.
I'm more inclined to believe it's a software glitch, and a factory reset will indeed solve the problem.

Oke,thanks

Same issue! Did a factory reset but didn't help. Send it to local service center, they keep telling me there is no issue with the phone and that when it happens I should record a video as evidence of the problem. So much so Samsung warranty! Plus I have encountered ransom reboots when answering the phone.
Totally unhappy with S5. It is terrible. S4 and S3 were very stable.

vegerfrancois said:
Hello,I have the same lag?
Anyone else have noticed this?
Click to expand...
Click to collapse
i did noticed that too..
on mine if you put directly your finger in the circle and drag it works 1st try..
i still didnt have time to hard reset to be sure..

I noticed this too. I find that you have to hold your finger on the green answer and slide slowly. It's definitely a software problem that will hopefully be fixed in an update.
Factory reset makes no difference as done this for another problem I was having.
Sent from my SM-G900F using Tapatalk

Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone

I had this problem at first as well, but after the latest update it fortunately disappeared, I did a full wipe as well.

Same problem here! Partially solved with enabling home button to accept calls....

Same here....its a pain in the ass ?
Sent from my SM-G900F using XDA Premium 4 mobile app

rathga said:
Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone
Click to expand...
Click to collapse
I disabled the lockscreen animation and that helped making the device more snappy. Here are some more usefull tips http://phandroid.com/2014/04/25/samsung-galaxy-s5-first-14-things-to-do/.

I also have this lag when I'm trying to respond. It only woks on the 2nd attempt.

There's definitely a knack to answering a call, which can be quite annoying. Cannot understand why they didn't just leave it alone. Would rather answer my calls with a quick swipe to the right.
Sent from my SM-G900F using Tapatalk

What FW version are you all on? ANG2 seems to have solved it for me!

johan81 said:
What FW version are you all on? ANG2 seems to have solved it for me!
Click to expand...
Click to collapse
I hadn't even noticed it was fixed since I got the new update. Just tested and problem is solved
Sent from my SM-G900F using Tapatalk

Until a firmware update, enable answer with home button.
Sent from my Galaxy S5 using Tapatalk.

Soft touch buttons unresponsive

I have a Nexus 4 and I am on Android 4.4. I recently encountered the issue of my soft touch buttons (back, home, recent apps) being unresponsive, the rest of the screen works but my buttons don't respond to touch. I can still slide ip for Google now though.
I tried restarting my device and even upgraded to a newer build of 4.4, no luck.

R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app

parveen75 said:
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.

soulcedric said:
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
Click to expand...
Click to collapse
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?

lopezk38 said:
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
Click to expand...
Click to collapse
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc

soulcedric said:
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
Click to expand...
Click to collapse
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)

popinterfaces said:
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
Click to expand...
Click to collapse
I will try that, but it seems odd that other people would have the problem fixed after a screen replacement, which would identify it as a hardware issue.

maybe the screen replacement method (used by repair services/centers) came with a reset/flash of the rom.
What is even more strange is that some people seem to encounter the same bug again even after a screen replacement.
Please, keep us informed if the flash method solved the bug.
I'm currently still on 4.4.2 (for development needs) and i'm worried i could face the same problem !

I've confirmed that it's a hardware issue and has affected a lot of users who updated. I cannot touch the area of the screen in full screen apps.
Google should be warned and issue a statement about this, this is very bad news for us users.

The fact that it works after a screen replacement with no software modifications is proof enough. Time to vow to never buy a Google product again...

Temporary solution
any one has this problem should download any soft key app
BUTTON SAVIOR IS A good APP
it solved my problem
i advice you to try it
you can try any other app it's not advertisement you can use any soft key app i wrote this name just because i have tried it
good luck every one

Galaxy S5 black screen upon wake up

Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?

snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.

Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.

gee2012 said:
I would reflash the stock rom you have atm and data factory reset afterwards or try a data factory reset first and see if that fixes your issue.
Click to expand...
Click to collapse
I have tried factory resetting my phone but it doesnt help. Thanks anyways
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
I have added mot.proximity.delay=0 but i couldnt find ro.lge.proximity.delay=25. Is there any other way to fix this problem. I have to pull my battery out couple of times a day and its starting to get to me.
.
Click to expand...
Click to collapse

and now my mulitasking buttons are not working. any idea why?

snazer said:
Hey people, not sure if i'm the only s5 user whose experiencing this but sometimes when i wake my phone up, the touch capacitive buttons do light up but the screen stays black. any idea why?
Click to expand...
Click to collapse
I have the same issue... do you still get this issue? For me, sometimes, the screen does not wake up only the capacitive keys... I have to press the power button again to turn it off and then press power again to turn it on.

me too
Hi,
I'm having the same problem.
It was intermittent for a short while and a battery pull would fix it, now it's permanent.
I get capacitive buttons, I can boot into recovery or download.
I can hear touches on the screen and the annoying at$t boot sound is back since I used Odin to reflash to stock.
I think I have to take this phone to a service center and see if they will exchange it.
I'm worried that there may be traces of towelroot but from the thread that provides stock firmware and instructions for Odin it would seem that I'm good.
Has anyone had any luck with this issue or have any other tips to try?
I'm bummed because I just applied a glass protector and it looks like I'll have to get another.
Not to mention having to drive to the center.
Thanks.

With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.

For the record:
The at$t service center reflashed my phone and the screen works again.
IDK why flashing stock with odin did not work for me.
I can see from the post above mine that the problem might come back, I'll insist on a replacement if it does.

still getting the issue but for me I just need to press power 3 times for it to wake up; no need to remove battery
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Levus said:
With the new 1.100 motherboard version the problem is solved. It's a hardware defect. Maybe it will be fixed in next fw versions with some voltage or timing setting changes but a mobo change will definitely solve it.
Click to expand...
Click to collapse
how can i find out what mobo I have?
---------- Post added at 06:51 PM ---------- Previous post was at 06:05 PM ----------
fffft said:
Known bug. Supposedly fixed in recent firmware updates. More details in existing threads.
Or simply circumvent the issue entirely by upgrading to a good third party screen saver.
If you're ambitious, you could also try the following edit, which may help.
Make a backup first, then try editing build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
.
Click to expand...
Click to collapse
just rooted going to try this one thx

You can use the samsung phone info app from the market...

I haven't solved this issue as well... Please,did anyone of u guys solve this problem? If u did,please,tell me what to do... My screen stays black,only capacitive buttons lights,and I must press power button 5,6 times to wake up the screen. It's really annoying... :/

No solutions yet ???? I have this problem too...

walidhiphop said:
No solutions yet ???? I have this problem too...
Click to expand...
Click to collapse
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.

qubbus said:
It is lollipop 5.0 memory leak bug!
Also on CM12 (based on lollipop 5.0.2) problem occurs sometimes.
Click to expand...
Click to collapse
I'm having issue even using Kitkat 4.4.2

ZaKaTRoN said:
I'm having issue even using Kitkat 4.4.2
Click to expand...
Click to collapse
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.

knightrider558 said:
I also have the same problem, after lots of struggling I found little solution (it worked for me...), Just disable ur S-Health App, this app cause blank screen issue(this app uses sensors). Respond here if it worked for you.
Click to expand...
Click to collapse
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.

ZaKaTRoN said:
Thanks for your reply, but it didn't work.
No problem, tomorrow i'm buying s6, Phone House give me 210€ for my s5.
Click to expand...
Click to collapse
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?

knightrider558 said:
Great decision just get rid of these sam devices -_- , last try did you change the runtime system?
Click to expand...
Click to collapse
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.

ZaKaTRoN said:
I have upgrade every new software phe (spain), even lastest btu (united kingdom) because is newer than phe.
Also i sent twice to technical service.
One more time... I hate my s5!!!, hehe.
Click to expand...
Click to collapse
hahah... but this solution worked for me

[Q] phone does not wake up

Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.

..

yeahman45 said:
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
Click to expand...
Click to collapse
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.

vndnguyen said:
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
Click to expand...
Click to collapse
It's a hardware defect. Mine was like this too since 11th april. After changing the motherboard to the newer, 1.1100 version, the problem is competeley gone away. It's waking up every time correctly.
We had a topic about this earlier...

Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted

yeahman45 said:
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
Click to expand...
Click to collapse
I'm totally sure because i had this bug from the beginning. I was trying all firmware updates, factory reset, etc. It's not related to the fingerprint sensor or any app installed or not.

Ok i have no choice. Will try the solutions i read from google, seems to he a common issue

yeahman45 said:
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
Click to expand...
Click to collapse
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .

Levus said:
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Click to expand...
Click to collapse
anyone else can confirm it's a hardware issue? does it get worse with time? I still get it (but seems worse sometimes, where i need to press power button several times to wake it up) and i have tried a lot of suggestions

anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?

yeahman45 said:
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
Click to expand...
Click to collapse
anyone can report if it also happens with a non touchwiz rom?? I can't flash one as my phone is still under warranty

no one can't reply? so this issue is not common after all?

guys i am going to void my warranty to flash cm12... does it solve this issue??

adit said:
Re-activation lock only works when knox is 0x0 but that too can be bypassed by installing custom rom so...
Click to expand...
Click to collapse
I can not install custom in my own phone ...0x1...after install xtrolite 2.2....f...

Have someone solved the problem by flashing a custom kernel? Still getting the issue on latest lollipop rom