I'm running X10 Eminence and everything's been fine for a while.
Now, I'm finding a lot of apps that cut my wifi/data connection the minute they are opened. The signal is dropped immediately when I open Handscent, Flixter, Weather Channel and I'm sure I'll discover more. Some apps work just fine, but others the network just cuts right off. The minute I go back to the homescreen, data/wifi reconnects.
No one has any clue or has an idea how to fix this?
Is your phone Rooted? if it is, you might have done something wrongly... if not, how bout you try and do a factory reset? backup your stuff 1st
If all else fail, then the problem might be with your SIM card...
My apps are backed up weekly. Restoring them has not helped at all and neither has reinstalling them. My phone has been in the same state of root for months now. All other apps work fine with data - just a select few.
I'd like to avoid having to redo everything again.
cwepruk said:
My apps are backed up weekly. Restoring them has not helped at all and neither has reinstalling them. My phone has been in the same state of root for months now. All other apps work fine with data - just a select few.
I'd like to avoid having to redo everything again.
Click to expand...
Click to collapse
Might be related, but I found whenever I killed "Backup & Restore" using any task manager the network would be lost and restart. If I left it alone it seemed fine.
Maybe some apps hook into some autostart thing that monitors network connectivity... ??
Turns out Adblocker was the culprit. I deleted it and everything works fine.
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 having a problem with my Verizon G2. I had the Xposed framework installed, and I installed an app called Xorware, which is a toggle for 2G/3G/4G. I messed around with the settings in the app a little bit, and left it alone. A bit later, the phone stopped connecting to the mobile data network. I tried uninstalling the Xorware apps, wiping the cache on my phone, and even restoring to a backup where I don't have Xposed installed, and I'm still getting the same issue. Wifi still works, but every couple of minutes it disconnects randomly and then connects again. I also tried removing the SIM card for a few minutes after turning off the phone, and still, no luck.
Is there any way I can fix this, or do I have to go and get a new SIM card?
joeb124 said:
Hi,
I'm having a problem with my Verizon G2. I had the Xposed framework installed, and I installed an app called Xorware, which is a toggle for 2G/3G/4G. I messed around with the settings in the app a little bit, and left it alone. A bit later, the phone stopped connecting to the mobile data network. I tried uninstalling the Xorware apps, wiping the cache on my phone, and even restoring to a backup where I don't have Xposed installed, and I'm still getting the same issue. Wifi still works, but every couple of minutes it disconnects randomly and then connects again. I also tried removing the SIM card for a few minutes after turning off the phone, and still, no luck.
Is there any way I can fix this, or do I have to go and get a new SIM card?
Click to expand...
Click to collapse
That's really odd. I'd try and update the PRL and / or Profile and see if that helps. If it doesn't, then might have to restock the phone with the kdz file. It's kind of a pain, but probably not as much as not having data.
So I know this topic has a few posts many a year or so old but I'm looking for a possible work around for this issue. Here's a background of what happened:
I have a rooted note 4 originally running cm12, I wanted to return to a stock build and when I did something happened (can't remember what) and my wifi stopped working it would click on them immediately off my first thought was kernel so I flashed a new one but didn't help I tried a different stock build 5.0.1 instead of 5.1.1 but still same issue. I went back to the cm12 and that seemed to work fine still, I looked for another stock build because I'm stubborn and flashed a different kernel than the previous ones I've tried. This seemed to fix my wifi issue at least for a day then back to the same issues. Anyway here's what I've been messing with to try and figure this out.
I'm focused around the file wpa_supplicant.conf as I've tried restarts and all that but that won't do anything. What I have noticed recently is when I don't have any networks saved in that file I can toggle airplane mode and try toggling wifi, after a few sometimes dozen attempts it comes on and works fine so long as it stays on. If I turn it off I have to restart my process of going into wpa_supplicant.conf>deleting my saved network>toggling airplane>then spamming wifi. As I'm able to repeat this it leads me to believe it's not hardware related, slim chance on loose cable, But if there's a way to prevent the system from auto saving a password that might help with a workaround. I've tried changing that files permissions as well as the ones in the system>etc>wifi folder but they get changed back
Anyway I'm still working on finding the root cause but will update if I find anything also tried deleting the wpa file and that works to after a restart but issue comes back and so does file which doesn't seem to me that its a corruption issue
Update:
So I somehow crashed my Samsung messenger app switch to hangouts and then back so decided to wipe my phone and refresh the OS. I factory reset then advanced wiped cache, dalvik, system and data. When it rebooted I tested the WiFi in the system setup and it worked fine I could turn it on and then off normally so I decided to continue setup once fully setup and no other apps installed I retested the WiFi. It worked fine I connected to an access point and it stayed connected I then forgot the network cycled wifi and tried again and again still worked so I let it sit and would test it throughout the day. About an hour or so later the problem reappeared which was odd. I did my old workaround deleting wpa_supplicant.conf and toggling wifi until it turns on. I got it to turn on and connect to my home WiFi and left it, so far I've kept my wifi on and it's stayed active for 24hours now and reconnects fine to my home router when I'm in range and back to lte when I'm away so right now it seems I can have wifi if I don't toggle it off. Still not sure what's causing this issue as since I'm currently using wifi to write this I don't see it as a hardware issue. After trying multiple kernels I don't see that as the cause either, although possible. Will keep messing around and update if I find anything further
Update 2: so far I've been able to keep my wifi working great as long as I keep it on and don't toggle it off. Doing this has kept it active and auto connecting to my home wifi for a week straight. I make sure to keep wifi I during sleep so it won't disconnect but it also seems to stay active through restarts which is great. This still leads me to believe it's software related and not hardware but not sure where the issue is.
Update 3:
So far I've just kept my wifi on while trying to find the issue. The only other issue I've come across was since my wifi is on 24/7 and auto connects if I want to use my lte instead i have to either turn off wifi or forget my home network which neither is an option. But I have found a solution:
I was able to add a shortcut to my home screen that actually disables the current wifi connection without disabling wifi and forgetting the password. To do this you must have Tasker just create a new task in second tab, I named mine disconnect wifi, click the plus sign and select "net", next select "wifi net" there is an option that says disconnect. Have that selected then go back and thats it,add in icon on bottom right to use as a shortcut. I've tested this and it works great one tap and it disconnects the wifi but keeps wifi turned on and if I want to re connect just go into WiFi settings and choose the one to connect to
Hey.
So I for the past month of so, my phone has been getting this weird issue where the network will suddenly cut and I'll be left with signal but no Data... It happens at very weird and pattern like intervals... What I mean is that it can happen when I'm using my phone. It can also happen on its own when my phone is in my pocket... Strange. If I manage to get home for example without it happening I can sometimes manage to turn on WiFi and the day afterwards when I leave Data still works. Now the only way I have found of fixing it is to Reboot my phone completely...
I have tried it on different Roms and even different Versions! So it seems to be a configuration problem? But I've wiped my phone between those Rom changes and I change quite often (Titanium, simply the best app on the entirr play store).
So it's very annoying and I can't figure out the pattern or what causes. I hope someone will be able to help.
Thanks!
+1 on that.
If anyone can elaborate, that would be very nice.
Hello
I've had a Samsung Galaxy S3 for ages, unfortunately for me, the phone recently just switched off, then on, then won't go past the "Samsung" screen. Ah, I thought (well, something a bit more sweary) - but I had a backup identical model phone in case one broke, so I started using that. Moved all my apps, installed banking app etc, and then happy.
Or so I thought...
The new (well, it's an old phone, but one I haven't been using, bought as back up) phone now switches off when charging every night, an issue which was going to switch to me charging it during the day when I can stare at it and see if anything happens to make it switch off, but then I realised it switches off each night even when it isn't charging.
I have a bigger battery to hold a charge for a few days, and so even when I don't charge it, just have it next to me as I sleep - and next morning it will be off. I presume it might be switching off around 5am... this is only a rough guide as if I switch it back on, and flick through the phone, I see my unread emails are up to around 5am, and then after a few minutes it logs back into the internet etc and brings me newer emails.
I first thought it was that it kept switching off when charging... but now I know it does it at (I presume) the same time every night even when it's not charging. Can't use it as an alarm clock anymore, as it's off before the alarm goes off. Anyone have any idea what's happening?
Did you copy all of your data and settings?. Most likely you have a software conflict going on.
I highly recommend you backup your data from all 3rd party apps. Do not backup your system apps data, google data, apps or games that cloud sync or phone settings, ie wifi passwords etc.
You must allow samsung apps, google and other cloud apps to sync their own way and you must calibrate the phone for wifi manually.
Beyond that you'll need to reflash stock firmware and start over using the guidlines I have given you above after restoration of the firmware (and root if required).
Beamed in by telepathy.
I assume when I installed on the other phone, it switched settings when I log in to various things. Because I installed everything asap, I've no idea if one thing is causing the issue.
How do I get the phone to calibrate manually? Apologies, I'm not great with techie stuff I add the wifi details, and logged into settings - is that manually? Things are backed up to themselves, so when I log back in it resets to previous settings when it syncs. Should I try and work out how to prevent all things from backing up manually? Haven't logged back into any games, although they might be installed, haven't actually signed in or used them.
How would I go about reflashing stock firmware? Doesn't sound like anything I've ever done before, but up for a challenge
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
shivadow said:
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ahh, cool, gottcha! Ok, will try soon. Surprisingly, I've switched off the phone every night instead of it auto-switching off at around 5-6am, and surprisingly it's so far going well. Had it on for 3 days and only at 47% now, so it's promising, still does switch off occasionally during the day, but I've just ignored that. Will do a factory reset in the next couple of days and report back Thanks for the help