Hi,
have you ever experienced M1 crash/restart after disabling airplane mode on stock Android 9 (update 057 or 058)?
Breaking the rule "never change what's working fine", yesterday I installed the 057 and 058 OTA stock updates.
I have AccuBattery and Screen Lock, too.
After leaving the phone in airplane mode all night (as I usually do), the phone seems to have crashed and restarted shortly after I disabled the plane mode. The phone was locked, I tried to unlock with fingerprint, but the phone was unresponsive. After a couple of seconds, it showed the Asus splash screen and restarted. Very disturbing.
I might think of something involving the Screen Lock app. Android Pie does not seem to require the biometric unlock fix option, so I had not enabled it. Now I enabled it again to check if the problem repeats.
Thank you and best regards,
/_uke
I am sure that occurred at least another time!
After staying in airplane mode for several hours, the phone seems unable to connect to any cell (signal indicators remain empty), then it restarts by itself and I find it asking to enter the post-boot PIN.
Thank you and best regards,
/_uke
Related
Hi all,
I have discovered an annoying bug on my HD2 when I got off a plane the other day and pushed the 'Airplane Mode - Resume wireless connections' - all that happened was that my Wifi turned itself on (it was off before the flight) and the phone itself stayed in off-line mode.
I rebooted the phone several times to no avail, every time all that happened was that the WiFi would activate every time I tried to deactivate the Airplane mode. When I deactivated the WiFi it went back into Airplane mode!
The only solution I found was to go to All settings - Personal - Phone then use the WM confirmation pop up screen to activate the phone. It seems the sense UI has a nasty bug there.
Hope this helps someone
I have a similar problem on my hd2:
Over night i let go my device into airplane mode (night-profile) with phone weaver 2.0 -- phone off, all connections off
The next morning i let go my phone into the day-profile and automatic enter my pin. But sometimes my phone connection can´t be activated - not with phone weaver and even not with the commanger in sense.
I have ti softreset my device - then it´s working again.
Is this a driver related problem? I had this issue with radio-rom 2.04, 2.05 and 2.07. Also with stock-rom 1.48 and custom-rom 1.66.
I have a stock unrooted Verizon Galaxy S5. For several months my phone has been plagued by several issues at startup. Whether I reboot the phone or start it up after the battery has died, it always enters an odd state immediately after loading and seems to get stuck in this state for an undetermined and variable amount of time (anywhere from a few seconds or minutes to hours or even overnight).
While in this state, this is what happens:
1. Screen stays on. Once I unlock the phone, the screen stays on. The side button doesn't do anything to lock the phone or turn off the screen. Holding down the button, however, still triggers the power menu. The screen timeout never triggers, even though it should turn off the screen after 2 minutes of inactivity.
2. WiFi and Bluetooth turned off. Even if they were turned on before I powered down the phone, they are not enabled when the phone first boots up. I can manually turn them on but the WiFi will not connect to a network, even if one is available. It may show it is connecting to the network, but it gets stuck at "Checking the quality of your internet connection" and continues to use the 4G network for data connectivity. This happens no matter what WiFi network I am within range of, so it's not an issue with the network or router itself. If I am not near a network at all I will still experience the other problems of not being able to lock the phone, etc.
3. Startup applications don't load. I have Tasker on my phone, but it doesn't load and show it's notification bar icon.
Otherwise, I can use the phone normally and open applications, surf the web, etc. It seems that loading some applications and using the phone eventually causes the phone to exit this mode, but I haven't been able to find a single particular application or series of steps to fix the problem. If I power on the phone and don't use it that just seems to make it take even longer to fix itself.
Once it gets out of it's weird state, the WiFi connection will become active (it will turn on WiFi if I haven't done so manually already) and it will connect to a known network if one is available, the phone will lock itself or I can do so from the side button, and things like Tasker and Power Save mode will turn on.
I am stumped as to what could be causing this problem or how to fix it. It seems the phone may be doing some kind of check, maybe related to Knox, that hangs during startup and prevents certain things from working until it straightens itself out.
Any clues into what this problem is, what is causing it or how I could further analyze this problem and determine its cause would be greatly appreciated.
Never heard of or experienced these issues. May want to contact Samsung.
Have you installed any official updates from Verizon at any point? I've heard of phones having phantom problems like this after receiving a bad update. I would definitely contact Verizon if you did update at any point. If not then like BigBot96 said, contact Samsung about the problem.
My wife's Note 2 did something similar when the battery died. I had to factory reset. Her phone was rooted/unlocked & running a custom TW ROM, though. May I suggest doing a complete factory reset and Odin. Backup data to computer or external sdcard since this will clear the entire device.
Edit: After rereading OP's post it actually sounds like an app is hanging at startup which could cause this behavior. A logcat should tell you what's going on.
Sent from my SM-G900V using Tapatalk
I have been happily using my phone on stock 4.4.2 EUR for last 8 months. This morning I woke up to find my phone constantly rebooting as soon as I enter the SIM pin and it lock on to a cellular signal. After a lot of trial and error, I have found that if I immediately switch to airplane mode before entering SIM pin and then switch off auto-sync the phone, and then turn my mobile signal and data back on (by turning off airplane mode) the phone is fine.
As soon as I turn on auto-sync it goes into loop mode again. For the time being I am keeping sync off, but has anyone else experienced this suddenly?
Makes me think it is connected with some automatic update that Google sent to my phone overnight for their Play services or such.
yes, I have the same problem. Please see my post about it.
Now I wonder how to fix it
Thanks
Sorry for late reply but found out that if you clear the data for
Google Services Framework and
Google App
this resolves the issue. These are located under Settings / General / Apps / All
Hi there, so I updated my ph-1 to the latest Oreo 8.1 earlier this morning and have been experiencing significant delays when unlocking my screen. Sometimes the phone did not respond at all and the screen just stayed black. I had to restart the phone in such cases. Help! I seem to be the only essential phone user in entire Sydney
If you're using immersive mode, that might be the issue. Try disabling that, and see if the issue persists.
I'm experiencing the same. Setting immersive mode to None does help a bit, but it's still not as snappy as before.
And after all the same settings worked perfectly on the 8.1 beta.
Tried to go back, but on official 8.1 the recovery mode only says "no command"....
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
And specialty if you use immersive mode with sytem UI make it very long delay
winstonxyz said:
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
Click to expand...
Click to collapse
Same issue here. Sometimes takes so long to unlock that I am unable to answer a phone call that comes in before it goes to Voicemail. Usually happens when the phone has been idle for a while.
Update:
Did the dreaded FDR (factory data reset). Installed the "Tiles" app from plasystore and ran the noted adb command to allow immersive mode, tile display, and enable write secure settings permissions. I chose the action to hide the navigation bar within the Tiles app. I ignored the setting to stop on sleep so the app keeps running when the phone screen goes off. In testing it for about an hour the phone seems to unlock without any issue for now and without any delay. I also made phone calls while the phone screen was off and I was able to answer the call easily. So far so good using the Tiles app!
sounds like the expanded desktop Oreo issue. There's a Xposed module DeepScreen Oreo for it.
Hi, I'm running a rooted stock Oreo (version 8.0.0) and I've just discovered that when I turn flight mode on, if I then turn wifi on, I get the pop-up message "In flight mode" and the wifi icon in Quick Settings stays a light blue shade but Wifi doesn't actually turn on.
I may be mistaken but I thought this was working last year and I haven't done any updates to the phone.
Anyone have any ideas how to fix this?
Kind regards,
Mack.
Hi, I'm pretty sure you can use this:
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
One of the settings allows you to tune Airplane Mode.
Just to update - I think there must have been some kind of data corruption... I did a factory reset and it all worked correctly again.