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
Related
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,
This morning I randomly decided to update my firmware (as per Sony's incessant reminders). I updated to 17.1.1.A.0.402, as it was what Sony's updating app was telling me the latest firmware was. I updated as instructed on my tablet, wirelessly. The update was successful and totally uneventful -- no incidents whatsoever.
However, immediately after my update, my wifi dropped, and after that, I couldn't reconnect to *any* wifi network whatsoever. I toggled on/off, and the wifi would reconnect for a matter of seconds, maximum 2-3 minutes before dropping and never reconnecting again. To reconnect to wifi, I'd have to toggle off/on again and then would have seconds to try and load a page (but would never succeed)
So, I updated the firmware again, this time using the update application for the Mac since my tablet could no longer connect to wifi.
I successfully updated to 17.1.2.A.0.314.
Still the same wifi dropping and not coming back issues.
Then I tried "repairing" my software from the Mac, which I'm lead to believe erases everything and flashes with the most recent firmware.
Still had the same wifi issues.
Then I tried an erase/factory reset directly from the tablet.
I still have the same wifi issues, but they don't kick in within seconds anymore. Now after several minutes, the wifi will drop and not come back.
Any suggestions for a fix? I'm as of yet unrooted, and would like to remain that way if possible...
Thanks!
I would suggest a factory reset after flashing the update. Might solve your problem.
Before that you could try to delete your Wi-Fi and set it up again...
Vaetheran2107 said:
I would suggest a factory reset after flashing the update. Might solve your problem.
Before that you could try to delete your Wi-Fi and set it up again...
Click to expand...
Click to collapse
Thanks for your help
"Repairing" from this Mac app is flashing the update, correct? It erased and then flashed anyway. Had to set up the tablet like it was new. Is that not a factory reset?
In any case, I did a factory reset immediately afterwards, from the settings screen of the tablet, as mentioned above.
By "delete your wifi" do you mean "forget" the networks I'm trying to connect to? If so, I've done that many times, and have had to re set up my wifi networks anyway upon each factory reset/flash/erase.
So I think I tried what you suggested, and no dice, unless I've misunderstood?
Perhaps worth noting: I'm using the accompanying Sony Bluetooth keyboard.
Wifi seems to stick around a bit longer when Bluetooth is toggled off (no keyboard), though I could use the Sony keyboard before the update, no problem at all.
Yes that was what I ment.
Sorry it didn't help solving your problem.
Seems like you should call Sony.
It's the Bluetooth. Wifi and Bluetooth are on the same chip and won't work at the same time. It's a hardware fault with pretty much every Android system I've used. Turn off the Bluetooth and your wifi will be fine.
Thanks for your reply – though it was possible to use the bluetooth keyboard at the same time as wifi before the update.
Bluetooth keyboards would be pretty pointless if you couldn't use wifi at the same time as you use the keyboard, wouldn't they?
Between the Sony Xperia Z2 tablet, a Samsung Galaxy Tab S, and an iPad, I've used all with bluetooth keyboards + wifi without issues (until this firmware update on the Z2).
Use 5GHz Wifi, then the problem will be solved.
Sounds like you have been lucky so far and due to the small amount of data a bluetooth keyboard transmits. Bluetooth headphones are always transmitting as is wifi when watching hd youtube videos. They will always interfere with each other, but only every minute or so. Google the problem and you'll see its pretty universal.
heathr said:
Hi,
This morning I randomly decided to update my firmware (as per Sony's incessant reminders). I updated to 17.1.1.A.0.402, as it was what Sony's updating app was telling me the latest firmware was. I updated as instructed on my tablet, wirelessly. The update was successful and totally uneventful -- no incidents whatsoever.
However, immediately after my update, my wifi dropped, and after that, I couldn't reconnect to *any* wifi network whatsoever. I toggled on/off, and the wifi would reconnect for a matter of seconds, maximum 2-3 minutes before dropping and never reconnecting again. To reconnect to wifi, I'd have to toggle off/on again and then would have seconds to try and load a page (but would never succeed)
So, I updated the firmware again, this time using the update application for the Mac since my tablet could no longer connect to wifi.
I successfully updated to 17.1.2.A.0.314.
Still the same wifi dropping and not coming back issues.
Then I tried "repairing" my software from the Mac, which I'm lead to believe erases everything and flashes with the most recent firmware.
Still had the same wifi issues.
Then I tried an erase/factory reset directly from the tablet.
I still have the same wifi issues, but they don't kick in within seconds anymore. Now after several minutes, the wifi will drop and not come back.
Any suggestions for a fix? I'm as of yet unrooted, and would like to remain that way if possible...
Thanks!
Click to expand...
Click to collapse
I also have the problem but my tablet has 3 days of new it was working perfect the I update to 17.1.2.A.0.314 and the it kick me of the WiFi in the configuration it stays on obtaining IP address and never get it I have to restart the tablet and then the WiFi connect like nothing I turned off today I turn it on and the problem again appear >.< this time I restarted the modem and it worked.
So I don't have idea what happens first time restart the tablet work now restart the modem worked.
I will try changing to 5ghz to see if the problem it's solved or go to warranty it only has 3 days!!!
WiFi and bluetooth
Wing00w0 said:
I also have the problem but my tablet has 3 days of new it was working perfect the I update to 17.1.2.A.0.314 and the it kick me of the WiFi in the configuration it stays on obtaining IP address and never get it I have to restart the tablet and then the WiFi connect like nothing I turned off today I turn it on and the problem again appear >.< this time I restarted the modem and it worked.
So I don't have idea what happens first time restart the tablet work now restart the modem worked.
I will try changing to 5ghz to see if the problem it's solved or go to warranty it only has 3 days!!!
Click to expand...
Click to collapse
Hi, here's my experience with my Z2 tablet, unrooted. I too have had wifi problems: after using the tablet fine for a while, with a strong signal, the tablet drops out, then wifi access stalls whilst "Obtaining IP address". I sometimes use a Bluetooth Microsoft keyboard, but have had the wifi drop out when I have Bluetooth off.
The only reliable (so far) solution I have found is to move to a static IP address. Not ideal, and perhaps not much help when travelling, but an OK workaround for a home or other wifi network where you have admin access to the router.
Hope that helps. Apologies if my newbie post is naive.
Hi all
I tried going to a Lollipop ROM on my S2 but I only managed to change the recovery, the ROM didn't work (boot loop) so I used ODIN to revert back to the stock ROM (i9100XWLSW) wiped both the data and dalvik cache. I did also have Kingroot installed during all this and I installed it again after flashing the stock ROM but I've since removed that too with another write of the stock ROM via ODIN.
The problem I'm having now is Whatsapp and other apps won't actually do anything if the device is asleep. The WiFi appears to be connected, logo is present at the top if i wake the device but it takes about 10 - 30 seconds of being inside an app (such as Whatsapp) for anything to happen. I'm not sure if this is a WiFi issue or some sort of app issue across the board? I woke up today at 9am checked my phone there was nothing on it. It was only at 10:30am when I went to send a Whatsapp message to someone and opened the app manually that i had messages come in from 8am that morning. I also use Whatsapp Web and some times it won't connect to the phone via WiFi even if the device is awake. I have to reboot and try again. Although if it's connected via Whatsapp Web and asleep messages come in no problem at all both on the PC and the phone??!!!!
It's doing it constantly now, at the start it was touch and go but now it's all the time i have to constantly check the app for messages to come in. This happens on other apps too.
What's going on? Have i damaged my device some how from the flashing process? I'm pretty familiar with ODIN as I used to flash my old Galaxy Apollo all the time but never had this problem.
I was going to get a new phone but I actually really like my S2 and it actually keeps up with most of the phones in my price range and in some cases (camera, AMOLED screen, storage, sometimes RAM) it is better than the new stuff!
Any idea's please?
Never mind went and got myself a nice Note 3 instead...
Thanks guys.
I got my Xiaomi Redmi 3 in the middle of october 2016. Since then i've been using it every day. It had minor problems, like music app sometimes turns off by itself, data connection didn't want to turn on only with phone restart, but nothing major, that couldn't be temporarily fixed. But a few days ago i just wanted to browse instagram, i opened the app, and it just turned off instantly. So i tried reinstalling it. Nothing changed. I then tried to install an older version of the app. Still no change. So i decided to leave it be. I was talking to my father, that it should be reflashed because there is something wrong with it. He just pressed regular restart on it, but after that the phone died. I mean it died. It does not respond to charging, connecting to usb, pressing any existing combination of the three buttons. The screen and the status LED does not light up even for a bit. I tried to reflash it anyway with methods specifically for this situation, but it doesn't work either. In the flash tool installation of the rom just does not start. I think it's because my pc does not accept the driver, even from the official website, it just says in the device manager, that it's Android and it has that little yellow triangle. So it is visible for my PC through USB but no driver is accepted. What should i do?
Replace to new phone or carry your phone to customer service, but hey it's xiaomi
This wont help with your phone, but just wanted to leave a note for others. I was having the same issue with the Instagram app. I reinstalled the app, wiped caches, upgraded my ROM, downgraded the app, every tried a entriely differnet ROM. Nothign worked. Instagram would just crash a few seconds after opening. Really weird.
Heres how i fixed it: go to Airplane mode, open the app, logout, turn off airplane mode, log back in.
rarely fc it's okay. but when got often it's a major issue. might be emmc needs to be fixed
Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Been using AA since day one without problems here.. And if someone suggested you try developer mode, why don't you just try it while you wait for 8.1?
Ok, thanks!
I have a PIoneer AVH4100-NEX and when I had my Nexus it was very flaky at best. I would have connection issues off and on frequent, but with my 9+ it has been flawless. Glad they worked it out.
jgirado said:
Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Click to expand...
Click to collapse
If all fails, do the factory reset.
After S9+ got the update upon booting for the first time, the battery life was horrible. After the factory reset, however, happily ever after... (even though it was the pain in the a$$ to setup the phone again.
Thanks for all the tips. Although I delete my S7 profile in my car the solution was to perform a factory reset of my car's multimedia system/navigation. Now is working like a charm.
Javier