Develop Bugs

Jellybean problems

First off, if this has already been done then sorry im obviously blind, if not then i think its a good place to post any jellybean related problems and fixes that people have discovered.
so here goes, i updated from the ota on thursday the 12th of july i had a totally stock yakju device with the build number imm761 (JRO03c after update)
problems i have found so far are
1.after every reboot the, screen stay awake during charging option is ticked in developer settings
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks

Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.

GldRush98 said:
Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.
Click to expand...
Click to collapse
yes i knew i forgot something thanks also the option to enable this feature randomly disappears

I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
And when I want to charge the power source does not load.
Last night I put in charge and not loaded than when we closed and I pressed power button + down button.
and camera, how do I set resolution? I make pictures. PNG 720x1280 on ICS I could change the resolution,
Jealybean sucks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shot at 2012-07-19

tuice said:
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
You have reached the Holy Grail of getting power to a mobile device—this is not a problem/consider yourself very lucky.

I do not think this is too good for battery life, and actually not charge only indicate that charge

Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2

omrij said:
Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didn't have this before upgrading to Jealybean

tuice said:
I didn't have this before upgrading to Jealybean
Click to expand...
Click to collapse
That's a pretty common Samsung issue, usb port dirty, faulty.
Either clean it or go to repair.

leeskywalker said:
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks
Click to expand...
Click to collapse
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella

I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.

Taboobat said:
I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.
Click to expand...
Click to collapse
i found after a reboot while plugged in it will go to 100%

cymru said:
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella
Click to expand...
Click to collapse
i have my address set in every possible place of my google account still no luck

I've never been able to get Google Now to start voice recognition by saying Google. I was beginning to think it was just a myth. Any ideas how to force it?
Sent from my Galaxy Nexus using Tapatalk 2

tuice said:
I do not think this is too good for battery life, and actually not charge only indicate that charge
Click to expand...
Click to collapse
Battery stats is what's responsible for indicating charge to my knowledge. Try wiping battery stats in CWM

tuice said:
I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
I've seen this happen before on a brand new HTC X One, happened after about 4 days of being used. We let the phone fully run down and then just changed it, didn't come back again.

Some Complaints about the i747

Coming from an HTC Vision running CM. Here are my complaints. Maybe there are easy fixes for them. Dunno... (my phone is rooted)
1. Battery drains faster than car can charge it. With screen on, GPS on, and data on and using navigation, the battery goes down. This hasn't happened with any of my other phones.
2. There is no simple way to go to speech recognition/input from the keyboard. On the keyboard on my last phone, there was a microphone button on the keyboard I could press to bring up speech recognition.
3. There is no widget you can put on the homepage that immediately opens up voice search. Last phone, I hit one button on the home screen and I said "set alarm for twenty minutes" or "text lisa smith I'm running late" or "Dial dominos pizza" and it just did it.
4. I can't seem to control what kind of data connection I am using. I use to be able to specify to use 2G if I wanted on the last phone.

synpax said:
Coming from an HTC Vision running CM. Here are my complaints. Maybe there are easy fixes for them. Dunno... (my phone is rooted)
1. Battery drains faster than car can charge it. With screen on, GPS on, and data on and using navigation, the battery goes down. This hasn't happened with any of my other phones.
2. There is no simple way to go to speech recognition/input from the keyboard. On the keyboard on my last phone, there was a microphone button on the keyboard I could press to bring up speech recognition.
3. There is no widget you can put on the homepage that immediately opens up voice search. Last phone, I hit one button on the home screen and I said "set alarm for twenty minutes" or "text lisa smith I'm running late" or "Dial dominos pizza" and it just did it.
4. I can't seem to control what kind of data connection I am using. I use to be able to specify to use 2G if I wanted on the last phone.
Click to expand...
Click to collapse
1. Umm install a custom kernel/rom, my battery life is amazing with AOKP and KT747
2.I am pretty sure there is, but i dont use it
3.yes there is a google voice search widget
4.yes you can go to your more setting under bluetooth, then mobile networks. The option is there

What custom kernal do you recommend? And all the roms seem to cost me functionaloty.
Sent from my SAMSUNG-SGH-I747 using xda premium

synpax said:
What custom kernal do you recommend? And all the roms seem to cost me functionaloty.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
KT747 its located in the original android development section, here is the thread.
http://forum.xda-developers.com/showthread.php?t=1756776
I am still running ICS though since its still to early on in JB's life cycle for GS3 development.

I wish I had #2 as well.

