I have a problem, which appeared with first upgrade to 9.0.
It's still annoying me.
When I press home button (even iа it's fingerprint scanner) the notification is played. All the sounds setup for buttons is "off" in preferences. Reboot helps for 3-12 hours and it gets back again.
I've tried to reset the phone to factory defaults and reinstall back all my apps, but still this pain gets back 1-3 times a day.
Has anyone found a solution for this?
Related
Well I've had my Tilt for a week now and I have been frustrated completely with the Phone App.
First of all, when I am calling a tone prompted location where you have to press the keys to get somewhere (611, corporate voicemail, etc), some of the time the phone will go into "hold" when i press the keys.
Secondly, after a call that i have pressed the keys for tone operation, the phone app will not completely close. the screen will stay half dim and the start bar and task panes are locked out. i can't access any of the icons at the top of the screen. the only button available is the task manager which shows no programs running.
i can pretty much replicate the 2nd problem consistently. does anyone else have this problem? Please try to call into a company say even 611, go through all the tone prompts and see if the phone app closes appropriately afterwards. make sure you are on the phone long enough for the screen to automatically dim.
the only way for me to get past this is to softboot so i can get access to the start menu again. but i'd rather not have to softboot after every phone call =T
Thanks!
Same problem here, any help would be great.
Massiv
disable the lock thing where you have to enter a pin - i think its a bug in the rom
Same problem - but if press the on/off button for the screen twice I do have again access to all icons. Not nice but ....
yeah i was messing around with the phone last night and realized that it has to do with phone lock and figured out if you press the power button to put it to sleep and press it again to wake it up, everything is normal again. it was just a fluke how i found out but i'm glad to know that this isn't only my problem. i was about to do another hard reset on the phone.
i called ATT techsupport and they told me it might be the simcard. can other Tilt owners chime in here. is this a ROM problem or could it be related to a faulty sim?
http://forum.xda-developers.com/showpost.php?p=1566518&postcount=2
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
From quite some time i have been having this problem, when if I wake my device after about an hour of off-screen time, my buttons act funky. For example when I go into the menu and try to back, it just vibrates once and nothing happens. After that i can neither press it again nor it vibrates. Same with Home button. I have to mash them/swipe them a couple of times for it to get it fixed and this whole thing lasts like 10 minutes. It's fine afterwards. It's not ROM related since I've went to stock full locked then installed 5.0.1 GPE Fresh. I had the issue on my last ROM (SkyDragon) as well and it really pisses me of. I am about to turn on the nav bar but I will be better off if i fixed it. Any suggestions ?
I had the same problem on my old Xperia. You have to disable vibrations. Write here if it works
Based on how random it occurs I can't tell for sure but it does make it better. Though I don't feel the good response like with vibrations
I am having an issue with my rooted, unlocked phone on 5.1.1. Every once in a while when in an app and pressing the home button to go back to the desktop I will instead get a blank screen. The navigation buttons are visible and respond when pressed (a gray background shows briefly when pressed) but don't do anything. I can pull down the notification shade but nothing happens when I press a notification. I can press the setting button but again nothing happens. This happened once while I was playing music and the music continued to play. I have to turn the phone off and then back on again to get it to work again. I thought it might be a Nova launcher problem so I went back to the default Google launcher but it still happens. As a last resort I reloaded the factory image, re-rooted and cleared all ther data to start from scratch but it is still happening. Has anyone seen this before or have any ideas what is causing this? It is driving me crazy.
Thanks,
John
demoleon said:
I am having an issue with my rooted, unlocked phone on 5.1.1. Every once in a while when in an app and pressing the home button to go back to the desktop I will instead get a blank screen.
Click to expand...
Click to collapse
It happens on my N6 a few times. Mostly when I had changed something.
For instance changing a language textfile of the nav.app Sygic. Or after adding custom Poi's.
Reboot solves the problem.
My idea is that it is related to caching or memory management.
Root N6, 5.1.1 LMY48i, FK r31, encrypted.
Disabled most g-apps;
This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?
Do you have lock instantly with power key on?
funkyverb said:
This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?
Click to expand...
Click to collapse
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!
funkyverb said:
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!
Click to expand...
Click to collapse
This delay issue is so silly but it annoys the hell out of me. Where did you turn off this feature in Pie?
Update: Found it. Just use the search box in settings and type in "camera" (or whatever it is in your language). The "double tap power" setting will get listed.
Thanks alot,
Watz
I even turned off the double press for camera app but I'm still noticing a 0.5 sec lag when i press the side key
I even restarted after changing the setting
Nothing is happening
Please help
xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Thank you bro.