Related
Hi everyone!!
5 days ago i bough a new galaxy s 3.
This is great device everything is perfect except one thing, the touchwiz 4.
Every time than I close an application it take some time (about 5-10 seconds) than everything comes back. So I decided to do an experiment. I downloaded Go launcher, made him default launcher and until now zero seconds of delay.
Am I the only one who expects that issue??
thanks all
touchwiz is just fine and fast enough. Is it faster compared to go, apex launcher and others? Definitely no but the for the functionality touchwiz gives it is fast on sgs3.
Sent from my GT-I9300 using Tapatalk 2
that's strange, because i am very upset from the reaction of the touch wiz. I only have him 5 days.
I will give you an example.
I play "where's my water" for example and that i press the home button it exits the game but it shows me only background picture and after 5 seconds everything comes back but that i go to app tray it shows nothing for about 10 seconds and everything comes back.
IT's very very annoying.
Oh, you're talking about known issue, UI redrawing, there's already posted a solution for that.
Minoza said:
Oh, you're talking about known issue, UI redrawing, there's already posted a solution for that.
Click to expand...
Click to collapse
Can you show me that thread?
tnx
You can disable S-Voice on Home Button double click -> increases Home Button reaction dramatically.
(Double Click Home Button - S-Voice opens, then hit the menu button, options, disable)
That was the first thing that I've done
That's for the home button lag, to fix the redraw set dalvik.vm.heapsize=256m to 192m at /system/build.prop.
You need to be rooted and have a root explorer that mounts system rw though.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Some body else have that issue??
Sent from my GT-I9300 using XDA
Corsus said:
Some body else have that issue??
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
Everyone has it, but the solution posted above fixes it.
For unrooted devices, just use another launcher!
Sent from my GT-I9300 using xda premium
Corsus said:
Hi everyone!!
5 days ago i bough a new galaxy s 3.
This is great device everything is perfect except one thing, the touchwiz 4.
Every time than I close an application it take some time (about 5-10 seconds) than everything comes back. So I decided to do an experiment. I downloaded Go launcher, made him default launcher and until now zero seconds of delay.
Am I the only one who expects that issue??
thanks all
Click to expand...
Click to collapse
It's not just that.
The overall responsivness is slow compared to a up2date Galaxy Nexus.
But seriously, that was expected. It's still touchwiz.
I'm sure there will be a solution in future. ;-)
Tnx guys.
You helped me.
What kind of root you suggest me to do?
Sent from my GT-I9300 using XDA
What's bothersome to me is once the phone is in sleep mode and u click the home or power button it takes sometimes 1 sec or 2 or even 3 secs and if you immediately try to scroll unlock the animation on the water is slowed as well. I didn't expect the phone to be slower to wake up then my N900 or LG O3D. Hope next update fixes this issue. BTW i've uninstalled s-voice and disabled any power saving features.
The slow lock-screen problem is linked to an apparent feature that Samsung have made to save battery, basically it puts the other cores to sleep for battery savings.
I have searched xda and Google but haven't found an answer. Does anyone know how to disable or remove screen capture? I tried freezing screen capture.apk in TB but that didn't help. I'm really tired of my pocket taking screen shots of my lock screen whenever I get a text. :-/
Sent from my SAMSUNG-SGH-I717
Maybe your pants are too tight.
Never heard of this issue before...
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Is that your Note taking a screen shot or are you just glad to see me?
Well it definitely wasn't my Note. Lol.
redman9 said:
Is that your Note taking a screen shot or are you just glad to see me?
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
Uh, you could flash an aosp Rom...they don't have swipe screen shot feature, which is what iimagine is happening right?
On aosp it's volume down and power only, no swipe, or s-pen shot at all.
Not sure how to remove it though
Yeah that's what's happening. It didn't start doing that until I flashed the last ics leak and now it's doing it on the official release. It only does it if I'm walking around with my phone in my pocket and I get a text and only about 75% of the time then. I would use an aosp rom but I like having the spen functionality.
studacris said:
Uh, you could flash an aosp Rom...they don't have swipe screen shot feature, which is what iimagine is happening right?
On aosp it's volume down and power only, no swipe, or s-pen shot at all.
Not sure how to remove it though
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
DHorrors said:
Yeah that's what's happening. It didn't start doing that until I flashed the last ics leak and now it's doing it on the official release. It only does it if I'm walking around with my phone in my pocket and I get a text and only about 75% of the time then. I would use an aosp rom but I like having the spen functionality.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Do you want screenshots completely disabled or just the swipe screenshot disabled?
Completely disabled is much easier, as I just did a quick test and completely disabled screenshots.
What ROM are you using?
EDIT: Spoke too soon. I'm partially there...it doesn't take screenshots anymore, but it crashes SystemUI when you try to. I'll keep looking into it.
Since it happens on screen wake with texts, why not use SMS pop up from the market and disable notifications in the native messaging app. At least it won't wake in your pocket.
Honestly either way is fine with me, I don't ever take screen shots so I really wouldn't miss the feature.
I'm on the official att ics stock rom rooted and cwm.
lactardjosh said:
Do you want screenshots completely disabled or just the swipe screenshot disabled?
Completely disabled is much easier, as I just did a quick test and completely disabled screenshots.
What ROM are you using?
EDIT: Spoke too soon. I'm partially there...it doesn't take screenshots anymore, but it crashes SystemUI when you try to. I'll keep looking into it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
I would try that but I do like the screen wake when my phone's not in my pocket.
froidroid said:
Since it happens on screen wake with texts, why not use SMS pop up from the market and disable notifications in the native messaging app. At least it won't wake in your pocket.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
Proving a little more difficult than expected. I'm still working on it, but won't be able to do any more on it tonight probably.
I appreciate the effort. I tried a couple of things that I thought might work but none did.
lactardjosh said:
Proving a little more difficult than expected. I'm still working on it, but won't be able to do any more on it tonight probably.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
I've been digging around in SystemUI and can disable just the swipe screenshot, but it crashes SystemUI most of the time.
This may be a dumb question but did you freeze or remove screen capture.apk when you were trying that?
lactardjosh said:
I've been digging around in SystemUI and can disable just the swipe screenshot, but it crashes SystemUI most of the time.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717
Not a dumb question at all. Freezing the screen capture apk doesn't stop the screen shot from being taken, which is a little bizarre.
I should get some more time to work on this tomorrow. Might take someone better than me though.
Yeah I thought it was weird that freezing it didn't do anything. I was thinking maybe that apk is what is causing the crashes when fooling with the system UI.
Sent from my SAMSUNG-SGH-I717
I worked on this some more today and its still crashing when I try to prevent the screenshot from being taken. I think another way would be to stop the phone from using the palm sweep gesture. That might be easier to figure out and I think is in framework.
That would work too. :thumbup:
Sent from my SAMSUNG-SGH-I717
Now that we have root is there a fix for lock screen lag?
The current root procedure breaks more things so its not worth it even if it did
Sent from my SCH-I605 using xda app-developers app
thejron said:
The current root procedure breaks more things so its not worth it even if it did
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
No check again last night at 2am EST on IRC we finally got shipped OS with root.
jellydroid13 said:
No check again last night at 2am EST on IRC we finally got shipped OS with root.
Click to expand...
Click to collapse
yes and all works great. love xda
On my Note it appears to be a TouchWiz problem. I do not have the lock screen enabled as my phone never leaves my side. From sleep it takes approx. 1 second to wake if i press the power button when using TouchWiz. It wakes in less than half a second when i use SSLauncher or Nova!
Not using touchwiz. Nova launcher instead. Still get crazy lag. Seems its across all Note 2. Hoping for a fix.
I was browsing the n7100 forums and someone there asked the same question. A lot of people said that the lag was because of the phone coming out of deep sleep so the only way to fix the lag would be to keep some app running in the background that keeps the phone from sleeping. The only problem with that is that your battery life won't be as good.
why not just download voltage control or similar app and raise the minimum clock speed?
I have no lag at all. My note 2 is faster then my g3
Sent from my SCH-I605 using Tapatalk 2
mzimand said:
I have no lag at all.
Click to expand...
Click to collapse
It's not lag so much as it is a delay. On my Razr, there's no delay between pushing the power button and the screen coming on. There is a delay on the Note 2 of around a second between pushing the button and the screen coming on.
I don't think it's the lockscreen. I don't see a difference when I turn it off. My guess is the little bit of lag is for hardware reasons.
I've read that this is due to S-Voice waiting for input before the screen completely wakes up. Go into S-Voice and find the setting to wait for input on wake or something similar and turn that off. Lag should be fixed...dont have the phone yet and already giving advice, lol.
ElephantGlue said:
I've read that this is due to S-Voice waiting for input before the screen completely wakes up. Go into S-Voice and find the setting to wait for input on wake or something similar and turn that off. Lag should be fixed...dont have the phone yet and already giving advice, lol.
Click to expand...
Click to collapse
No such option at all.
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
http://www.youtube.com/watch?v=AT5mEUlyMk4
ElephantGlue said:
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
Click to expand...
Click to collapse
Went into s voice and there was nothing about that in there. Just wake on command and thats all.
ElephantGlue said:
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
http://www.youtube.com/watch?v=AT5mEUlyMk4
Click to expand...
Click to collapse
This video is for home button lag not lockscreen lag. Plu my s voice was all ready disable by home button. This thread is for lockscreen lag/delay not home button.
The Fix for me
Here is what i found turn off s-voice this what i found to fix the lag i think it is running waiting for the wake voice command
do turn it off if you dont use it did and it did the trick it is in the apps drawer so dont look for it in the settings
I thought this was generally accepted to be due to the phone entering a deep sleep and shutting off the CPU cores, thus the delay in waking up the processor and thus the display.
Will do further testing around forced wake locks and hold cpu states.
i disabled the lock screen...so much better! this phone does not pocket dial, so its not needed anyway imo.
Is there any way to make the fingerprint scanner with the screen off ?? I know in iphones they have a mod in cydia to do it.... Is it possible to get the same thing here ?
gdmlaz said:
Is there any way to make the fingerprint scanner with the screen off ?? I know in iphones they have a mod in cydia to do it.... Is it possible to get the same thing here ?
Click to expand...
Click to collapse
Why on earth would you want that ?
And if it's possible, I guess it will drain your battery faster...
speedme said:
Why on earth would you want that ?
And if it's possible, I guess it will drain your battery faster...
Click to expand...
Click to collapse
when you swipe it unlocks, No need to turn the screen on, Works fine on iphones my gf has hers rooted and works perfectly
gdmlaz said:
when you swipe it unlocks, No need to turn the screen on, Works fine on iphones my gf has hers rooted and works perfectly
Click to expand...
Click to collapse
As said, if it would be possible...the battery will drain a lot faster as the screen will always be active/the system will perform wakelocks all the time.
But it's a good idea
Sent from my SM-G900F using XDA Premium 4 mobile app
speedme said:
As said, if it would be possible...the battery will drain a lot faster as the screen will always be active/the system will perform wakelocks all the time.
Click to expand...
Click to collapse
That's what was generally said about double tap to wake, yet the phones that have this implemented, don't have drastically increased battery consumption because of it.
On the other hand, Samsungs half second delay after pressing home button, to wake after deep sleep (formerly just a "feature" of exynos devices, now with snapdragons as well) , is extremely annoying.
Don't see how would the screen always be active? Rather, the fingerprint sensor would be.
Sent from my SM-G900W8
Idan73 said:
That's what was generally said about double tap to wake, yet the phones that have this implemented, don't have drastically increased battery consumption because of it.
On the other hand, Samsungs half second delay after pressing home button, to wake after deep sleep (formerly just a "feature" of exynos devices, now with snapdragons as well) , is extremely annoying.
Don't see how would the screen always be active? Rather, the fingerprint sensor would be.
Sent from my SM-G900W8
Click to expand...
Click to collapse
That's what I was thinking if iphones are doing it without any problem and lg is using their knock why can't samsung
I don't believe battery drain would be an issue, but how would you keep the phone in a state to be read?
With double tap to wake and swipe to wake surely the waiting for action state is already developed.
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Up up up
Sent from my SM-G900T using Tapatalk
Prof Peach said:
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Click to expand...
Click to collapse
This is already working.. I scanned 3 times the same finger, and now working like this..
sosimple said:
This is already working.. I scanned 3 times the same finger, and now working like this..
Click to expand...
Click to collapse
if the screen is off the fingerprint won't unlock and turn the screen off at the moment...... you have to press the home key wait for screen to turn on then swipe
Prof Peach said:
With double tap to wake and swipe to wake surely the waiting for action state is already developed.
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Click to expand...
Click to collapse
gdmlaz said:
if the screen is off the fingerprint won't unlock and turn the screen off at the moment...... you have to press the home key wait for screen to turn on then swipe
Click to expand...
Click to collapse
I know. I talk about press (so the screen turns on) AND sweeping the finger at the same time.. This is working for me. I have to do a longer sweepe though.. And i have used all 3 finger setting to the same finger, probably a bit different portion of the finger every time..
Try it.. It works for me. Always unlock with one sweeping and pressing at the same time..
The disadvantage, i can unlock only with one finger.
The problem for me is that i have the home button to wake switched off using wanam exposed module. The phone was active in pocket way too many times.
sent from my Galaxy S5 running NeatRom v2.3
Ok, so loads of people have faced this problem. This guide will help you to make the home button/fps work again!
Do the fingerprint sensor test first
Dial *#808#
A menu will appear
Select Finger print test
Select Finger Print auto test
If it says pass, you already have a working sensor
Reboot the phone to make it work again
If it says fail, follow the given methods!
Method 1
Put the phone on charging
Note: Do not remove the charging cable during the whole procedure
Go to Settings>Apps>All
Find com.oneplus.fingerprints.service
Select Clear Cache
Select Force Stop
Press the Power button for 10 seconds until the phone is completely off
Switch it on normally
Check if it works or not!
Method 2
Press the power button to bring up the reboot menu
Long press on Power Off option
Reboot to Safe Mode will appear
Click ok and let it reboot
Check home button if it works or not
Reboot normally
Tip: Try doing method 1 in method 2 when in safe mode
Method 3 <<Tested working by me
Drain the battery to 0%
When the phone switches off, keep pressing the power button and starting it
Keep doing Step 2 for 20 times
This is for draining the left over battery completely
Now, charge the phone to 100% keeping it switched off
Remember: Charge to 100% Works only when it is fully charged
After it says "OK" and it is fully charged, keeping the charging cable in, press the power button to boot the phone
Remember: DO NOT TAKE OFF THE CHARGING CABLE HERE
Enable the hardware buttons from settings if you have turned them off if you have been using software buttons (Settings>Buttons)
Check if the home button and fingerprint sensor works
Method 4
Clean flash OOS Stock version 2.0
Check if the home button works now
Best of luck!
Will keep this in bookmarks, because as a regular thing, this device should break my home button too.
Thanks so much buddy.
method 3 worked for me when all else failed.
Nice post here
Method 2
Method 2 worked for me! I've tried a lot of things, including Safe Mode things. but this time Method 2 while charging worked! Thank you very much!
For me none of the methods worked.
I presed the sensor arround until somehow changed to homescreen guess it was a bad contact or ground issue but its been working flawless since yesterday
Sent from my ONE A2005 using Tapatalk
I should mention that there is a shortcut rather than having to dial the number, you can make a shortcut with any activity launcher, in fact Nova launcher for instance can do that natively.
Sent from my ONE A2003 using Tapatalk
Wow I should have came across this thread before!
I had this issue before, but I fixed this issue with a clean install to OOS 2.2.0 myself.
Overall, nice post OP!
sewer56lol said:
I should mention that there is a shortcut rather than having to dial the number, you can make a shortcut with any activity launcher, in fact Nova launcher for instance can do that natively.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
What number? Wrong group/thread lmao
Or am i missing something
Sent from my ONE A2003 using Tapatalk
regalstreak said:
What number? Wrong group/thread lmao
Or am i missing something
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Fingerprint sensor test number and really any other hidden utility.
Sent from my ONE A2003 using Tapatalk
regalstreak said:
Ok, so loads of people have faced this problem. This guide will help you to make the home button/fps work again!
Do the fingerprint sensor test first
Dial *#808#
A menu will appear
Select Finger print test
Select Finger Print auto test
If it says pass, you already have a working sensor
Reboot the phone to make it work again
If it says fail, follow the given methods!
Method 1
Put the phone on charging
Note: Do not remove the charging cable during the whole procedure
Go to Settings>Apps>All
Find com.oneplus.fingerprints.service
Select Clear Cache
Select Force Stop
Press the Power button for 10 seconds until the phone is completely off
Switch it on normally
Check if it works or not!
Method 2
Press the power button to bring up the reboot menu
Long press on Power Off option
Reboot to Safe Mode will appear
Click ok and let it reboot
Check home button if it works or not
Reboot normally
Tip: Try doing method 1 in method 2 when in safe mode
Method 3 <<Tested working by me
Drain the battery to 0%
When the phone switches off, keep pressing the power button and starting it
Keep doing Step 2 for 20 times
This is for draining the left over battery completely
Now, charge the phone to 100% keeping it switched off
Remember: Charge to 100% Works only when it is fully charged
After it says "OK" and it is fully charged, keeping the charging cable in, press the power button to boot the phone
Remember: DO NOT TAKE OFF THE CHARGING CABLE HERE
Enable the hardware buttons from settings if you have turned them off if you have been using software buttons (Settings>Buttons)
Check if the home button and fingerprint sensor works
Method 4
Clean flash OOS Stock version 2.0
Check if the home button works now
Best of luck!
Click to expand...
Click to collapse
Unfortunately, neither of the 4 methods works for me.
*edit: What I did, I reformatted all data wiped all cache. Installed the latest CM13/picogapps. BAM! it's working again!
teeluun said:
Unfortunately, neither of the 4 methods works for me.
*edit: What I did, I reformatted all data wiped all cache. Installed the latest CM13/picogapps. BAM! it's working again!
Click to expand...
Click to collapse
Lucky you. Will add this method lulz
Sent from my ONE A2003 using Tapatalk
few days ago I wrote that method 2 with charging helped, but now it stopped working again
Elxaan said:
few days ago I wrote that method 2 with charging helped, but now it stopped working again
Click to expand...
Click to collapse
Did you flash the latest ota? That might be the problem. Try method 2 again lol and reflash the old oos
Sent from my ONE A2003 using Tapatalk
regalstreak said:
Did you flash the latest ota? That might be the problem. Try method 2 again lol and reflash the old oos
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
No, I didn't anything with OS after fixing
Elxaan said:
No, I didn't anything with OS after fixing
Click to expand...
Click to collapse
Hmm try method 2/3 again
Sent from my ONE A2003 using Tapatalk
After following step 1 and step 2 my oneplus launcher isn't responding at all. now i don't have a working phone. GREAT!!!......
aleco90 said:
After following step 1 and step 2 my oneplus launcher isn't responding at all. now i don't have a working phone. GREAT!!!......
Click to expand...
Click to collapse
You really did something wrong
Sent from my ONE A2003 using Tapatalk
regalstreak said:
You really did something wrong
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Love how that's your first reaction. It's a Step By Step thing, you can't go wrong!. How about the phone is just ****ty as hell? or better? help me?
aleco90 said:
Love how that's your first reaction. It's a Step By Step thing, you can't go wrong!. How about the phone is just ****ty as hell? or better? help me?
Click to expand...
Click to collapse
Sideload some launcher with adb, otherwise dirtyflash the rom zip
Sent from my ONE A2003 using Tapatalk
What I did was two things. First I went to system/usr/keylayout and added 102 HOME VIRTUAL to the end of that file (follow the examples in the file) and then I installed xposed, downloaded gravity box MM, turned on the option in navigation keys to disable double tapping home button, and rebooted. This fixed my home button.