The latest jellybean aokp has been working flawless for me. The previous one had a couple issues but they seem to be solved. Battery life is good.

If you're using the stock keyboard, go to settings>language and input and click the cog to the right on the Samsung keyboard. Make sure voice input is checked and you'll have a mic button on the keyboard to the left of the space bar.
Sent from my Nexus 7 using Tapatalk 2

KentuckyHouse said:
If you're using the stock keyboard, go to settings>language and input and click the cog to the right on the Samsung keyboard. Make sure voice input is checked and you'll have a mic button on the keyboard to the left of the space bar.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
thanks for clearing this up! i knew there was a way, but I never use voice input/search

CaLiSwEEPeR said:
thanks for clearing this up! i knew there was a way, but I never use voice input/search
Click to expand...
Click to collapse
No problem, man. Glad I could help!
Sent from my Nexus 7 using Tapatalk 2

KentuckyHouse said:
If you're using the stock keyboard, go to settings>language and input and click the cog to the right on the Samsung keyboard. Make sure voice input is checked and you'll have a mic button on the keyboard to the left of the space bar.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I saw that but it didn't seem to work. However, you need to long-press that settings button to get the microphone.
I've found the speech recognition intermittently is either brilliant or stupid/non-functional.

For the mic on keyboard use either the ICS or JB keyboard, if your current ROM doesn't have it, get it from the market.
Sent from my SAMSUNG-SGH-I747 using xda premium

Flash custom ROM!
Flash custom ROM and all your problems will be gone.
Instead - you will have flasher hemorrhage and seeking solutions for ROM bugs.

As far charging keeping up.... I took a short USB extension. Opened up the cable. There were 4 wires inside.... red, black, green and white. Cut the green and white wires. Strip the white and green wires coming from the phone side of the USB and short them together. Use electrical tape to tape them up.
The phone charges from the cigarette lighter at 4000-5000 milliamps. The phone charges from the electrical outlet at 9000 milliamps - 1 amp. When plugged in to in to a lighter the green and white are the data cables and are open. When plugged into a wall charger, the wires are sorted which enables fast charging. There is an app/widget called current widget I believe that shows you what you are charging at.
Sent from my SGH-I747M using xda premium

synpax said:
Coming from an HTC Vision running CM. Here are my complaints. Maybe there are easy fixes for them. Dunno... (my phone is rooted)
1. Battery drains faster than car can charge it. With screen on, GPS on, and data on and using navigation, the battery goes down. This hasn't happened with any of my other phones.
2. There is no simple way to go to speech recognition/input from the keyboard. On the keyboard on my last phone, there was a microphone button on the keyboard I could press to bring up speech recognition.
3. There is no widget you can put on the homepage that immediately opens up voice search. Last phone, I hit one button on the home screen and I said "set alarm for twenty minutes" or "text lisa smith I'm running late" or "Dial dominos pizza" and it just did it.
4. I can't seem to control what kind of data connection I am using. I use to be able to specify to use 2G if I wanted on the last phone.
Click to expand...
Click to collapse
1. Have any of your other phones had a battery with the capacity of this phone? My suggestion would be to get a 1a car charger....I'd guess your current charger puts out 500ma-750ma or about as much as charging via pc usb port. Yep, it'll take forever. But when you use a 1a charger it'll charge much faster. I have the same problem with my usb car charger....at least until my Satechi 2.1a charger arrives on Wednesday
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It won't charge any faster than using a 1a charger even though it can put out 2.1a due to the IC in the phone that regulates the charging, but having the headroom is nice for use with other devices that can use it.
2. I don't use the stock ICS keyboard, I prefer GoKeyboard myself, and on it I can choose to have the speech recognition key displayed if I want.
3. A simple double tap of the home button will launch S-Voice...no need to take up valuable homescreen space with a widget
4. That one there is not a fix for yet

This phone uses microsim.

Gadgetz said:
A simple double tap of the home button will launch S-Voice...no need to take up valuable homescreen space with a widget
Click to expand...
Click to collapse
You can also use this method if you would prefer to launch Google Voice search from the home button: http://sgs3mod.blogspot.ca/2012/07/heres-how-to-launch-google-voice-search.html

"OK Google" Detection Kills Voice Recording

