Hello,
I have just formatted my phones memory to factory settings and then installed some programs / applications etc...
Anyway, since I did not take back up, all of my contacts are gone as well as my other data.
After formatting, there were just e-mail addresses of my friends and nothing more. I could not understand from where they came from. My first question is this.
Later on, I added some numbers manually and some numbers by copying from my sim. But, I had changed my mind and decided to carry all contacts from my previous phone to HD2. In order not to be confused I deleted all contacts. Now, When I pick a phone number from history and go to call history my phone crashes :S.
Sorry, I have told a very long story but now summing up: What should I do if my phone crashes every time when I open call history of a number (even it is saved or unknown number)
An additional question: I have installed lots of hot fixes from HTC's support page. Is it possible those hot fixes made my phone slower / confused? Moreover, I could not setup all of the hot fixes from HTC's since it says my phone is not compatible with those hot fixes :S Is it possible those installations made my phone crash when I open Call History?
Please help me, If I cannot solve the problem I'll go mad :S
Thanx in advance,
Problems are solved after a new ROM
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?
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 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.
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!