So, I've had the premium for almost 3 weeks now. On the second day it crashed whilst I was listening to music +browsing in chrome. Thr screen turned inky and then turned off. Since then I haven't had anything similar happen, but I have had 1 or 2 reboots. Are these signs something could be wrong with my phone? I have like a week to get a replacement. It's rev 2, other than this I have no complaints.
Try to remove cach in recovery mode, maybe that will fix your problem. If not let me know
This has been happening to me as well and actually results in boot loops. Since I have Liveboot, I can see the dmesg output. It says "Failed to start system services. Invalid abi: ABI" or something like that. I'm RomAur so maybe that has something to do with it?
It has happened to me 3 times this week. Also RomAur 1.1. It seems to happen when i am heavy multitasking, definitely related to chrome I think.
I'm completely stock... I use chrome as my main browser. The last time it happened it froze on wake whilst it was charging... The first time I was listening to music and doing something else which I can't recall. The phone has 3gb of ram so I don't really clear my recent apps as often as I did on my S4. It happens once a week on average for me. Cache wipe didn't do anything.
You could've easily gotten a faulty device. A but load of hardware issues can do that and I would advice you to do a factory reset, update to the latest F/W (flash it if not available in ur region), see if it happens again and if it does - get a replacement
Gd luck
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
TheImmutable said:
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
Click to expand...
Click to collapse
exactly like that on my z5 . when i flash the xposed uninstaller , it doesnt randomly reboot, but when i flash xposed , it does.i was thinking of flashing .200 ftf and then flashing xposed from the beggining (before i install any apps ) to see if it helps , but you said you did it??
Related
I have 2 problems.
First since a month mine and my wife's phone started to have no connection after dialing some number. We both have the same issue. Let's say I hit to call my friend Tony. SO after pressing name I see connection sceen, I see time of conversation, I see bars but no voice. The person I call to hears me. I tried with different people. Same issue on both phones.
After restart calling is normal. Airplane mode off/on doesn't help.
On June 2014 we finally decided to switch roms. So since then we have Cyanogenmod 10.2.0-hercules (4.3.1). It was alright, beside problems with camera, 30% of photos and videos have defects /artefacts.
SO I thought maybe changing rom will help.
I spent whole day on searching stock roms but all files are deleted and i can't find neither one of last 4 versions.
So I thought I will change rom to earlier version of Cyanogemod. It didn't help.
Today I spent few hours too and finally decided to change rom to 4.4.2 | HellKat (first that succesfully wanted to download).
Something went wrong.
I thought I was doing everything right and there are no tricky parts but I guess I forgot to do something or... maybe something is wrong with my phone.
So I'm using TWRP. First I hit "factory reset", then "advanced wipe" and and wiped everything beside sdcard.
Then I installed my new rom, after few seconds, it shows "failed"
So I wiped everything again and tried to restore my backed up rom.
It showed "failed"
SO I wiped everything again and installed my current rom.
It shows "failed".
I started to worry and to think that I just want my old phone back, at least it works... sometimes.
I hit reboot, wipe, and install again my current rom.
Success. (Maybe reboot after wipe is needed? or maybe it's coincidense)
Finally.
I hit reboot and installed gapps.
So I was almost happy that i could go back to where I was.
Not quite...
I started to download my apps.
On second one screen went black.
Actually it powered off.
I tried to turn it on but it was only showing Samsung logo and black screen after that.
I went to TWRP, wipe, install current rom 3 times.
It seems that restart after installing makes phone bad and I can only see black screen without even booting. Ewentually I found out that now I have 60% chance that if I hit reboot I won't be able to come back to my system.
I will have just black screen and the only way to have working phone is install new rom again and not restarting.
Or maybe it's just coincidence but I don't have time to play and spend another hour on wiping, installing rom and the gapps and apps.
I hope you guys see some stupidity or some detail in what i did wrong.
I hope that maybe one of you will actually will be able toi help me with chagning rom the right way or to fix that connection issue.
same, sort of.
I have similar issue. I cant make calls unless i reboot. And it seems when i open an amount of apps, the calls just dont work. I dont know what to do.
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
DarkMatter_74 said:
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
Click to expand...
Click to collapse
Funny fact, before you wrote we have been testing our phones and found out that it is actually snapchat who makes a problem wih calling. We uninstalled it from botrh phones and 3 days it is ok
I will install new TWRP , hopefully there is newer version.
Just a heads up, Google Hangouts Dialer has the same effect as Snapchat as well.
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
blackwing102 said:
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
Click to expand...
Click to collapse
There's an older version of Snapchat that works without booking your audio. Search the threads for it. If I come across it anytime soon, I'll return with the link.
Edit:
http://forum.xda-developers.com/showthread.php?p=57344868
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
Hi everyone. I have a sporadic problem with my vanilla note 3 from t mobile. Its a totally random occurrence but sometimes it will freeze(loose all input functionality) sometimes it will just stay black screen(no input taking) and usually (not always) it will reboot itself after this happens(sometimes a battery pull is required). Is this a memory leak issue? Thanks for any help. Sometimes it will run fine for a week or 2 and then all the sudden it will start acting up.
Was it rooted? I had a similar issue before mine was rooted, some of the system load programs that I didn't use would start up and then grab all resources. ..
Mine was doing the same thing while rooted with towelroot. Even after I unrooted it was doing the same thing. I didn't try a factory reset, but T-Mobile is sending me a replacement phone.
JimSmith94 said:
Mine was doing the same thing while rooted with towelroot. Even after I unrooted it was doing the same thing. I didn't try a factory reset, but T-Mobile is sending me a replacement phone.
Click to expand...
Click to collapse
no it was never rooted and I cant get the bloatware off if its not rooted right?
same problem
im running dompop 3.5. about to install .4. but i have not been able to add any lockscreen except swipe. when i try another it unmounts my external sd card. if i reboot my phone it will reboot until it gets ready to stop doing it. some times it loads and says something about system ui not loading and asks me if i want to wait or push ok. freezes and reboots when it wants to. goes blank. i have factory reset it, fised permissions, and re flashed updates and rom clean and dirty. still does it. someone please help. phone is only a year and some months old. also my nandroid backups wont work. they are not all partitons or they just plain fail.
craigo198 said:
Hi everyone. I have a sporadic problem with my vanilla note 3 from t mobile. Its a totally random occurrence but sometimes it will freeze(loose all input functionality) sometimes it will just stay black screen(no input taking) and usually (not always) it will reboot itself after this happens(sometimes a battery pull is required). Is this a memory leak issue? Thanks for any help. Sometimes it will run fine for a week or 2 and then all the sudden it will start acting up.
Click to expand...
Click to collapse
If it was my phone I would do cache wipe first, if still no go then full factory reset and I would then reinstall most important programs first.
Restarting phone every few days is not a bad idea on it's own and BTW when was the last time you cleaned garbage from it?
About a week ago I noticed that every time my phone dies I have to clear the cache before it turns on again. If I don't it stays stuck at the HTC One screen forever. At first I thought this was isolated to the phone dying, but now whenever I try to restart regardless of battery level I have the same issue. It's extremely annoying since it takes at least ten minutes for the all the apps to optimize (331), and if my phone dies I know it'll be a while before I can use it again. Plus, the whole process ends up using battery.
Does anyone else have this issue, or know how to resolve it? I've never had this happen before, and I have no clue what could be causing it
I'm on ARHD 45 Lollipop 5.0.1, with the latest ElementalX kernel and Xposed installed.
I don't know what would cause this but my first step would be to do a full wipe in recovery (dalvik, cache, data, and system) and then reinstall the ROM. If that didn't work I'd do a full Ruu back to stock LP FW. Then see if it does it on the stock ROM. If it still does it then I'd say you something wrong with the hardware.... But I'm really not an expert in these phones. Hopefully someone more experienced than me will come along with more insight.
Thanks for the advice, I'll try that out last resort, gonna wait and see if anyone else has a solution. A little tedious for me to go through that process right now, I'd rather save that for later.
afff53 said:
About a week ago I noticed that every time my phone dies I have to clear the cache before it turns on again. If I don't it stays stuck at the HTC One screen forever. At first I thought this was isolated to the phone dying, but now whenever I try to restart regardless of battery level I have the same issue. It's extremely annoying since it takes at least ten minutes for the all the apps to optimize (331), and if my phone dies I know it'll be a while before I can use it again. Plus, the whole process ends up using battery.
Does anyone else have this issue, or know how to resolve it? I've never had this happen before, and I have no clue what could be causing it
I'm on ARHD 45 Lollipop 5.0.1, with the latest ElementalX kernel and Xposed installed.
Click to expand...
Click to collapse
Any battery saving xposed apps? If you're running anything other than greenify try disabling them then restart. Also do the same with anything that involves monitoring wake locks.
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Renos_Z said:
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Click to expand...
Click to collapse
I already use Nova Launcher, so I dont think this will fix my problem. Now its taking more time between rebooting cycles buts its still there.
I guess my last attempt will be to flash a stock ROM and see if it works.
CaioBomani said:
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
Click to expand...
Click to collapse
reflash firmware via Odin. gert FW(firmware) from sammobile.com/firmware and use SamFirm to download, as it downloads 4x faster than from thr site directly. When flashing, use the HOME_CSC vs just the CSC file, as the csc factory resets whereas home_csc keeps your files and settings etc etc. If that doesnt fix it, you have a hardware issue(IMO, at least, and ive been rooting samsungs for a decade). If you have a hardware issue, id get it as good as i could and use the trade-in specials sammy has going