Sometime in the past 48 hours, I got the new option in Google Now to enable the "OK Google" hotword detection from any screen, so of course I went ahead and turned it on, and have been loving it.
A little while ago, I went to record something with the stock Voice Recorder (which unfortunately is something I do quite often), and it won't record. It gives me a message "Unable to start a new recording. Other applications already recording". So I go back into Google, disable the hotword detection from any screen, and look and behold, Voice Recorder works again.
I haven't tried any other recording apps yet to see if they have the same conflict, but I intend to shortly. I just figured I'd let others know about the issue. It seems like a huge oversight on Google's part that such a highly anticipated feature would break one of the stock functions on a popular flagship device. Hopefully they push a fix soon, or someone here finds a way around the problem....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900T

Just checked, mine too. Fortunately, I have never had a need to use voice recorder.

how do you make it work did you get a update
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
Morningstar said:
Sometime in the past 48 hours, I got the new option in Google Now to enable the "OK Google" hotword detection from any screen, so of course I went ahead and turned it on, and have been loving it.
A little while ago, I went to record something with the stock Voice Recorder (which unfortunately is something I do quite often), and it won't record. It gives me a message "Unable to start a new recording. Other applications already recording". So I go back into Google, disable the hotword detection from any screen, and look and behold, Voice Recorder works again.
I haven't tried any other recording apps yet to see if they have the same conflict, but I intend to shortly. I just figured I'd let others know about the issue. It seems like a huge oversight on Google's part that such a highly anticipated feature would break one of the stock functions on a popular flagship device. Hopefully they push a fix soon, or someone here finds a way around the problem....
Sent from my SM-N900T
Click to expand...
Click to collapse
hey i want to get that on my note 3 how does it work

mrej201 said:
how do you make it work did you get a update
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
Click to expand...
Click to collapse
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T

Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse
thanx and yea i want the feature for so long

Yeah, just search for 'unleashthegoogle'. I used it on another device, and it's quite easy and only takes a few seconds, but I don't remember exactly what you have to enable off the top of my head, so search for the apk and the instructions.
Sent from my SM-N900T

Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse
try the app but it wont work

phil.culler said:
Just checked, mine too. Fortunately, I have never had a need to use voice recorder.
Click to expand...
Click to collapse
Hmm, this is interesting (and not good at all).
Did anyone try this with call recording?
One fix I can think of before Google fixes it, have a Tasker / Xposed module that disables Google Search when the whitelisted (recording) apps are running. Can some dev confirm this?
I don't have the update yet and unleashthegoogle doesnt seem to work. So can't test.

mrej201 said:
try the app but it wont work
Click to expand...
Click to collapse
https://plus.google.com/app/basic/stream/z12sczagllb1inism235gtbp1mb2j3qb204
This post describes how to do it. I just did it. Interesting that it disables recording voice. I wonder if it breaks video recording audio...
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
I tested the voice on my video recording and it didn't break that. It works fine. I even said the hot word, okay google, and it was fine. Also, the Google keyboard seems to work fine with dictating words as well. I'm dictating this right now.
To the guy above me that's a really good idea, blacklisting Google during certain apps.
Sent from my SM-N900T using XDA Free mobile app

I just tried a few things, and the only thing I've found that it breaks is the stock Voice Recorder app. Camera audio recording works, two guitar tuner apps I have work, and the three 3rd party voice recording apps I tried all work flawlessly. One of them lets you select which microphone to record from, and all those options work fine as well. I haven't tried with call recording, as it's not something I use, but i would imagine it works fine, since hotword detection is (presumably) disabled during a call.
The Tasker idea is a damn good one, and I may just set something like that up in a while. What I'd like to know now, is if the same problem exists on other Samsung devices, or if it's just the Note 3 that's affected...
Sent from my SM-N900T

Dunno why it breaks it, but if you have root and want an alternative, google now for 3rd party launchers xposed module works great for me and it doesn't break any sound recording.
Sent from my SM-N900T using XDA Free mobile app

Yeah, there's several things I can do as an alternative. Right now I'm just using a different voice recorder; might set up a Tasker profile later.
It's not that big of a deal, really. It's just annoying/surprising/disappointing that such a highly sought-after and anticipated feature breaks some of the core functionality on a high-end, popular, flagship device. It's even worse if the issue exists on all Samsung (Touchwiz) devices, which I'm trying to determine. Google dropped the ball on this one...
Sent from my SM-N900T

There's a minor update to Google Search rolling out. I haven't been able to find a changelog anywhere yet, but I just checked it out, and unfortunately it still breaks Voice Recorder. *sigh*
Sent from my SM-N900T

from the screen- select Apps - google folder - google setting- search & now - turn on google now and follow the instructions
Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse

got mine to work
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.

