This setting has been working fine since i got the phone but ever since this particular phone has received the android 12 update, this setting (screen off push block) has essentially stopped working, no matter what i do, after a restart, they just revert to the initial values as shown in the picture (messages app off and all others are on). I have tried resetting the phone multiple times with no avail. I have another one of the same exact phone that was updated to the same exact XOS version, but this issue is not present there (Both phones are completely stock). Is there a way to fix this?
Related
Starting a new thread for this. I have upgraded to 2.3.3 via Kies. I have also rooted my phone.
I noticed now the system bar clock freezes and fails to work properly, as well, my time seems to be an hour off. I am using the update time automatically (using network provided values). Ironically (Likely because it uses an internet time source) beautiful widgets does not share that problem.
Very odd - is anyone else seeing the same problem?
My temporary fix is shutting off automatic and setting it explicitly myself.
Seems to have resolved itself - I essentially went to manual which meant picking the right timezone. I let that settle things down, then went back to automatic and everything was fine again.
I did see someone else posted that they did that and eventually the OS got confused again later - but right now everything is in working order - correct time, and system clock is not frozen.
The stock android clock on top right of my screen wont update! Say i turn phone on at 1:20, it wont update to 1:21 or ever change unless i reboot then it will have the correct time for that ONE minute. I haven't recently installed or changed anything like apps or anything. BUT the clock on my lockscreen(widgetlocker) updates and works fine and is accurate. I went in date and time settings and its set to automatic, in the greyed out "set time" it shows a correct updated time, however this time isn't being shown up on the top right of my phone. I tried putting it in "manual" mode instead of the automatic mode and it still wont update..Ive reboot and pulled the battery several times to no avail. Im runnning stock rom and kernel, just rooted. As i said before i havent touched any new apps or settings in several days. This is really annoying as i cant tell what time it is while on and using my phone without going to the lockscreen and it just now began happening. Anyone have a fix or also have this issue??
I'm having the same problem today with my HTC Inspire 4g. Like you I have done nothing to my apps and its getting annoying. My phone has Cyanogenmod 7 flashed onto it.
i had same issue . made a phone call to make the phone get the auto time change then rebooted for good measure
Wow, mine was related to the time change, apparently! As soon as it reached 2am where i am it started working fine again!!(Time change was at 2am here)
Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.
Hi community
I'm having a strange problem with my V30 H930. At some point a few days ago the vibration motor stopped working. Since then, if I charge the phone wirelessly, it still charges but it doesn't indicate anymore that it's charging, just as if it wouldn't charge at all. Those two issues seem not to be related at first but they always occur at the same time as described below:
First step: I tried all possible settings to reenable the vibration motor but even in the service menu (dialling *#546368#*930#) in the manual test it was dead.
Second step: I backed everything up and did a factory reset. This didn't change anything, both issues remained.
third step: I re flashed the firmware using LGUP with the "refurbish" option to really get a clean device. And both the vibration and the charging indicator both worked again! Happily I started to reinstall my apps but after a few minutes (I think about 10min or so) both problems reappeared and remained.
fourth step: I again reflashed the firmware using LGUP (which again seemed to solve the issues) and proceded to log into my google account but then didn't do anything. No configuration, no installing apps and not using the phone at all. Still after 5-10 min again the issues resurfaced.
fifth step: I again flashed the firmware and directly after the setup wizzard (logging into google account, accepting terms and conditions etc.) I disabled wifi and cellular data to prevent any updates. Still it initially worked but after 5min the vibration motor was dead and the charging indicator faulty.
I still don't know how both issues are related (but they always seem to appear and disappear at the same time). Also although I suspect it must be a software issue (because it worked a few minutes after reflashing the firmware), I'm really at a loss how to tackle the problem. Would you think a custom firmware might work? How much of a safety risk is it to run banking apps on custom firmware?
Can anyone help me? What may I do to get the vibration to work again?
Thank you very much in advance
Jamkas
Hey! It's been a while since your original post, but I started to have the same issue with V30 recently... Have you maybe found a solution? I'd appreciate your response
My phone started to randomly crash after installing the first update of Android 13. First it was once every 2 weeks, then 1 week and then it was daily. I tried to flash Android 12 and Android 11 to no avail. I formatted it, emptied caches and the error persisted. I left it and last week I tried to update it and root it. Surprisingly it stayed on for longer and I discovered:
- It doesn't crash as long as I stay with the Internet off.
- I can connect to the network via Bluetooth.
- If I turn the WiFi on whole connected to the network via Bluetooth it doesn't crash, it will once I disconnect the Bluetooth connection.
I have attached the last_kmsg file
This happened to my mother too, seems one of the recent updates has busted wifi. We tried to factory reset and now the phone boot loops.
Also, they updated the security version with this update, so cant even downgrade.
Really looks like samsung have screwed this update up.
I have manager to get a stable experience by flashing the latest lineage os GSI. It is a bit sketchy if you want to have all the functionalities (wide angle lens, fingerprint sensor etc) but it still works as a daily driver
Ill give that a go, currently trying the UK Vodafone Firmware to see if that works, otherwise I might try what youve done.
I don't tend to buy samsungs, this is my mothers phone, but for me this is a huge red flag not to. Not only did the update break the phone, but they also increased the security bit so you cannot downgrade