Ok. Problems I have encountered the 2 days I have used the phone:
Constant freeze. The first hour I used the phone it froze and rebooted 7 or 8 times.
Missing SocialLocation.apk. This caused a problem for the GPS in smart actions to work at all. Rooted phone and installed the app, and problem disappeared.
Tried to hard reset the phone because of all the rebooting problems. Guess what, on the first menu coming up where you can choose language, the phone froze and rebooted again. Now still it is constantly freezing and rebooting.
The freezing issues does not really have one specific app causing it. It can happen whenever doing whatever!
Anyone got a solution for this? Maybe a OTA update for Norwegian model?
Well, as my dad's phone is still fine as of now with not a single reboot in 2 days, I'd suggest you get in contact with your carrier and ask for a replacement. This seems to be a phone defect and you should be able to get your replacement easily. Be sure to not mention rooting and installing SocialLocation.apk though!!
You rooted and removed some files from the System, did you not?
Related
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
jasonale said:
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
Click to expand...
Click to collapse
So when your phone have become unstable , in what condition it was ? did you ever flash it before ... so my s2x did the same thing afer a update with odin on 4.2 ... so i have reflashed it and evrything was working good after
Hi there fellow S6 edge owners.
my version of Samsung S6 Edge is Hong Kong's G9250, only got this phone two days, ago, I used to have an HTC One m7 and always rooted with custom roms, but seems like Samsung has done a great job this time, I am going to stick with stock rom for now.
Strange things happened to me after I purchase from the store and with the helpful staff from the samsung store helping me setting up this beauty. Not long later after I walk out of the store the Following message from Security Log pops up: "Unauthorised actions have been detected. Restart your device to undo any unauthorised changes"
So I restart my phone, thinking it's no biggie, but the message would reoccur any time in between 30 to 2 hours, or when I am updating and installing apps as a new phone. I didn't transfer any old contents, nor having install any apk manually. The rom is stock as it can be.
So I factory reset it, and the same message would keep popping up, I scan my phone using the security app and no threats were found, but I had to restart my phone to make the notifications goes away, I start to suspect there might be something wrong with the rom itself or the kernel, so I decide to Factory reset it in under 6 hours of purchase, after booting on and signing in, the message would come up again!!
So I took it to the store, and asked them have they seen this? One of the manager said you need to cleared the app preferences and clear the credentials. I also updated the security policy myself. but still no luck. So they gave me a new one, with in 20 minutes of setting up, the message "Unauthorised actions have been detected. Restart your device to undo any unauthorised changes" Comes up again.
I am just wondering if any other is experiencing any similar issues? This is getting annoying.
same issue
Im having the same issue with Australian stock.
I too am having the same issue on Australian stock. :/
I'm having the exact same issue with Hong Kong stock. Tried everything from reinstalling to clearing the app preferences.
Has anyone found a solution to this annoyance? I don't like these notifications popping up every 5 minutes!!
If youre rooted, Use TitaniumBackup and freeze "SecurityLogAgent"
it'll get rid of those popups
Sent from my SM-G925V using XDA Premium 4 mobile app
Same problem
Norwegian Phone. Same problem. Notification every 5 min or so.
Ekjord said:
Norwegian Phone. Same problem. Notification every 5 min or so.
Click to expand...
Click to collapse
same problem here as well
So, I was faced with the same problem as you all above. I did a bit of research and speculate (I'm still not 100% on this) that this security bug is linked with the keyboard Samsung has preinstalled on the device. Try disabling it, using another keyboard, or just disconnecting it from any network it may use (mainly to update your dictionary regularly.)
What I did exactly:
-Reboot phone into recovery, wipe cache partition, factory reset.
-Start up phone, security threat came after a few minutes, before anything was installed.
-Restarted phone through security to reset kernel
-On startup, disabled keyboard and enabled swiftkey. Scanned, result: secure.
-Enabled keyboard, but disabled all features. No problems. Scanned, result: secure.
-Enabled features one by one, no problems yet. No problems. Scanned, result: secure.
-Reset keyboard settings. Scanned, result: secure. After a few minutes, security was triggered.
As I said, this may or may not be related, but this is the first time I've been seeing my phone as secured since I bought it.
I read somewhere that the problem is known.. and should be fixed in an update...if you are rooted you know what you have to do
Had the very same problem which disappeared with the update to 5.1.1. Have a couple of colleagues who suffered as well as the update cleared it up. Unfortunately from what I've read 5.1.1 kills the prospect of rooting without triggering Knox... Should have done more research before rushing to update...
Cloudyherb said:
Hi there fellow S6 edge owners.
my version of Samsung S6 Edge is Hong Kong's G9250, only got this phone two days, ago, I used to have an HTC One m7 and always rooted with custom roms, but seems like Samsung has done a great job this time, I am going to stick with stock rom for now.
Strange things happened to me after I purchase from the store and with the helpful staff from the samsung store helping me setting up this beauty. Not long later after I walk out of the store the Following message from Security Log pops up: "Unauthorised actions have been detected. Restart your device to undo any unauthorised changes"
So I restart my phone, thinking it's no biggie, but the message would reoccur any time in between 30 to 2 hours, or when I am updating and installing apps as a new phone. I didn't transfer any old contents, nor having install any apk manually. The rom is stock as it can be.
So I factory reset it, and the same message would keep popping up, I scan my phone using the security app and no threats were found, but I had to restart my phone to make the notifications goes away, I start to suspect there might be something wrong with the rom itself or the kernel, so I decide to Factory reset it in under 6 hours of purchase, after booting on and signing in, the message would come up again!!
So I took it to the store, and asked them have they seen this? One of the manager said you need to cleared the app preferences and clear the credentials. I also updated the security policy myself. but still no luck. So they gave me a new one, with in 20 minutes of setting up, the message "Unauthorised actions have been detected. Restart your device to undo any unauthorised changes" Comes up again.
I am just wondering if any other is experiencing any similar issues? This is getting annoying.
Click to expand...
Click to collapse
I am in ontario and i had the edge from a month ago and unfortunately broke it but got a new one last night in the mail and now this issue is happening to me. My first edge ive had for a month has never given me this warning before super annoying and im not reseting a bunch of ****. Was hoping thered be a disable option for the security grrr... i guess hope an update fixes this.
Hello guys,
I own my Samsung Galaxy S4 I9515 (Value Edition) for about 2 years and since a few months I've been experiencing annoying issue: phone started to get restarted by itself. Sometimes it restarted just once or twice and started to work for few days, but then it restarted over and over again in the same time, like in the 'restarting loop' so I was not able to launch it in the end. Sometimes, but not always, taking the battery away helped, but few times even this didn't help as so I had to either reset the phone to factory settings (wipe) or even install the official Samsung software from scratch (using Odin for example). After such reinstallation it was working for few hours, but as soon as I managed to install all my apps it started to restart again.
Finally I decided to return the phone to official Samsung store for guarantee repair. First time, they told me the issue doesn't happen in their service so they only reinstalled the software (what I also did myself before). The same day when I got my phone back, I restored my apps from Google Play and it started to be restarting again. Because of that, I return the phone to Samsung again. This time they told me the same, that the problem didn't happen during their tests, but they advised me to buy a new battery as with the current one phone seems not to work correctly. So I bought brand new, original Samsung battery, restored my Google account on the phone again, and... It happened again, phone has restated for 10 times during one hour
Do you have any idea why may this happen? Or how can I check what is happening? Does Android store some logs somewhere to see why it crashes and restarts?
I suspected two things:
1. Memory card - I thought memory card could make it happening, as to Samsung I gave the phone without it, but I tested it yesterday with no sd card and the same happened.
2. Apps - as I mentioned before, every time I reinstall the software I add my Google Account and apps start to be installed from Google Play, and mostly after that phone starts restarting again. But how can I check that which app is causing that? On the other hand it would be weird, as I'm using my Google Account on the other Android phone with the same apps and nothing bad happens.
Maybe you have any other idea, would be appreciated, because neither me nor Samsung official service couldn't solve this issue.
Thank you in advance!
Hi all,
I'm not sure if this is a Huawei Ascend G7 issue, or if it's an Android issue. About two weeks ago, my phone began randomly restarting by itself. It would then go into somewhat of a bootloop, in that it got to my lock screen, processed a bit, and then restarted again. When I'd hold the power button, it would restart and work well...for a few hours, and then it would restart again. I started removing my most recently-installed apps and it kept happening.
Eventually, I got fed up, and restored from scratch and once I connected my Google account, all my apps loaded back up, and the same issue persisted.
I previously had the phone rooted with Kingoroot, and this issue occurred before I removed it, as I figured that may be related. When I restored, I got rid of it and it's nowhere to be seen on my phone, and I don't have root access anymore.
Questions -
a) Does anybody know what the hell could cause this behaviour?
b) I'm not a newbie with Android, but I'm not much of a techie either. I've been trying to see the logs for my phone, but I've installed a few log-viewing apps and they all seem to need root. How can I view the log files to figure out what the culprit is?
Any help you can give me would be really welcome. It's not quite a crisis right now, but it's pretty frustrating when my phone randomly reboots and there doesn't seem to be any consistency in what I'm doing to cause it...
Thank you!!
Steve