sharpjustin18 said:
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.
Click to expand...
Click to collapse
I just tried that and it didn't work for me. Anyone find a fix for this yet? Or at least a formal bug report somewhere?

sharpjustin18 said:
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.
Click to expand...
Click to collapse
travipross said:
I just tried that and it didn't work for me. Anyone find a fix for this yet? Or at least a formal bug report somewhere?
Click to expand...
Click to collapse
I just tried the suggestion above and it is working for me now. I have not restarted yet and I am not sure if it will stick, but thought ill pass this along.:good:

DesperateScorpion said:
I just tried the suggestion above and it is working for me now. I have not restarted yet and I am not sure if it will stick, but thought ill pass this along.:good:
Click to expand...
Click to collapse
Thanks for the input. I tried again just to be sure. I turn hotword detection off, start a recording, then turn hotword detection back on during the ongoing recording. The recording will continue until I stop it, but I can't start a new one immediately after.

travipross said:
Thanks for the input. I tried again just to be sure. I turn hotword detection off, start a recording, then turn hotword detection back on during the ongoing recording. The recording will continue until I stop it, but I can't start a new one immediately after.
Click to expand...
Click to collapse
Well, it doesn't stick. After a restart its back to the same issue. Did you try using a third party recorder?

DesperateScorpion said:
Well, it doesn't stick. After a restart its back to the same issue. Did you try using a third party recorder?
Click to expand...
Click to collapse
I haven't tried using a third party recorder, no. My workaround for the time being is to just use the "OK Google from home screen" option in Nova Launcher, as opposed to "OK Google anywhere" in Google Search.
It turns out the Google Search option also distorts hangouts voice calls on some Galaxy S4s so theres more than one reason to avoid it until it gets fixed. Fortunately the home screen detection on Nova Launcher doesn't share these issues.

Finger print reader doesn't work

Anyone's reader doesn't work sometime?
I've had much trouble with it not working and actually promoting many errors.
After many times re-registering my prints, I got it to work well. Now since yesterday morning, the reader just flat out doesn't know a finger is placed. No vibrate, just screen times out. Sometimes it'll vibrate once no match then fail to notice my finger thereafter.
Anyone else have these problems?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G920P

hayabusa1300cc said:
Anyone's reader doesn't work sometime?
I've had much trouble with it not working and actually promoting many errors.
After many times re-registering my prints, I got it to work well. Now since yesterday morning, the reader just flat out doesn't know a finger is placed. No vibrate, just screen times out. Sometimes it'll vibrate once no match then fail to notice my finger thereafter.
Anyone else have these problems?
View attachment 3286301
Sent from my SM-G920P
Click to expand...
Click to collapse
I had this exact issue last friday. After a full restore the fingerprint reader still wouldn't register any touches. I took it to the sprint store and they gave me a new S6. There are some other threads in the T-mo forum where people are experiencing the same issue.

balistic2 said:
I had this exact issue last friday. After a full restore the fingerprint reader still wouldn't register any touches. I took it to the sprint store and they gave me a new S6. There are some other threads in the T-mo forum where people are experiencing the same issue.
Click to expand...
Click to collapse
Thanks for the info. I've been trying to get past it, avoid exchanging. But just might...
Sent from my SM-G920P

Try a complete shutdown. Boot into recovery and wipe cache then restart.

JoeFCaputo113 said:
Try a complete shutdown. Boot into recovery and wipe cache then restart.
Click to expand...
Click to collapse
Didn't work. I know what's going on partially. There is a huge delay in registering the finger, why? Idk.
You can validate on this screen. Takes 5 secs to notice and 3 to respond to taking finger off
Sent from my SM-G920P

Ok so trying to figure out what's wrong, I wanted to reboot the finger print service, thinking there was a process running for it. Sure enough I found it. I stopped it, and now it is running as efficient as it was before. Pretty awesome.
Sent from my SM-G920P

hayabusa1300cc said:
Anyone's reader doesn't work sometime?
I've had much trouble with it not working and actually promoting many errors.
After many times re-registering my prints, I got it to work well. Now since yeste
rday morning, the reader just flat out doesn't know a finger is placed. No vibrate, just screen times out. Sometimes it'll vibrate once no match then fail to notice my finger thereafter.
Anyone else have these problems?
View attachment 3286301
Sent from my SM-G920P
Click to expand...
Click to collapse
Nice to see you here hayabusa. We seem to have the same tastes in phones! Anyway, I had similar issues and so have others. This may be turning into a common issue! You can follow the link I posted in this thread for others having this issue.
http://forum.xda-developers.com/sprint-galaxy-s6/help/fingerprint-scanner-issues-t3087896
I returned my first s6 on day 13 and got a new device with basically no hassles.

