Panama (TPA) Exynos, I updated (OTA) to Android 12 and since then I have occasional semi-reboot. Phone kind of shuts itself and immediately shows the Samsung logo that you see when you turn it on. Phone comes back to normal after about 1 minute. It usually happes in the middle of calls.
Anyone esle experience this?
Thanks.
Related
Hi, I got the SGS2 last week from three UK as an upgrade! It was all well and good. Just yesterday I updated firmware from KIES (from KE1 to KF4). Then I used chainfire's kernel to root it and then again installed stock kF4 kernel to remove yellow triangle at boot. Then I successfully Unlocked the phone and now can use any SIM.
Just today it all started. Not a single call lasting for more than 10-20 seconds. I know I have read it elsewhere as well and then I am posting here. Just when a single signal BAR GOES DOWN, the stop hearing the other side and the call ends. I confirm that the internet has no problems till now but sometimes it is a bit slow. So What I did was to put the same SIM in my old SGS, it worked fine then started to have occasional call drops. As the phone is unlocked, I tried vodafone and O2 and they worked well, though occasional call drops. (THE SIGNAL BAR IS FULL OR ALMOST FULL) so it's an area of good network coverage.
I called three, they booked me in for returns, I have rooted phone and dont have JIG, so I wont send until I've done that. Is there any other way I can tackle this? like flashing KE1 modem on this firmware? or flashing a sim-free firmware??
Please help guys!! I hope I have made things as clear as possible.
EDIT:Now I cannot even login to google services, it states (network error) although all other things are working perfectly as wifi is connected
Just flashed:
PDA: I9100XWKF3
PHONE:I9100XXKE7
CSC: I9100XEUKD1
Call dropping is the same with the same sim, when i changed the sim, now it is occuring 50-60% rather than the 100%.
But in the battery info, time without signal is still 100% after going through the forums, I tried turning airplane mode ON and OFF and also checked setting>about phone>status, it helped drop the time without signal to 80%, the longer I open it the better it gets, but this aint no solution
Guys i bought my Galaxy S5 on 3rd May. And during that 48 hours almost my phone has been rebooted twice automatically. One time i was browsing through chrome and every thing hangs ups resulting in ramdom reboot. Second time i finnished a call and was removing ear phones when phones was rebooted. After that when i checked phone status from about phone it was showing that phone was up to about 20 hours. I want to know anyone else facing that problem or its just me. BTW i am using exynos version.
Hi guys I'm pretty new to the forums.
I've recently updated my note 4 to 6.0.1 via OTA not a rooted phone.
Now sometimes my phone battery will just drop down from like 40 percent to 0 but that's a known battery issue.
What the problem is sometimes the phone would just shut off by itself and when I turn it back on I have to wait a few minutes and it'll read phone cannot boot and all these msg's pop up. RIght now it's working so I can't really remember what it says but I would like to reflash or put a different rom on?
How do I go abouts doing this?
Thanks
I bought Galaxy A5 2016 at february this year. It worked fine until august, when I started to notice that sometimes when phone was at my pocket and I received a call, then when I took it out and answer the call, the answer and reject buttons on touch screen didn't respond and I ended up missing the call. With home button I am able to answer calls always, but I'd rather prefer to continue using the touch screen buttons. Anyone knows what's the reason for this failure and possible actions to correct it? I don't even know if it is hardware or software issue because the failure keeps showing at Marshmallow, Lollipop, after a factory reset, cache wipe and even in safe mode boot. Now the phone is at technical service but I don't think they will be able to repair it. It is a difficult to reproduce failure, doesn't happen but in very specific circumstances, but when it does, it is very annoying because calls are the core part of a phone.
I think that it could be possible for it to be a software error that has appeared in some of the updates of the phone. I always do updates when the phone notices me of that. The failure persists with Lollipop Spain PHE June version and with the first two Spain Marshmallow versions. The third one I was not able to test it because it appeared when the phone was already at service. If it is a software issue I am very worried about it, because it would took a lot of time to review the code, search for the failure, reproduce it, correct it, do testing procedures, release new software version... Perhaps Lollipop April Spain PHE version could be free of failure? It was from a time where I remember that my phone worked fine. Also, weeks before having the failure I started to use power saving mode continuously because it reduces framerate and CPU usage and sometimes when I play certain games battery goes down slowlier. Could be that related? Maybe a failure on the way phone wakes at pocket when power saving enabled? Kernel problem?
Please I would thank any information. I am very confused.
[Q] just installed latest update - now stuck on "samsung" boot screen for an hour.
i don't recall the last update taking so long to install. it was on 90% battery but have plugged in just in case.
it's a UK S7E unrooted or modified in anyway. if it doesnt reboot before i go to bed i'll leave till morning where i'll have to force it i guess.
anyone else experienced same?
in UK with Three if it makes a diff (phone from samsung store though).
Hi
I use a SE7e bought sim free from the Samsung Experience Store.
I'm Payg on o2.
Updates to sim free phones are untouched from the network.
Which update did you download ?
its only been asking to install for the last week or so (never install straight away just in case) but never got any more info than that (meaning i never wrote anything down).
i think it just listed bug fixes and nothing huge. was about 200mb maybe?
dupe
forced reboot and had a message saying to visit a samsung service centre.
great
tried again and now installed. weird.