Related
Hi guys. I'm totally new to the android/smart phone world btw. Anyways, I recently got my Samsung Galaxy S2... first thing I noticed, my touch screen wasn't working. I popped the battery in and out and then it started working as it should.
My phone was working fine this morning, then all of a sudden out of no where, the touch screen stopped working again. I've tried turning on/off the phone multiple times. I've taken out the battery and even my SIM card nothing... i'm worried.
Has this happened to anyone else? Is there a fix? Do i have to go through Samsung? I hope not. Incase anyone asks, I did not root my phone.
Any help/feedback would be appreciated.
When the touchscreen stops working... were you charging the phone at that time?
The first time i turned on my phone, was actually by accident and it was charging.
However, just earlier now, it was not. it was just sitting on my computer desk. The home button, lock button and touch capacitive buttons work.... but i can't get past the lock screen
you could try a factory reset to see if its software related, but it sounds like hardware. I would definitely Return the phone .
I guess I can't do a factory reset, since I can't get into any of the menus... man this sucks. I spent $900 *gulp*
To do a factory reset,
1. Turn the POWER OFF, pull the battery out and put it back again.
2. Simultaneously press and hold the Volume Up, Home and Power button
3. If the Samsung Symbol appears, release the Power button
4. A Boot Menu will then show, Use the volume up/down to choose wipe data/factory reset.
touch screen not needed this way.
oo that's interesting... I tried it. and it didn't get to a boot menu. maybe I was doing it wrong. I tried a few different ways, but no success. It turns out I have warranty with the store. They're going to replace it for me Thanks for the feedback guys. Awesome forums.
Something similar happened to me yesterday. When I had the in-box USB cable attached to a BoxWave VersaCharger (combined AC/DC charger), and the VersaCharger was plugged into 120V AC, the touchscreen would stop working. As soon as I unplugged the USB cable from the SGS2, or plugged the VersaCharger into a 12V DC lighter socket, the touchscreen would work fine.
I've got the same problem as the OP... I had my phone charging overnight and this morning when I first went to use the phone I could not unlock the screen. I could wake the screen via the home button, and see I had a missed call etc but it just wasn't responding to touch. BTW I can't remember if when I first tried to unlock the phone if it was charging or not but really this shouldn't matter.... oh and btw, I'm not rooted or anything either! Naturally I rebooted the phone but still the same problem....so I tried a battery pull and still the same problem. Just now I did a factory reset but the touch screen still isn't working! I guess this is a hardware problem so I'm going to get it fixed under warranty by Samsung! Gutted that I will likely be without my phone for a week or 2!
EDIT, UPDATE...
Well, I was just on my way to the repair shop Samsung warranty had told me to take it too, and I took my sim card out to put in my old Hero (the only thing I hadn't tried!) and I couldn't believe it but the touch screen started working fine again! Weird, but that is now my advice if anyone else has a problem with their touch screen not working - oh and I took the sim out whilst the phone was still turned on. Crisis averted!
UPDATE 2
Sadly this has happened about 4 times to me now and I'm just waiting for the inevitable next time. Each time doing a factory reset then taking the sim card out seems to bring the screen back to life (though last time not immediately) but I shouldn't have to put up with this. Problem is, I don't want to send off a seemingly perfectly working phone to get repaired as I fear they will struggle to notice the problem, never mind fix it! I'm hoping a new firmware comes out soon, in the hope that it may resolve my issues...
Me as well ...
I have had this happen to me twice now (Touchscreen not responding).
The first time I had just installed a game and thought it must have been related to that. Pulled the battery and no joy, left it for a while and it came back to life...
Second time I was surfing the web and it stopped responding, pulled the battery and left it for maybe a minute but no joy .... pulled the battery again and left it for probably 20min and it came back to life. When it came back up I noticed the livewallpaper had been turned off and my widgets were gone from the homescreen.
What I did notice when it wasn't working was it had "safe mode" displayed at the bottom left of the screen
Have the Same Problem
Have the same problem i Mine and was super exicedat first it worked fine and after charging the touchscreen stopped working i pulled the battery out and put it back in but no luckso im gonna return mine to the shop hope they replace it
Moral:AT FIRST SUPER EXICTED BUT NOW SUPER ANGRY
Same issue - Is there ANY way to save my data before I send it in for repair/replace?
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
blaubeer said:
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
Click to expand...
Click to collapse
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Nitrile said:
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Click to expand...
Click to collapse
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
blaubeer said:
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
Click to expand...
Click to collapse
get a USB jig off ebay or amazon to reset the flash counter. should not cost more than 5 or 6 euros, shipped.
anyways you need to flash CF-root through ODIN if you are coming from stock. instructions are all in chainfire's cf-root thread.
Nandroid Restore
So I successfully rooted, used CWM to do a Nandroid backup, mounted the sd_card and saved the contents (including the nandroid backup) to my PC, reflashed the stock rom & kernel, usb-jigged it to get the counter back to zero/original and sent the phone in for repair. My efforts paid off as they repaired it without question under warranty. I just received the phone back and today set about restoring my backup:
Copied the sd_card contents I'd saved to my HDD back onto the phone
Re-roooted it with Cf-mod.
Used CWM to restore the backup I took before sending it in
It restored boot/system/data/cache successfully
selected reboot now in CWM
The result is that it is still missing all my apps. It only seems to have the "data" like my camera shots and SMS messages, system settings like whether bluetooth is on or off, the volume level, Wifi networks etc. So something was restored. But there is no Google Account configured, the lock screen picture is the default not the one I had beforehand, and as I said, all the apps - the main reason I did this whole thing as my personal data is all backed up to the cloud on a regular basis anyway - have not been restored. Am I confused? I thought a nandroid backup took a complete snapshot of everything, apps included.
Finding out the list of Apps I had in order to reinstall them is not an issue - I have a list of everything I had installed saved on AppBrain. But if I reinstall the apps, all the settings (or progress in the games) within those freshly installed apps will be back to square one, not where I left them, right? Or should I reinstall the apps and then restore the data partition over the top again?
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
achillies400 said:
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
Click to expand...
Click to collapse
Nope, no screen protector or any kind of case for that matter. Anyway, that isn't my issue anymore. The touch-sensitive unit was defective, the phone was repaired under warranty. My issue now is getting my apps & settings back. I have meanwhile read elsewhere that Nandroid doesn't back up the apps - pretty deceptive "backs up everything!" "it is like time travel" etc comments around here then.
Anyway, I reinstalled all the apps I had previously, and thought by reapplying the data partition from the nandroid backup it might then bring back the settings for the reinstalled apps. Instead all it did was remove all those apps again - now I am really confused. How come the restore DOESN'T bring back the apps I used to have, but DOES remove the ones I subsequently install. Does Nandroid touch the apps or doesn't it?
Touch screen not working
So i am having a very peculiar problem related to the GT-I9100 Touch Screen.
I bought the phone from Saudi Arabia and I live in Bangladesh at the moment. So for now I don't have warranty.
I bought it on 4th of this month. It had 2.3.3. So I updated it to 2.3.5. I did not use the phone much before that so I don't know if this problem was there before.
So here is the problem.
First time I noticed it when i pulled the phone from my pocket and could not unlock the pattern. First I thought I forgot the pattern. After sometime I noticed that i could not touch the buttons. I was dragging my finger over the points but there was no connecting line. I restarted the set. But it still did not work. After sometime I took the battery out. And after that it started normally and unlocked. And the touchscreen is totally fine.
I tested it using *#0*#. And every single point in the screen registers touch.
After that this happened couple of times. First couple of days I thought it was a pattern unlock problem. But i tried PIN and Password even using no unlock. It happened in every case.
So after couple of days it totally stopped happening.
But from yesterday it is happening again. And today it happened 3 times.
So today as I had no unlock protocol i tried tapping Home twice. As this brings on the voice command menu. And for the first time i was in the phone without touching the screen.And first i noticed the Menu and Back Soft keys works.And the touchscreen still does not work. And i noticed some thing weird. Always some thing in the screen is Selected. In Menu the + Icon is selected. In first screen the Map icon is selected. Also in Recent Apps the first App is selected. So after a lot of reboots it is back to normal again. Now i see something interesting. In the Battery Usage Graph i can see some really sharp drops. 3 times. Looks like when this happens phones charge takes a nose dive.
So here is the Gist.
Info related the Problem:
1. Usually happens when the phone is my pant pocket for sometime. It does not happen if it is sitting on the table.
2. Touchscreen gets totally disabled.
3. I have no idea why this happens.The exact reason behind it.
4. Battery Charge takes a nose dive when this happens. See the attached images.
5. I still don't know how to bring it back. Sometimes a simple reboot works. Sometimes I have to pull the battery. And sometimes it works on its own.
6. Every other function of the phone works. Like music playback using my UE 200vi music keys using PowerAMP, Siri(Android version), Call can be received using headset.
Battery nose Dive:
dl.dropbox.com/u/30943431/SC20111115-203017.png
dl.dropbox.com/u/30943431/SC20111116-202913.png
Also the selection
dl.dropbox.com/u/30943431/SC20111116-202146.png
So this is the thing. My biggest problem right now is, I don't know why it happens and I don't know how to bring it back from this situation. If I knew I could make sure I don't get it again or I would just fix it every-time. As when this happens I cant make calls or anything which requires the touchscreen.
So guys help me if you can by giving ideas. As i will not go back to KSA in 6 months. So buying a $550 phone unlocked was a total waste. As i cant use it here.
Thanks a million in advance.
---------- Post added at 09:29 PM ---------- Previous post was at 09:13 PM ----------
Sorry for this. But looks like i cant post outside links before i have 8 posts. So i removed the "ht tp : //" part of the links. Copy paste in browser address bar and it will open fine.
And also the next time it happens i will do a video to shou you guys.
Having the same problem while charging touch screen doesn't work
Stock charger and usb cable
i was on CM7 but that happend so i flashed stock but no luck
I will write more observations
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Hi everyone,
I've been lurking for the past year or so, but now I got a problem of my own and I hope I can solve it with your help.
For a while now, almost every time, I picked up the phone, tried to check mail, or do something, and it wouldn't do anything. It seemed like it was turned off, except I couldn't turn it on by pressing the power key. It wouldn't react to touching the screen, menu button, plugging in headphones, the USB cable, pressing hardware buttons, sending myself a mail/sms, or calling myself, the alarm didn't go off (especially troublesome), it was, for all intents and purposes, completely frozen, until I removed and reinserted the battery. Then, I could normally turn it on and it seemed like everything was in order and a new message or email (in the account that triggers a notification) was waiting for me.
This started after I upgraded to ICS (official). I also rooted the phone with CF-Root. Everything was working fine, except for these freezes.
Last week, I had enough and I did a factory reset. After that, it seemed to be ok, until 2 days ago, when I flashed it with ICS 4.0.4 and rooted it again. It was fine for 2 days, today it started freezing again. I did not install any new apps - all the apps were (re)installed immediately after the flashing.
I *did* have some problems with the camera (I couldn't see what I was shooting, I found out that it's probably a wrong version of CF-root, so I reflashed that, problem persisted, I reflashed just the kernel of official 4.0.4 and the problem disappeared. This is all I did before I noticed the problem again.
I would think that it might be because of the SD card, some app or something else, but to the best of my observing, it ONLY happens, when a notification should be triggered - instead, the phone freezes.
Any ideas?
Thanks,
Ben
i think your RAM is on its maximum level, try cleaning your RAM once in a while.. go to your Task Manager (if you're on a stock firmware)
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
Hey there Guys,
so, I am desperate enough with this issue, that I'd actually pay the one who fixes it for me.
If you need specific infos, let me know what and where to find. Cuz I'm hella stupid with this stuff.
Bought a Samsung S9+ on Amazon. (should work just fine)
Model Number: SM-G965F/DS
Here we go, (try to remember as much as possible, as its 1 year ago)
since I can't live without root, I did do so by the magisk method. I think it didn't work so well, cuz there were system issues. Couldn't boot anymore. Thought I "bricked" it.
I managed to factory reset and boot it again, with an operating system I downloaded from google results, of which I thought was the correct one for this model. (problem might be here? Wrong OS? If so, where and what exactly do I have to download?) Its kinda bs to me, that there are different versions depending on the country etc.
Lets continue:
Managed to successfully root it then. Everything worked fine. Samsung s9+ rooted.
After a short while, I encountered the issue I am facing since then.
Problem:
My Samsung is rebooting every day. Suddenly turns black, reboot with Samsung Logo. Fun fact, all tabs are still opened in the background afterwards. (no real reboot?)
Happens when:
- time is not fixed. Anytime possible.
- even when I'm not using it. (but mostly)
- Even while video recording. Not app specific. (I always keep only one app open btw.)
- sometimes when it happens while I use Instagram, I'm logged out of Instagram afterwards. (not sure if it happened with Facebook, but might) (I use Insta a lot, Facebook almost never)
Solutions I tried.
- Empty cache. (I think I tried it the correct way.)
- Factory reset
Not confident in the app issue belief, that I'd uninstall every single app for 2 days each.
Assumption:
I don't feel/think its one app. If so, maybe Instagram? But shouldn't be the case though. As said, I always close all apps after I put down my phone.
Maybe its the OS? What do i know..I'm a scrub.
Help highly appreciated. The reboots are driving me crazy and are tremendously inconvenient sometimes.
pkenso said:
Problem:
My Samsung is rebooting every day. Suddenly turns black, reboot with Samsung Logo. Fun fact, all tabs are still opened in the background afterwards.
Click to expand...
Click to collapse
Reasons to Cause Android Phones Keep Restarting
1. Corrupted data in memory.
2. Incompatible third-party apps.
3. Outdated cached data.
4. Hardware issue.
Boot Android into Safe Mode
Safe Mode is a good place to help you to track down the causes of problems occurring on your Android phone. Once you boot your phone into safe mode, all third-party apps installed on your device will be got rid of. In this mode, check if your phone still keeps restarting without any reason. In case the problem disappears, then a third party app is the main cause of the problem. All you need is to find out and delete it from your phone.
jwoegerbauer said:
Reasons to Cause Android Phones Keep Restarting
1. Corrupted data in memory.
2. Incompatible third-party apps.
3. Outdated cached data.
4. Hardware issue.
Boot Android into Safe Mode
Safe Mode is a good place to help you to track down the causes of problems occurring on your Android phone. Once you boot your phone into safe mode, all third-party apps installed on your device will be got rid of. In this mode, check if your phone still keeps restarting without any reason. In case the problem disappears, then a third party app is the main cause of the problem. All you need is to find out and delete it from your phone.
Click to expand...
Click to collapse
So I assume if the problem still persists in safe mode, its a firmware issue?
I'll try the wiped cache now until it reboots again. If so, then safe mode.
safe mode (no apps) just seems hard as I use my phone for work and the issue appears randomly within 48 hours..
--- Instead of safe mode, would be the same if I just uninstall for example a few apps for a certain time?
--- I read about a master reset. Wouldnt the simpliest and 100% working method be to just reset the phone with a new firmware? Which I can download where?