thunderwagn said:
Nice to see you here hayabusa. We seem to have the same tastes in phones! Anyway, I had similar issues and so have others. This may be turning into a common issue! You can follow the link I posted in this thread for others having this issue.
http://forum.xda-developers.com/sprint-galaxy-s6/help/fingerprint-scanner-issues-t3087896
I returned my first s6 on day 13 and got a new device with basically no hassles.
Click to expand...
Click to collapse
Thanks I read that today after I made my post, I'll post my solution because it works for me great now. And yes I think last I saw you was the s4 lol
Sent from my SM-G920P

hayabusa1300cc said:
Thanks I read that today after I made my post, I'll post my solution because it works for me great now. And yes I think last I saw you was the s4 lol
Sent from my SM-G920P
Click to expand...
Click to collapse
Lg g3 wasn't it?
I hope you have no more issues with the s6!

thunderwagn said:
Lg g3 wasn't it?
I hope you have no more issues with the s6!
Click to expand...
Click to collapse
Definitely the LG G3 I skipped a gen haha
No more issues other than this, that's why I didn't want to give it up. Now they do need to do an update for ram optimizations cause it currently sucks, can't multitask with apps closing out.
Sent from my SM-G920P

having the same problem with S6 Edge

Same issue here. Was at work showing a customer mine... fingerprint scanner failed to recognize any of my fingers.
Backup Password would not open my phone either. After entering my Google information multiple times, I had to resort to a full device reset in order to have a working device.
Not exactly what I was expecting from this. I had no problems whatsoever up until that point. The device simply went to sleep and the fingerprint scanner stopped working at all.
After searching it seems to be a bit more widespread than anticipated. All carriers are seeing the issue.

Damn. It's random when it works or not
Sent from my SM-G920P

Here is video I recorded of the issue. Clearly you can see how it doesn't work as intended delayed response.
https://youtu.be/ZlVZN39f4sQ
The reader is defective. It senses my finger on the button well after I have taken it off. Notice it says "lift my finger.." I can no longer blaze through it as when it did work.
Watch my video again, then watch wwwjoshdew video of how it's Supposed to work
How To Setup the Fingerprint Scanner on the Galax…: https://youtu.be/GJqdr0PNV5E
Sent from my SM-G920P

hayabusa1300cc said:
Here is video I recorded of the issue. Clearly you can see how it doesn't work as intended delayed response.
https://youtu.be/ZlVZN39f4sQ
Sent from my SM-G920P
Click to expand...
Click to collapse
I don't think you quite understand how it's supposed to work. You want to read as much of your thumb as possible, not just keep placing it in the same spot. That means placing it in different positions and different ways. I read most of my thumb and now It unlocks in a second from any angle. But yes, the initial reading takes a long time.

jptech said:
I don't think you quite understand how it's supposed to work. You want to read as much of your thumb as possible, not just keep placing it in the same spot. That means placing it in different positions and different ways. I read most of my thumb and now It unlocks in a second from any angle. But yes, the initial reading takes a long time.
Click to expand...
Click to collapse
I understand completely how it works. The issue is not my angle. For demo, I recorded my print this way and that's fine. But you fail to see the actual issue at hand. The reader is defective. It senses my finger on the button well after I have taken it off. Notice it says "lift my finger.." I can no longer blaze through it as when it did work.
Watch my video again, then watch wwwjoshdew video of how it's Supposed to work
How To Setup the Fingerprint Scanner on the Galax…: https://youtu.be/GJqdr0PNV5E
Sent from my SM-G920P

hayabusa1300cc said:
I understand completely how it works. The issue is not my angle. For demo, I recorded my print this way and that's fine. But you fail to see the actual issue at hand. The reader is defective. It senses my finger on the button well after I have taken it off. Notice it says "lift my finger.." I can no longer blaze through it as when it did work.
Watch my video again, then watch wwwjoshdew video of how it's Supposed to work
How To Setup the Fingerprint Scanner on the Galax…: https://youtu.be/GJqdr0PNV5E
Sent from my SM-G920P
Click to expand...
Click to collapse
Maybe you're experiencing the memory leak to cause that sort of behavior. After the first fingerprint reading, mine always had timing issues, and it turns out it was fixed after I deleted the fingerprints and rebooted my phone.

