Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
FYI for WidgetLocker lovers..........the latest update has fixed the issues where the fingerprint scanner did not work on the WidgetLocker screen. The fingerprint scanner now unlocks and takes you right to your home screen. If you use the slider bar in WidgetLocker, it no longer takes you to the normal lock screen, but brings up the code unlock screen instead as the regular lock screen does. I have checked this multiple times on my phone on 4.1.83, GladiAtrix, and Cool Blue.
WidgetLocker Market Link
You do have to swipe the scanner a wee bit slower it appears, almost like Atrix was prior to 4.1.57 update, but other than that it works fine.
+1 Yea noticed that been using it again with no problems as well ^_^
Sent from my MB860 using XDA App
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
It happens to me also.
Sent from my Chuck Norris powered PRO RED DXblurred Atrix
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
blunted09 said:
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
Click to expand...
Click to collapse
When you say slowed down your phone..............in what way? I know it slows down unlocking slightly, but I notice no other slow downs once the phone is unlocked.
CaelanT said:
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
Click to expand...
Click to collapse
I updated this morning. I just checked the market again just now & no additional update was available; I'll check back again later. Re: swipe speed, I'd say I didn't change my speed at all. Again, that seemed to not be a problem for ~1/2 a day.
The only known issue right now is that Exchange can break things. I'm working on a method for rooted Exchange fingerprint scanning users to bypass this (the trick actually allows for some other things too so it's not as niche of a group as it sounds), but it requires manual XML changes right now and could mess up your system. When it's wrapped into an apk and ready for user testing I'll post somewhere in the Atrix section to let you guys know.
If you're not using Exchange (or a similar device admin that "Requires password") and having issues with it not working in cases that the Motorola lock screen would, then Settings > Report Bug and provide as much details as you can about when it's not working.
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
dLo GSR said:
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same here. Mine was working, now it's completely unresponsive. Back to the stock lock screen.
I am one of the elusive Exchange users he mentioned though...
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
dLo GSR said:
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
Click to expand...
Click to collapse
Still not working consistently enough for me to continue using...bummer... I've been back to stock lock for awhile now & waiting for next update with fingers crossed.
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
dLo GSR said:
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
Click to expand...
Click to collapse
I use FP with pin, so maybe you have hit on something there, as I have no issues with it.
yup, confirmed it's true with the dev, and also that it's Motorola's fault.
"I did notice this in testing, however Motorola does not support the Fingerprint scanner with Pattern so I decided not to either. What you found is unintentional and may have issues on it's own (I haven't tried with the latest firmware, but I had played with that setup on the original firmware and found it unreliable. Setting a delay with the Fingerprint scanner (via sqlite) also caused weirdness).
With regard to WidgetLocker, there's some code in there to handle Motorola's pattern and some other code to handle Motorola's fingerprint scanner. I did try to get both to work, but in limited testing was unable to do so and since it's not officially supported by Motorola I decided not to pursue further. (I actually also thought they fixed the loophole you found in the later firmware so the only way of doing it was sqlite, but apparently I was wrong)"
I am still new to the fingerprint reader so my old habit of swiping, which takes you to an pin pad. It says to Use fingerprint or enter pin, but about half the time it doesn't take the fingerprint. I'll either have to let it time out and get it on the main lockscreen or just enter the pin.
Actually the first day it was so bad that I didn't even think it was accepted on that pin screen. It wasnt until last night when I even saw it say "use fingerprint" but it works about half the time.
The fingerprint scanner works pretty reliably everywhere else so I don't think its a hardware issue. Just curious if others are having problems scanning on the pin screen.
Only time I have an issue is the first time Samsung Pay reads my print. 99% of the time, I have to put my finger on it again. Best way to solve your issue that I found is by unlocking your phone as follows:
Press and hold the home button with a finger that you have saved. When the phone unlocks, remove your finger. This way your finger is firmly on the reader. If it is still giving you issues, try making the fingerprint again in the settings.
I have big fat fingers lol. And I use my thumbs to unlock. In the fingerprint settings, I now have multiple fingers set to unlock the phone, that way, if I'm having maybe a problem hitting it right with one finger, I can get it with the other. I've got both hands covered. Multiple fingerprints to me is key. Also, when I was first learning to scan my prints, it took me a little while to get it right. For my thumbs, I'm pretty methodical... I start at the bottom left, lift up bottom middle, lift up, top left, lift up, etc... Basically let it scan a small quadrant of my thumb at a time. Seems to work really well. I have very few bad readings. Usually happens when my fingers have something on them, or the button has something on it, or my finger is laying too far sideways...
Sent from my SM-G935V using Tapatalk
No its not about reading my finger. I have multiple fingers setup (4).
I dont have an issue unlocking via fingerprint from the main lockscreen. The problem is when I try to swipe and it asks for a pin. Its this screen where it works half of the time. Its not that it isnt "matching" because when it works it will throw an error like "no match". But half the time it doesn't even recognize me trying to scan a finger.
I've been testing it more and more and it is a bug.
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
mwshows said:
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I just moved to the Note 5 and grabbed Marshmallow. I can say that the issue was specific to the S7E. Even on the same screen, it is responsive regardless of whether it was successful or failed, at least it prompts and responds.
On the PIN screen, it just would recognize a fingerprint input half the time.
Update
My Note 5 did it a few times today too. Aggrevating.
When you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Im having this exact issue as well. So annoying to be not able to unlock via fingerprint at the PIN screen!!!!
Having exact same issue, and it pretty much makes the
fingerprint unlock method useless. I'm using a Galaxy S7 Edge, in Australia with an Australian carrier, so it's a safe bet the issue isn't isolated to Verizon (perhaps move the thread in the main s7e thread to get more attention?)
*The fingerprint works
100% time on the main lock screen, but whenever you tap a notification or swipe
to unlock, and you are presented with the PIN/Fingerprint or
Password/Fingerprint screen, the fingerprint unlock method rarely works. You
either have to enter the pin/password, or go back to the main lock screen and
use your fingerprint there to unlock the phone.
Seeing as multiple people have reported the issue, safe to say its not an isolated issue. I'm surprised more people haven't complained
about it, as it really defeats the purpose of fingerprint unlocking.
*Is there a way to raise the issue with Samsung so they can address it in a future update? Or does anyone know of a temporary fix?
To solve the problem you can have your home and work address saved as a safe place and the phone will not lock at those locations.
For me this helps to not use the fingerprint scanner all of the time. I also never have a problem with it anyways.
Sent from my SM-G935V using XDA-Developers mobile app
Good suggestion, thanks for that : )
I'm hoping Samsung acknowledge the issue and fix the problem soon. TBH, I'm surprised more people haven't encountered and complained about the issue. I noticed it within a day of getting the phone. Perhaps people don't bother with fingerprint unlock? Either way, fingers crossed an update comes soon.
I traded out for a Note 5 and its MM update is doing the exact same thing. I switched to a pattern backup and I think its working much better.
I am going to try that new Good Lock that updates the UI. Running good and will report if its still broken or if it fixes the fingerprint reader.
Did some testing of my own. Issue is not present with goodlock. Did you find the same mate?
player911 said:
IWhen you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Click to expand...
Click to collapse
Same identical problem here. It worked only one time, after that it doesn't worked anymore.
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
invision1 said:
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
Click to expand...
Click to collapse
I will wait for more stable version, in the meantime I continue to keep this annoying bug. I just don't understand why if it is a bug, most people doesn't have this problem.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Apparently yestrday a dutch user got a new update on his phone. I have an unbranded phone, i will wait for it. I keep you guys posted.
invision1 said:
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Click to expand...
Click to collapse
Could it be an hardware issue? Has anyone installed last Samsung's update? Maybe it solve this issue too.
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
invision1 said:
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
Click to expand...
Click to collapse
I didn't tried Good Lock yet, but i wonder why some users have this issue and others have not. Anyway when i will receive the update i'll let you know
Hey guys,
As the title explains, since I did the Oreo update on my A2017G (A2017GV1.3.0B02), I got a weird issue with the camera app.
Every time I take a picture, I have to wait for 5~10 seconds for the app to save the picture on my phone. If I try to take another picture right away, switch to another app, or do anything else, the picture isn't saved at all...
It's really annoying especially when I want to rapidly take more than one picture.
The issue isn't present in any other app that use the camera.
Does any of you know how to fix that?
Thanks
Is it set to save to internal storage or SD?
RobboW said:
Is it set to save to internal storage or SD?
Click to expand...
Click to collapse
I tried both, and both are having the same issue.
Tried to also disable or change options like quality or GPS, still no changes.
my friend's axon had that problem on marshmallow, i didn't because i bought it later and my phone came with nougat. now on oreo it happened sometimes until i reseted the phone (for other reasons too) and the camera app. i don't have any problems yet.
If it takes the image and the problem comes after, it's either the image processing or saving of file.
I reset my phone and formatted my card to try and avoid issues. Camera works great.
Screwed with work mode and fingerprints, now cannot delete saved prints. Grrr, need to reset again. I tried flashing Oreo back over the top of itself which worked fine but no luck fixing the fingerprint problem so I assume the issue is in saved data.
You can flash yours back over. Download the OTA update file from the Oreo thread and use it same as an SD card update. I always keep a ROM in my SD just in case I need to fix it. Put it in a folder and just copy to SD root if you need to use it.
Thanks for your help guys, I found a fix to this issue, so I'm sharing it here in case people need.
It's very simple; just go the app manager and delete the camera app data.
Now restart it and it should work nicely ?
RobboW said:
Screwed with work mode and fingerprints, now cannot delete saved prints. Grrr, need to reset again.
Click to expand...
Click to collapse
What problem do you have with the finger print scanner?
I realized mine got a lot less sensitive and precise since I updated to Oreo, and fail to read my fingerprints really often.
Edit: nevermind, I didn't read your post correctly
What a PIA, had to reset my phone again to fix the fingerprint issue. Setting up from beginning again. This time I will only use two prints
RobboW said:
What a PIA, had to reset my phone again to fix the fingerprint issue. Setting up from beginning again. This time I will only use two prints
Click to expand...
Click to collapse
Ouch that's annoying indeed.
How many prints did you register before having your issue?
All 5 ?
This time only 2 registered. Live and learn.......?
It's running well at present ?
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
None of these problems here. All that tested and works fine. Phone is super fast after update. Oh and i didnt format the phone after update
klemen241 said:
None of these problems here. All that tested and works fine. Phone is super fast after update
Click to expand...
Click to collapse
Thanks for your reply! I hope somebody facing similar problems has overcome and provide suggestions.
But Sammobile blog has also confirmed these issues.
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
shuvadeep said:
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
Click to expand...
Click to collapse
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
***Update***
Yes this trick is working.
---------------
Also one more question I don't know if it's my phone or everyone is facing this issue. Whenever I switch on VoLTE calls (Screenshot Attached) my phone temperature increases and battery drains.
Nitin5556 said:
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Click to expand...
Click to collapse
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
gee2012 said:
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
Click to expand...
Click to collapse
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Nitin5556 said:
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
Click to expand...
Click to collapse
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
cbotadra said:
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
Click to expand...
Click to collapse
Yes the problem is there in the May update.
Samsung should do something about this.
Nitin5556 said:
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Click to expand...
Click to collapse
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
gee2012 said:
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
Click to expand...
Click to collapse
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Whiskey103 said:
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Click to expand...
Click to collapse
No, its possible that some users who do flash a rom with Odin could face some issues too but i personally don`t. I`am using the ABN bank app and i haven`t rooted for a long time now. I used to do it because of theming and getting updates/upgrades but nowadays i personaly don`t see a reason anymore to root anymore. So i can`t help you with your question.
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Virgo_Guy said:
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Click to expand...
Click to collapse
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
gee2012 said:
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
Click to expand...
Click to collapse
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Virgo_Guy said:
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Click to expand...
Click to collapse
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
gee2012 said:
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
Click to expand...
Click to collapse
Erase playstore cache and you won't even notice it for a while only to re-appear after sometime.
"Less noticiable" and "very much noticiable" in my usage in 1x & .5x respectively. In ASD5 build, this transition slips like a soap.