Related
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!
Was just wondering if anyone with the T807 10.5 tablet might want to share any news as to gaining root for our devices. I've begun feeling like the bastard child over here. This is my first tablet and I love how well it's performing. I just really hope that the processor in this model is not worth anyones effort to try to work on.
At any rate, should anyone want to share any news or any other info on the T807 model matbe this can be the place to start ! I surly can't be alone .. can I ?? Maybe we can get some sharp developers attention.
Longball said:
Was just wondering if anyone with the T807 10.5 tablet might want to share any news as to gaining root for our devices. I've begun feeling like the bastard child over here. This is my first tablet and I love how well it's performing. I just really hope that the processor in this model is not worth anyones effort to try to work on.
At any rate, should anyone want to share any news or any other info on the T807 model matbe this can be the place to start ! I surly can't be alone .. can I ?? Maybe we can get some sharp developers attention.
Click to expand...
Click to collapse
No news yet. Btw, how is yout tablet's battery performs?Mine suck, it went down 20% in 2 hours with very little usage
I'm right here with you. I check Xda every day. I have pm'd chainfire already but nothing yet until the firmware is release I guess. I have tried to extract the recovery but no luck. I guess it's going to be a waiting game.
Sent from my SPH-L720 using Xparent Blue Tapatalk 2
I just picked up one today. And you guys arent alone on this one. Looks like I'll be checking around often. ha.
Longball said:
Was just wondering if anyone with the T807 10.5 tablet might want to share any news as to gaining root for our devices. I've begun feeling like the bastard child over here. This is my first tablet and I love how well it's performing. I just really hope that the processor in this model is not worth anyones effort to try to work on.
At any rate, should anyone want to share any news or any other info on the T807 model matbe this can be the place to start ! I surly can't be alone .. can I ?? Maybe we can get some sharp developers attention.
Click to expand...
Click to collapse
Thanks for bringing this up I've had my tablet since the 6th and I've been itching to root...
Sent from my SM-T807P using XDA Free mobile app
BADBOY1412 said:
No news yet. Btw, how is yout tablet's battery performs?Mine suck, it went down 20% in 2 hours with very little usage
Click to expand...
Click to collapse
Battery is not an issue. I've only had mine two weeks. I watch a lot of videos on CNN and YouTube. When I first got the tablet my battery did seem a little sluggish. most likely the result of all the crap that was being downloaded automatically the first day or two. I noticed now that after a few cycles of charging things have settled down and I'm getting adequate battery life. to be honest this tablet is a beast and I love it. I've watched close to an hours worth of videos this morning only down 7 percent. maybe you have some rogue application running in the background ?
Q andUOTE=shanda5303;56104820]Thanks for bringing this up I've had my tablet since the 6th and I've been itching to root...
Sent from my SM-T807P using XDA Free mobile app[/QUOTE]
I didn't even have mine out of the box that it came in and I was on XDA already! I was just getting ready to install the t-800 version when I realized I had the T807 model. anyway I'm just glad I'm not alone
I got mine right when it was available from sprint and at first there was one other person on here looking but the number of people are climbing everyday. Hopefully the firmware is released soon and we will have root shortly after.
Sent from my SPH-L720 using Xparent Blue Tapatalk 2
possible solution...theres a catch of course
Longball said:
Was just wondering if anyone with the T807 10.5 tablet might want to share any news as to gaining root for our devices. I've begun feeling like the bastard child over here. This is my first tablet and I love how well it's performing. I just really hope that the processor in this model is not worth anyones effort to try to work on.
At any rate, should anyone want to share any news or any other info on the T807 model matbe this can be the place to start ! I surly can't be alone .. can I ?? Maybe we can get some sharp developers attention.
Click to expand...
Click to collapse
shanda5303 said:
Thanks for bringing this up I've had my tablet since the 6th and I've been itching to root...
Sent from my SM-T807P using XDA Free mobile app
Click to expand...
Click to collapse
BADBOY1412 said:
No news yet. Btw, how is yout tablet's battery performs?Mine suck, it went down 20% in 2 hours with very little usage
Click to expand...
Click to collapse
bcombel said:
I'm right here with you. I check Xda every day. I have pm'd chainfire already but nothing yet until the firmware is release I guess. I have tried to extract the recovery but no luck. I guess it's going to be a waiting game.
Sent from my SPH-L720 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Tahde said:
I just picked up one today. And you guys arent alone on this one. Looks like I'll be checking around often. ha.
Click to expand...
Click to collapse
I AM NOT RESPONSIBLE IF U DAMAGE YOUR DEVICE OR DELETE DATA....PLEASE ATTEMPT THIS AT YOUR OWN RISK!
first i suggest reading through the thread linked below so u will know what i do...long story short though there is a user here by the name of @BDA_Rival who basically did the worse thing possible by trying to root his SNAPDRAGON 807 with an EXYNOS 805 cf auto root and as u may have guess ended up soft bricking it (its hard to actually permanently break it...although the fact that the odin firmware is unavailable at the moment is a bit of an issue). The ONLY reason i'm even suggesting this is because there is a known working way of getting the tab back booting & worse case u can return it & say it messed up during an over the air update or something. Ok...so what ended up saving the other guy was twrp for the NOTE PRO 12.2 905 LTE which is not only snapdragon but apparently uses the same partition structure (just to be clear...twrp only caused the device to become bootable again but does NOT actually function properly most likely due to different display drivers). So....with all of that said it is QUITE possible that the cfauto root file for the P905 could be used to root the sprint/verizon (full disclosure...the other users tab was a sprint variant) version of the tab s! Did i mention that there was a catch...well even if this does work due to the nature of how @Chainfire root method works u will be left with a copy of the stock note pro recovery instead of the origial 807 version which most likely will NOT work combined with the fact that there is a no cwm or twrp for your device yet (should be an easy fix if we could get the devs attention) and u will be left with a device that boots possibly with root as well but WITHOUT recovery.
http://forum.xda-developers.com/galaxy-tab-s/help/firmware-sm-t807p-t2884192/page2
^807 root brick thread (advise reading before trying...its only 2 pages long)
just wanted to add...the user tried the suggested autoroot in post #6 but that didnt work & the one mentioned here is linked in post #14
Id love to root, but I am perfectly fine holding off until we have our versions firmware available. Root is another thing (as I've noticed lately with phones) that I have seen, where users can obtain root with other similar models. Having TWRP from the Note Pro work is going in the right direction for us.
I'll definitely be watching the thread you linked. Thanks for your post.
P
BADBOY1412 said:
No news yet. Btw, how is yout tablet's battery performs?Mine suck, it went down 20% in 2 hours with very little usage
Click to expand...
Click to collapse
I usually get 4.5 days per charge with 7 plus hours of screen time. Lots of Web surfing on network and youtube. There is a trick to condition your battery when you first use a new device it solve your issue currently.
I always setup then use my new device until the battery dies. Then recharge fully before the next use.
My setup includes tuning the sound, I disable all click tones and vibrations including touch vibration
WIFI
WiFi alway on, ALL Wifi >Advanced options disabled
SCREEN
The display I set to 25% then set to auto
Screen timeout set to 30 seconds
Smart screen disable reading disabled
Reading mode Disney
SYNC ACCOUNT
Gmail sync all disabled (when I read my Gmail I manually sync)
I have two email accounts I sync automatically for my business
GPS
GPS disbled unless in use
Disable locations and notification for all apps expect Google maps
MESSAGING
Messaging notification on but sound disabled
WIDGETS
Weather widget set to refresh hourly (this is the only widget I used which syncs)
No Facebook Twitter or other accounts , If I had them I would sync them manually
I also have a cover with magnets which disables screen when I close the cover
The procedure has become second nature for all my new devices
SG Note OG , note 2 and 3. On these phone I get 7 plus hours of talk time per day mostly on bluetooth with 2 - 3 hours of screen time over 18 hours mostly on the network, and moderate music streaming
I hope this helps
Ethan me know. ..
Sent from my SM-T807V using XDA Free mobile app
sdglenn said:
P
I usually get 4.5 days per charge with 7 plus hours of screen time. Lots of Web surfing on network and youtube. There is a trick to condition your battery when you first use a new device it solve your issue currently.
I always setup then use my new device until the battery dies. Then recharge fully before the next use.
My setup includes tuning the sound, I disable all click tones and vibrations including touch vibration
WIFI
WiFi alway on, ALL Wifi >Advanced options disabled
SCREEN
The display I set to 25% then set to auto
Screen timeout set to 30 seconds
Smart screen disable reading disabled
Reading mode Disney
SYNC ACCOUNT
Gmail sync all disabled (when I read my Gmail I manually sync)
I have two email accounts I sync automatically for my business
GPS
GPS disbled unless in use
Disable locations and notification for all apps expect Google maps
MESSAGING
Messaging notification on but sound disabled
WIDGETS
Weather widget set to refresh hourly (this is the only widget I used which syncs)
No Facebook Twitter or other accounts , If I had them I would sync them manually
I also have a cover with magnets which disables screen when I close the cover
The procedure has become second nature for all my new devices
SG Note OG , note 2 and 3. On these phone I get 7 plus hours of talk time per day mostly on bluetooth with 2 - 3 hours of screen time over 18 hours mostly on the network, and moderate music streaming
I hope this helps
Ethan me know. ..
Sent from my SM-T807V using XDA Free mobile app
Click to expand...
Click to collapse
What i do is I turn wifi scanning off when connected to a network. I also set my brightness to 25 percent and keep auto brightness off which works better for me. Smart stay on, adapt display off and set to cimema mode, smart pause off, and debloated some things such as knox,flipboard,buiness+,sidesync since im rooted. Hope this helps for anyone else too!
We need to be careful about these threads-- evidently ALL US LTE versions have the SM-T**7 naming convention, including the exynos AT&T version. As far as I know, the Verizon and Sprint versions are T807.
I have the t807 for tmobile ( non snapdragon )
used the 805 auto root.
worked just fine.
I am not trying anything else, such as twrp and roms
unit the official development is done
THEDEVIOUS1 said:
I AM NOT RESPONSIBLE IF U DAMAGE YOUR DEVICE OR DELETE DATA....PLEASE ATTEMPT THIS AT YOUR OWN RISK!
first i suggest reading through the thread linked below so u will know what i do...long story short though there is a user here by the name of @BDA_Rival who basically did the worse thing possible by trying to root his SNAPDRAGON 807 with an EXYNOS 805 cf auto root and as u may have guess ended up soft bricking it (its hard to actually permanently break it...although the fact that the odin firmware is unavailable at the moment is a bit of an issue). The ONLY reason i'm even suggesting this is because there is a known working way of getting the tab back booting & worse case u can return it & say it messed up during an over the air update or something. Ok...so what ended up saving the other guy was twrp for the NOTE PRO 12.2 905 LTE which is not only snapdragon but apparently uses the same partition structure (just to be clear...twrp only caused the device to become bootable again but does NOT actually function properly most likely due to different display drivers). So....with all of that said it is QUITE possible that the cfauto root file for the P905 could be used to root the sprint/verizon (full disclosure...the other users tab was a sprint variant) version of the tab s! Did i mention that there was a catch...well even if this does work due to the nature of how @Chainfire root method works u will be left with a copy of the stock note pro recovery instead of the origial 807 version which most likely will NOT work combined with the fact that there is a no cwm or twrp for your device yet (should be an easy fix if we could get the devs attention) and u will be left with a device that boots possibly with root as well but WITHOUT recovery.
http://forum.xda-developers.com/galaxy-tab-s/help/firmware-sm-t807p-t2884192/page2
^807 root brick thread (advise reading before trying...its only 2 pages long)
just wanted to add...the user tried the suggested autoroot in post #6 but that didnt work & the one mentioned here is linked in post #14
Click to expand...
Click to collapse
I tried this method and had to odin the firmware to get tab working again. Just an FYI. I will be uploading the firmware to androidfilehost soon
holt3113 said:
I have the t807 for tmobile ( non snapdragon )
used the 805 auto root.
worked just fine.
I am not trying anything else, such as twrp and roms
unit the official development is done
Click to expand...
Click to collapse
I just bought the 807T from T-Mobile too. When you restart your Tablet holding the home, volume control and power button bring you to a download screen? I don't get that option. Instead I get a image of the android laying down with a exclamation mark coming out of his stomach and the options:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Am I doing something wrong?
hijeff1 said:
I just bought the 807T from T-Mobile too. When you restart your Tablet holding the home, volume control and power button bring you to a download screen? I don't get that option. Instead I get a image of the android laying down with a exclamation mark coming out of his stomach and the options:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Am I doing something wrong?
Click to expand...
Click to collapse
Looks like you're pressing volume down instead of volume up.
Umm. Volume down, home key, and power button ??
POWER + HOME + VOL DOWN = Download mode.
POWER + HOME +VOL UP = Recovery.
Day 269 still haven't found a way to root sm-t807
With both the M7 and M8, I could swipe up on the camera (stock ROM) and the camera would launch right away without having to do the pattern unlock. With the M9 (which I just got 2 days ago), when I swipe up on the camera it does not launch the camera app, but it delays for ~3 seconds, then tells me to do pattern unlock. When I do the unlock, it goes to my home screen and still doesn't launch the camera app.
Is this behavior consistent for everyone else on the stock ROM/launcher?
Still investigating what launchers/ROMs I'd be most interested in for this new device or whether it's even worth keeping. Having quick camera access is pivotal and the motion gesture holding the phone in landscape and pushing the volume button is a complete joke (works 1/3 the time... maybe).
I have both m8 and m9 and no software differences at all in this area . try to factory rest your phone and I think the problem will be fixed .
Sent from my HTC One M9 using XDA Free mobile app
hamud.q said:
I have both m8 and m9 and no software differences at all in this area . try to factory rest your phone and I think the problem will be fixed .
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
It couldn't be the same software.
A) M9 is 64 bit OS and M8 is 32 bit
B) Sense 7 hasn't even been officially released for the M8, so if you're using a Sense 7 rom on your M8, then it is a port from an M9 rom.
So...stock it's definitely not the same software and even if you're running the "same" custom ROM on both, they're not really the same, just similar.
I am able to launch the camera from the lock screen with no issues and always have. I agree, do a wipe and reflash; something is borked on your phone.
slmclarengt said:
With both the M7 and M8, I could swipe up on the camera (stock ROM) and the camera would launch right away without having to do the pattern unlock. With the M9 (which I just got 2 days ago), when I swipe up on the camera it does not launch the camera app, but it delays for ~3 seconds, then tells me to do pattern unlock. When I do the unlock, it goes to my home screen and still doesn't launch the camera app.
Is this behavior consistent for everyone else on the stock ROM/launcher?
Still investigating what launchers/ROMs I'd be most interested in for this new device or whether it's even worth keeping. Having quick camera access is pivotal and the motion gesture holding the phone in landscape and pushing the volume button is a complete joke (works 1/3 the time... maybe).
Click to expand...
Click to collapse
Let me see if I understand...So you have camera icon in your docked icons? How are you turning on the screen? Power Button? Then you pull up the camera icon from the lock screen? Then you get a 3 second delay and then you have to enter your pattern unlock? And after you enter your pattern, you get the home screen and not the camera?
That doesn't sound normal. I'm not on a stock rom right now, but when I put the camera icon in my docked icons, turn the screen on and swipe it up, I get the camera immediately (but I'm using smartlock right now and I don't have to enter my pin when I'm in the office).
Good (?) to know I'm just uniquely seeing bad behavior. I'll try factory reset phone under backup & reset. Loving the ability to search settings fluidly now.
Thanks everyone for the info!
jollywhitefoot said:
It couldn't be the same software.
A) M9 is 64 bit OS and M8 is 32 bit
B) Sense 7 hasn't even been officially released for the M8, so if you're using a Sense 7 rom on your M8, then it is a port from an M9 rom.
So...stock it's definitely not the same software and even if you're running the "same" custom ROM on both, they're not really the same, just similar.
Click to expand...
Click to collapse
Man if u read again I said there is no differences in this area ( about launching the camera) . despite it's 64 or 32 or sense 6 or 7 . ok?
Sent from my HTC One M9 using XDA Free mobile app
slmclarengt said:
Good (?) to know I'm just uniquely seeing bad behavior. I'll try factory reset phone under backup & reset. Loving the ability to search settings fluidly now.
Thanks everyone for the info!
Click to expand...
Click to collapse
Have you tried temporarily turning off lockscreen security?
jollywhitefoot said:
Have you tried temporarily turning off lockscreen security?
Click to expand...
Click to collapse
Just tried that to no avail. Even with the setting at "Lock Screen" but no pattern/pin lock, it still delays then goes to home screen regardless of app I attempted to launch.
SW Version 2.6.651.11
5.1
Sense 7
slmclarengt said:
Just tried that to no avail. Even with the setting at "Lock Screen" but no pattern/pin lock, it still delays then goes to home screen regardless of app I attempted to launch.
SW Version 2.6.651.11
5.1
Sense 7
Click to expand...
Click to collapse
What about other apps? Like mail or messages? Do they have the same behavior? I assume they would, but I really know know why that would happen. Did you check in the Sprint forum to see if anyone else is having that issue?
After getting a new device with 5.0.2 that worked fine, I upgraded to 5.1 and saw the issue again. That's when I looked more thoroughly through the Play Store for app updates (probably skimmed through on first device). I'm pretty sure after updating "HTC Sense Home" with its proclaimed "bug fixes" the issue was gone. Camera and other swipe up apps on lock screen behave as expected now.
This is just copied and pasted from my forum post on windows central, I figured it would be seen by more people here! Oh and i cant post screenshots because im still a new member on the XDA forum but you can see screenshots on the windows central post! Just search for my username to find it.
Guys, I figured it out!! Casper does work and will let you send snaps!
So I was messing around with Snapchat (Casper) on my Nokia Lumia 920 and I almost had a heart attack when I saw a picture that I had took pop up with the editor like it was ready to send (which it did). So here is what I did:
1st I opened up Casper (duh)
2nd I took an image from the camera (IMPORTANT: make sure you've set Casper to use the installed camera app)
oh and also I found this to only work with the front camera (probably because of the lower image quality/image size??)
3rd This is the hardest part...waiting (now i know you will all probably think this is a trick but i promise its not, I've done this three times so far and its worked.)
You have to wait for about 1 min and 10 seconds, I know this sounds ridiculous but just make sure the screen doesn't time out or anything, I timed it on my watch. Then Casper will pop up with your image in the editor:
Ta-Da send as usual!
I'm really hoping that this will work for all of you! I was very excited when I got this to repeat multiple times! I first figured this out when I took a random selfie and I went to my stories, then I clicked on someones story and I pressed send as snap when that editor popped up I blacked out the screen using an emoji and I way typing something to send to my friend when the image I took earlier flashed up in front of me and startled me a little, lol!
you can tell me what version are you using? I am not able to sign in with the last two versions available in my lumia 930
It doesn't work for me. I use Casper, set the Installed Camera app as default. Already tried Blackberry mode on/off but no change. It just goes to the startscreen, but the app doesn't close. Looks like it's trying to open the camera but insted pushes me back to startscreen.
I have a Lumia 920 with win 10 mobile 10512 (Fully unlocked)
Please help...
viniciiusmuniz said:
you can tell me what version are you using? I am not able to sign in with the last two versions available in my lumia 930
Click to expand...
Click to collapse
Im Using W10 Build: 10512
Im Using Casper Version: 1.3.0.1
Is the keyboard popping up on your version?? if you dont have a keyboard that pops up in the app im afraid to say you will have to hard reset your phone by first backing up everything and then going to settings>system>about>reset your phone
*THIS WILL DELETE EVERYTHING FROM YOUR PHONE BE CAREFUL*
The new fix for this is on the forum you do not have to reset your phone.
Good luck getting it to work
GlenniBoy said:
It doesn't work for me. I use Casper, set the Installed Camera app as default. Already tried Blackberry mode on/off but no change. It just goes to the startscreen, but the app doesn't close. Looks like it's trying to open the camera but insted pushes me back to startscreen.
I have a Lumia 920 with win 10 mobile 10512 (Fully unlocked)
Please help...
Click to expand...
Click to collapse
Did you update your windows camera from the app-store, mine is fully updated, try deleting and reinstalling Casper, maybe that will work?
Doesn't work with my 930.
Edit: Actually seems to work, the image ends up just randomly popping up on your screen
devize said:
Doesn't work with my 930.
Edit: Actually seems to work, the image ends up just randomly popping up on your screen
Click to expand...
Click to collapse
Hmm I wonder if the time that it takes for the image to pop up is different per device, I would try timing it on the 930, let us know what you get!!
zombiegator said:
Hmm I wonder if the time that it takes for the image to pop up is different per device, I would try timing it on the 930, let us know what you get!!
Click to expand...
Click to collapse
I've got a 100% record with getting this working so far, without even having to do your 3rd step of waiting 1 minute. It usually takes around 30 seconds, give or take 5 after taking a picture and pressing the tick before it pops up on my screen. Only works for front facing cam it seems. Sometimes it won't work just sitting there waiting for the image to pop up so I'll have to play around with the app by viewing/downloading a picture or two from someone's story, exiting back to the main screen and then it'll pop up. I don't know if this is necessary or me just getting impatient but so far it's worked every time for me. Also works quicker when the app is freshly opened, so if you've been playing around with it by viewing snaps before you try sending one it'll probably take longer to pop up.
So if you haven't gotten it to work, try taking a picture with the FFC and after about 30 seconds, just play around with the app, view stories etc. and then press back out of their story onto the main screen, rinse and repeat until it pops up randomly within the next 30-60 seconds. It's taken up to 1:30 from pressing the tick for it to pop up sometimes but so far I've got every picture that I've taken with the FFC on mine to eventually pop up. I have blackberry mode turned on as well.
zombiegator said:
Im Using W10 Build: 10512
Im Using Casper Version: 1.3.0.1
Is the keyboard popping up on your version?? if you dont have a keyboard that pops up in the app im afraid to say you will have to hard reset your phone by first backing up everything and then going to settings>system>about>reset your phone
*THIS WILL DELETE EVERYTHING FROM YOUR PHONE BE CAREFUL*
Good luck getting it to work
Click to expand...
Click to collapse
Um, no, you do not have to reset your phone. There is a thread in this forum here that will instruct you how to restore the keyboard, and it works. The solution had been found and posted before you wrote that; why would you tell someone to wipe their phone if they don't have to?
Darrian said:
Um, no, you do not have to reset your phone. There is a thread in this forum here that will instruct you how to restore the keyboard, and it works. The solution had been found and posted before you wrote that; why would you tell someone to wipe their phone if they don't have to?
Click to expand...
Click to collapse
Because I didn't know there was another way to do it, my keyboard did the same thing and I had to reset my phone. Thanks for sharing the link though!
Sure thing. I actually reset my phone a few times over a couple days, trying to get everything working perfectly, but I was checking here several times a day for a solution. I needed Access Point to access cellular data, but it has to be installed on 8.1 and then upgraded to 10; you can't install it on a fresh 10 install. I was incredibly frustrated when my kb stopped working in my android apps every time, where it would work fine after a reset but then I could only use wifi and I would have to use the recovery tool again or deal with not having any data. Despite the bugs I think 10166 ran better and I hope they push another build soon.
Darrian said:
Sure thing. I actually reset my phone a few times over a couple days, trying to get everything working perfectly, but I was checking here several times a day for a solution. I needed Access Point to access cellular data, but it has to be installed on 8.1 and then upgraded to 10; you can't install it on a fresh 10 install. I was incredibly frustrated when my kb stopped working in my android apps every time, where it would work fine after a reset but then I could only use wifi and I would have to use the recovery tool again or deal with not having any data. Despite the bugs I think 10166 ran better and I hope they push another build soon.
Click to expand...
Click to collapse
Yeah, I agree with you, 10166 did run better in terms of compatibility IMO, I think the only thing that 10512 did for me was increase the battery life by like 1000% lol
How took an image from the camera?
MCSPECJAL said:
How took an image from the camera?
Click to expand...
Click to collapse
Read the description up top, you have to make sure Casper is set to use the default camera not the Casper camera
zombiegator said:
Im Using W10 Build: 10512
Im Using Casper Version: 1.3.0.1
Is the keyboard popping up on your version?? if you dont have a keyboard that pops up in the app im afraid to say you will have to hard reset your phone by first backing up everything and then going to settings>system>about>reset your phone
*THIS WILL DELETE EVERYTHING FROM YOUR PHONE BE CAREFUL*
Good luck getting it to work
Click to expand...
Click to collapse
theres no need to reset, there is a method to manually install the keyboard, duh!
surya467 said:
theres no need to reset, there is a method to manually install the keyboard, duh!
Click to expand...
Click to collapse
I know... Someone already mentioned that in the post right below the one you quoted and I responded to them. Like I said earlier, I didn't know that at the time, I will try changing my post to avoid future confusion.
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.