jptech said:
Maybe you're experiencing the memory leak to cause that sort of behavior. After the first fingerprint reading, mine always had timing issues, and it turns out it was fixed after I deleted the fingerprints and rebooted my phone.
Click to expand...
Click to collapse
Yeah I know I have memory leak for sure. My home screen reloads often, I have to close out all apps then it'll be fine for a little bit. I wiped cache from recovery, reboot etc. The reader remains unusable still. Seems like this isn't widespread but still affects some of us users, not to mention the ones that don't frequent XDA. I understand 5.1.1 aims to fix memory leak. Sucks but still the best phone I ever had.
Sent from my SM-G920P

Just updating that I did a factory reset, and has cured my ailing print reader issue.

I had a similar issue its been random, i have been unable to narrow it down, so due to frustration I have stopped using it I will attempt to reset it and do it again. I love the feature when my nieces try to take my phone and they cant get in.

LG G4 screen turning itself on after timeout/lock

I've had the G4 since it was launched and until now been very pleased. A couple of days ago it started to turn the screen on by itself every time it timed out or I pressed the lock button... Unless it's plugged into a charger.
I've tried pulling the battery and uninstalling any recent apps I'd installed but to no avail.
Annoyingly, by the time I got myself to carphone warehouse to get it sorted I was just outside my 28 days.
Seen a lot of people having issues with the screen but can't find anyone having this exact problem. Anybody experiencing similar? Any thoughts? Cheers.
Sent from my LG-H815 using XDA Free mobile app

Guess there's not a lot of people suffering the same issue... Noticed something odd today with the battery. Never seen it drain this fast before, is there any way the screen issue could be related to the battery? It would kinda corroborate that the phone acts totally normal when it's charging... Trying to find someone else with this phone to try swapping batteries is... Difficult.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H815 using XDA Free mobile app

Factory reset.

Done it, twice.
Sent from my LG-H815 using XDA Free mobile app

Do you have a screen protector on? If you do, is it possibly covering the light/prox sensor?

Nope, no protector, and I often manually cover the proximity sensor to demonstrate more easily what the phone's doing. Screen times out straight away and them comes back on just as quickly.

Same issue here
Sorry to drag up a thread but ive been having this issue from day 1 and its driving me MAAAAD! Press the lock screen button, the second the screen turns off it comes back on and its on the lock screen (like it would if i used the power button to unlock it)
I turned on "show touch screen touches " in developer options to see if the screen protector was touching anything but its not As far as i can tell it looks like the lock screen sensor might be dicky/weak from the factory? Major sads considering its the button I use on a hourly basis!
Any help or ideas greatly appreciated, i dont really fancy taking it back after 4 weeks to have it sent of for months to be looked at/repaired

H815P suffering the same but mine is randomly. I hardly ever notice but sometimes I just look at the phone and the screen is on.

Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?

volkie1912 said:
Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?
Click to expand...
Click to collapse
do you use greenify on unrooted phone?

vati said:
do you use greenify on unrooted phone?
Click to expand...
Click to collapse
yea, i am using greenify on unroot phone

volkie1912 said:
yea, i am using greenify on unroot phone
Click to expand...
Click to collapse
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation. On unrooted phone it cause more battery drain than running the pr in the background

vati said:
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation.
Click to expand...
Click to collapse
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?

volkie1912 said:
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?
Click to expand...
Click to collapse
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.

vati said:
es, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Thanks for info dude[emoji106]
Sent from my LG-H815 using Tapatalk

vati said:
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:

turn off daydream clock in display settings
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
choroz_niki said:
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:
Click to expand...
Click to collapse
turn daydream clock display settings

Hey its the sensors next the the front camera that is causing this i had this look reply typed and it just disappeared but long story short i noticed it didnt down it when the phone was facedown so i tried covering the sensors next to the front camera and it didnt do it at this point it could just be a program error or hardware problem idk how it turn off the sensors and it may look tacky but use something to cover the sensors and you should be fine im not 100% sure this is the problem im still testing but so far it works

Try disabling knock to wake feature. I recently noticed that I could tap anywhere and then again somewhere else, minutes later, and the screen would turn on. It was so sensitive that sometimes it would wake by just blowing on the screen.
To get to this setting, I created an activity widget using Nova launcher. (It's under the Settings -> Knock settings).
You can also use Better Battery Stats or Amplify to see what's keeping your screen on

fixed mine
Here you go...
Settings > Display > Motion Sensor Calibration