My SGS2 was suddenly rebooted itself when I connected it to my PC. It didn't happen before and it does not happen now.
My question is, when something goes wrong and the phone suddenly reboots or a specific app crashes or whatever (just one time, not on a regular basis) how can I know if any damage was done, to data for example, like a corruption, and whether or not should I reinstall this app or wipe and flash the phone?
I was just about to finish configuring settings and installing apps after a clean ROM installation when it happened, and so I thought about doing everything all over again because I wanted it to be "perfect".
If anyone shares this annoying habit I'm sure you will know what I'm talking about. I figured out I might just ask a pro about this thing I usually do, as I am aware that it is possible that there is absolutely zero logic to it and it is all in my head
Thanks.
P.S: Didn't post in the device forum because I figured it is a question that is based on the Android OS nature rather than subjective to a specific device model.
Clean install, re-flash rom.
Press thanks if this post helped.
sanpedro_bonita said:
Clean install, re-flash rom.
Press thanks if this post helped.
Click to expand...
Click to collapse
I was hoping for a little bit more info
Is there any reason to re-flash just because of a single crash? if so, please elaborate as I am very willing to understand the considerations.
Thanks.
Anyone?
why dont you do a research on logcats !!
if you can understand logcats fine or else just post the logcats in the forum of the app that causes crashing!!
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
MoonBlade said:
why dont you do a research on logcats !!
if you can understand logcats fine or else just post the logcats in the forum of the app that causes crashing!!
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Click to expand...
Click to collapse
Because I'm not asking about troubleshooting a crashing app... nor a faulty OS installation.
I'm asking about the general idea of re-flashing a phone just because the OS suddenly crashed, one time only, without any special use for the moment.
You said your phone rebooted after you connected it to the pc. This the problem. No need to reflash imo, just close all apps when connecting next time.
Sent from my GT-I9000 using xda app-developers app
rechazame said:
Because I'm not asking about troubleshooting a crashing app... nor a faulty OS installation.
I'm asking about the general idea of re-flashing a phone just because the OS suddenly crashed, one time only, without any special use for the moment.
Click to expand...
Click to collapse
what do you mean by OS suddenly crashed.. is it that it rebooted all of a sudden out of nowhere or are there some system process that gets FC ?
if its happened one time only no need to reflash... if problem exists reflash with proper wipe..
wget21 said:
You said your phone rebooted after you connected it to the pc. This the problem. No need to reflash imo, just close all apps when connecting next time.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
It was actually right after I power it up so maybe it was still loading some stuff? and btw, how do I close all apps? I can google it of course but then I will find about 5698 different ways to do it without knowing which one did you mean
MoonBlade said:
what do you mean by OS suddenly crashed.. is it that it rebooted all of a sudden out of nowhere or are there some system process that gets FC ?
if its happened one time only no need to reflash... if problem exists reflash with proper wipe..
Click to expand...
Click to collapse
Kind of out of nowhere, yes, but even if it had something to do with me connecting it to the PC too soon after starting the phone - I am still curious if a sudden crash (a single one out of nowhere) can make some sort of a damage to any system or app data that it is recommended to re-flash or something.
I really hope you got my point. I used all my English skills to this one! :laugh:
rechazame said:
Kind of out of nowhere, yes, but even if it had something to do with me connecting it to the PC too soon after starting the phone - I am still curious if a sudden crash (a single one out of nowhere) can make some sort of a damage to any system or app data that it is recommended to re-flash or something.
I really hope you got my point. I used all my English skills to this one! :laugh:
Click to expand...
Click to collapse
android can crash when it runs out of RAM. Doesnt necessarily mean that a system app is damaged. if however a system app is damaged it will show up as a FC (force close) rather than a reboot.
so still im of the opininon that you dont have to reflash you rom yet...
How exactly did it work? Did you connect your phone to PC and then it rebooted?
By closing all apps i meant removing everything from recents screen.
MoonBlade said:
android can crash when it runs out of RAM. Doesnt necessarily mean that a system app is damaged. if however a system app is damaged it will show up as a FC (force close) rather than a reboot.
so still im of the opininon that you dont have to reflash you rom yet...
Click to expand...
Click to collapse
So you are basically saying that if something wrong happened like a sudden reboot, and it doesn't happen again, you wouldn't mind about it. Correct?
wget21 said:
How exactly did it work? Did you connect your phone to PC and then it rebooted?
By closing all apps i meant removing everything from recents screen.
Click to expand...
Click to collapse
Yeah. But it didn't happen since. Just this one time.
I got curious about what might have caused it and what might have happened because of it and decided to ask here if it makes sense to re-flash
your rom is fine. The reboot used to happen to me from time to time when i plugged it into the computer or when i uninstalled an app. It had something to do with an app being executed in the background and not releasing every ressource. This didnt happen on the last few builds for me though...
wget21 said:
your rom is fine. The reboot used to happen to me from time to time when i plugged it into the computer or when i uninstalled an app. It had something to do with an app being executed in the background and not releasing every ressource. This didnt happen on the last few builds for me though...
Click to expand...
Click to collapse
And can a sudden reboot cause any damage to any app or sys data integrity?
normally not. if you dont have fc over fc then you dont need to reflash
rechazame said:
So you are basically saying that if something wrong happened like a sudden reboot, and it doesn't happen again, you wouldn't mind about it. Correct?
Click to expand...
Click to collapse
i wouldnt mind it if its a one time thing !!
Thanks guys.
Related
about a month ago this happend to me:
out of the blue everything on my phone started FC repeatedly (whatsapp, camera, Luancher Pro, phone, etc..) so pulled out the battery and it then it didnt want to boot up so i tried a fresh install from recovery but.. recovery was crashing as well and i had to pull out the battery every time. finally afer playing a speed game with the phone i got to re install (i wiped user chache/data /dalvik ) and the problem was gone ...
these recent days some apps started FC on me but i thought i was somewhat common .. mainly Mi file explorer .. so right now my phone started to do the same thing again.. FC everything! The main one crashing is = the process com.android.phone stopped unexpectedly. i have no signal now and cant open anything.. if i pull out battery I know it wont boot up and may not let me use recovery without a hassle!
i dont know if this has to do with but when i install a rom ( i had topsmarts 1.3) i use root uninstaller to uninstall lots things i dont want like: weather and news, terminal emulater, dev tools, es explorer..
what is can be causing this problem and what can i do to fix it??? it looks like i wont be using it today because its as good as a brick right now.
edit before OP: i selected reboot and as expected its looping at the Unlocked screen:crying:
Try re-flashing it anyway... if there's a recovery problem again let us know
Sent from my MB860 using xda app-developers app
ticiano_arraes said:
Try re-flashing it anyway... if there's a recovery problem again let us know
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
hey so i went into recovery and wiped and re-installed like normal... and its up and running again..
but the question is what causes it? i dont want this to happen again in X days
antmiu2 said:
hey so i went into recovery and wiped and re-installed like normal... and its up and running again..
but the question is what causes it? i dont want this to happen again in X days
Click to expand...
Click to collapse
It's not a living thing or a machine with mechanics that suddenly doesn't work because of a misconception. If it was a misconception it would not work at all. If you solved it by reflashing, then it's a software issue and it won't happen again if your CWM image is not broken. But just to make sure I would reflash CWM to make sure it doesn't cause any trouble.
and be careful with removing system apps
Sent from my MB860 using xda app-developers app
I believe it was you removing system apps which caused your problems. You should always freeze system apps instead of uninstalling/removing them. That way if your phone starts to act up you can thaw/unfreeze them until you figure out which one is causing the issue.
ticiano_arraes said:
and be careful with removing system apps
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Exactly. Removing system apps can result in accidental removal of base code and intrinsic system processes that are required for your ROM to function properly. These apps can probably be disabled and hidden instead of removing them altogether.
Sent from my iPad using Tapatalk HD
A logcat would help tremendously here. Would show exactly why things are FCing.
sorry i dont know how to do a logcat .. but the things i remove are:
es file explorer
news and weather
gtalk
terminal emulator
theme chooser
voice dailer
antmiu2 said:
sorry i dont know how to do a logcat .. but the things i remove are:
es file explorer
news and weather
gtalk
terminal emulator
theme chooser
voice dailer
Click to expand...
Click to collapse
You really have to freeze apps one by one if you are unsure of what you are doing. On stock Blur build for example, Yahoo Authenticator can cause FC issues with your contacts if you freeze or delete it. You wouldn't think this would affect your contacts, but it does.
Hi!
I am using DSC's ROM (on 1.7 ATM) and I sometimes get a "flashing lights" and immediate reboot when my phone tries to use location services -I can't be sure if it's GPS, WiFi, or both-. I think I flashed the right BB when I installed the ROM -there was a batch script that took care of that if I remember correctly-, but quite frankly, after having spent many hours around the forums, not being sure what to do exactly, and having a bit of fear of bricking it/whatever; I'd rather ask beforehand. So:
What should I do?
About phone says:
BB: GAUSB1A1406214-EU
Thanks!
try disabling > use wireless networks
it should be inside > location & security settings
something similar..
I just did; the phone crashed and it's now rebooting. I was running logcat at the time, but nothing relevant showed before the reboot.
well... usually try using dsc 1.0 and see what happen..
there are reports that google maps is the causing of the problem though.. i dont use it btw...
Oddly enough, I've just tried several apps which use location services and it has not yet crashed. It's not getting a fix since I'm indoors, but at least it hasn't crashed yet...
europeancity said:
Oddly enough, I've just tried several apps which use location services and it has not yet crashed. It's not getting a fix since I'm indoors, but at least it hasn't crashed yet...
Click to expand...
Click to collapse
Try installing the latest version (2.1) or DSC 2.0 they have less or even none issues. Don't forget to wipe caches and fix permissions.
The behaviour didn't change when I upgraded from an older DSC ROM to 1.7... Why would it matter exactly? Were there any bugs corrected on that release that could affect the location services?
europeancity said:
The behaviour didn't change when I upgraded from an older DSC ROM to 1.7... Why would it matter exactly? Were there any bugs corrected on that release that could affect the location services?
Click to expand...
Click to collapse
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1751041
I read the linked thread and it sounds very much like the problem I'm having. However, I thought that problem had already been corrected by 1.7, and I couldn't see any output on the logcat the last time it rebooted. So: should I try with the 366BB and Kernel? Should I upgrade to 2.1? Thanks!
europeancity said:
I read the linked thread and it sounds very much like the problem I'm having. However, I thought that problem had already been corrected by 1.7, and I couldn't see any output on the logcat the last time it rebooted. So: should I try with the 366BB and Kernel? Should I upgrade to 2.1? Thanks!
Click to expand...
Click to collapse
I disabled the reboot code in kernel but no idea if it helps really.
Upgrade won't hurt i think.
_n0p_ said:
I disabled the reboot code in kernel but no idea if it helps really.
Upgrade won't hurt i think.
Click to expand...
Click to collapse
I can't really be sure about it, but... wasn't that change already present in 1.7?
How long could it take, and how hard would it be for a n00b like myself (although with some programming experience) to add some logging output when the reboot *would have* happened?
Thank you really! I'm getting more and more interested in this!
europeancity said:
I can't really be sure about it, but... wasn't that change already present in 1.7?
How long could it take, and how hard would it be for a n00b like myself (although with some programming experience) to add some logging output when the reboot *would have* happened?
Thank you really! I'm getting more and more interested in this!
Click to expand...
Click to collapse
2.1 has an option to disable kernel NoSync hack.
Also, look here:
http://forum.xda-developers.com/showpost.php?p=35386212&postcount=5686
Sweet. I will flash it and come back with feedback.
Thanks!
Sent from my Dell Streak using xda app-developers app
Hey all,
I don't know if this is the right place exactly (I couldn't see a CM-specific thread), and I've tried posting on CM official forums but no-one seems to bother replying.
I updated from cm11 m8 to m9. All seems well but after booting the phone, I'm gradually greeted with a series of 'xx app has stopped working' messages.
Its mostly the Google apps, like Sheets,Docs,Drive etc. but also (more crucially) the WhisperSoft app which I believe is why I can no longer do text entry in a swipe-like manner. I've written this message using the peck method.
Anyone know what I should do?
As I say, no-one is answering on CM forum and I don't know what to do.
If anyone has advice, i'd be greatful.
Regards.
Do a factory reset.
Choristav said:
Do a factory reset.
Click to expand...
Click to collapse
Are you serious?
That seems ridiculous. Is there nothing else I can do that's less drastic?
SkEvol said:
Are you serious?
That seems ridiculous. Is there nothing else I can do that's less drastic?
Click to expand...
Click to collapse
You can stop senselessly flashing stuff if you can't manage your own system.
Choristav said:
You can stop senselessly flashing stuff if you can't manage your own system.
Click to expand...
Click to collapse
So.. I have to start from scratch because an official update knackers things up?
I have nothing against 'managing my own system' but starting from scratch is... Everything...
And I personally don't see it as 'senseless' to apply an update which is official.
I just think an problem which effects some of the fundamentals (text input) is a silly oversight and if the only method of fixing this is to do a factory reset something about the deployment/update method needs revising.
SkEvol said:
So.. I have to start from scratch because an official update knackers things up?
I have nothing against 'managing my own system' but starting from scratch is... Everything...
And I personally don't see it as 'senseless' to apply an update which is official.
I just think an problem which effects some of the fundamentals (text input) is a silly oversight and if the only method of fixing this is to do a factory reset something about the deployment/update method needs revising.
Click to expand...
Click to collapse
You seem confused, that's not an official update. An official update does not mean dirty flashing. An official update does not mean anything related to GAPPS either, not even close, considering the overwhelming amount and different editions of these.
So.. what are you complaining about? Suck it up, backup, do a fresh install, restore. Takes 30 minutes. And don't flash anything if you can't handle it.
OK fair enough, you've made your point. You think I'm being wingey about having to factory reset, and I'm still none the wiser about why it's happened. I know my original question was 'what can I do?' and you answered that but I think by now you're probably not prepared to go further and help my understand why its happened so if anyone else has had the same thing happen just sound off.
PS I called the thread title 'problem with Google apps' because it's mainly those apps and the play store which are crashing. And to my noobie understanding, I'd called it an 'official update' because it came straight through to the phone; no tinkering about downloading, purposely booting into a mode to flash anything. I did it via the update options in cm settings.
SkEvol said:
OK fair enough, you've made your point. You think I'm being wingey about having to factory reset, and I'm still none the wiser about why it's happened. I know my original question was 'what can I do?' and you answered that but I think by now you're probably not prepared to go further and help my understand why its happened so if anyone else has had the same thing happen just sound off.
PS I called the thread title 'problem with Google apps' because it's mainly those apps and the play store which are crashing. And to my noobie understanding, I'd called it an 'official update' because it came straight through to the phone; no tinkering about downloading, purposely booting into a mode to flash anything. I did it via the update options in cm settings.
Click to expand...
Click to collapse
it's not official, it's just snapshot
http://download.cyanogenmod.org/?device=i9300
I have an issue that I cannot pinpoint the cause of figure out a solution to. Maybe someone here can help.
My Sprint G3 is always crashing and rebooting the launcher (phone doesn't turn off, just closes evwrything). I'd be in the middle of any app and it will randomly close every single app. The running apps page always displays after every crash. It's as if too much ram is being used, but it will happen even after a fresh phone restart and launching something simple like WhatsApp.
My phone is rooted via the Stump one click method. I don't have any type of rooted mods enabled, only Adfree. I use Nova launcher (paid & updated).
Is there some sort of event viewer that will log the activity of the phone so I probably someone here can see what might be causing the phone to crash? I'm tempted to Unroot and restore back to stock... But if I can avoid that, I'd greatly appreciate it.
Syph said:
I have an issue that I cannot pinpoint the cause of figure out a solution to. Maybe someone here can help.
My Sprint G3 is always crashing and rebooting the launcher (phone doesn't turn off, just closes evwrything). I'd be in the middle of any app and it will randomly close every single app. The running apps page always displays after every crash. It's as if too much ram is being used, but it will happen even after a fresh phone restart and launching something simple like WhatsApp.
My phone is rooted via the Stump one click method. I don't have any type of rooted mods enabled, only Adfree. I use Nova launcher (paid & updated).
Is there some sort of event viewer that will log the activity of the phone so I probably someone here can see what might be causing the phone to crash? I'm tempted to Unroot and restore back to stock... But if I can avoid that, I'd greatly appreciate it.
Click to expand...
Click to collapse
If you're running ART that could cause that. Go back to dalvik and see if that cures it.
engine95 said:
If you're running ART that could cause that. Go back to dalvik and see if that cures it.
Click to expand...
Click to collapse
I believe I'm still on dalvik as I never changed that setting.
Syph said:
I believe I'm still on dalvik as I never changed that setting.
Click to expand...
Click to collapse
Maybe it's Adfree then. There's a special version that some people are using. It's in it forum somewhere. I'll see if I can find it.
In the meantime, uninstall it and see if it goes away.
engine95 said:
Maybe it's Adfree then. There's a special version that some people are using. It's in it forum somewhere. I'll see if I can find it.
In the meantime, uninstall it and see if it goes away.
Click to expand...
Click to collapse
Thanks. I've reverted my adfree hosts file and uninstalled it. But I think the issue persists. If I try to use any app that clears cache, specifically Clean Master, when it's doing the scan of apps it'll crash midway through the scan. If I go to system settings > Apps & wait for all the downloaded apps to load the details, it'll crash there too.
This is the oddest thing.
Edit:
This visual may help. It's a video of me running Clean Master & seeing how it just crashes. I can replicate this issue every time like this, but the crashes are random when using other apps.
Link to video: https://docs.google.com/file/d/0B9-N9bB35E-QdnY3Zk1FaW9EMXM/edit?usp=docslist_api
Ok, so I began uninstalling some apps that I thought may have been the issue... Which they weren't as the crashing still continues. I decided to reboot under safe mode and the problem occurs there too.
I honestly cannot recall if this began before or after rooting with stump. I may have to Unroot & factory restore. =/
Syph said:
Ok, so I began uninstalling some apps that I thought may have been the issue... Which they weren't as the crashing still continues. I decided to reboot under safe mode and the problem occurs there too.
I honestly cannot recall if this began before or after rooting with stump. I may have to Unroot & factory restore. =/
Click to expand...
Click to collapse
I'm at a loss... The 2 things I mentioned can be the culprits, but not for you I guess. Some other ideas?
Did you uninstall Stump after getting root?
Have you froze or uninstalled any system apps/ priv-apps?
It might even be Nova is having issues.
That's all I got.
engine95 said:
I'm at a loss... The 2 things I mentioned can be the culprits, but not for you I guess. Some other ideas?
Did you uninstall Stump after getting root?
Have you froze or uninstalled any system apps/ priv-apps?
It might even be Nova is having issues.
That's all I got.
Click to expand...
Click to collapse
Thank you for your help. Nova was one of the apps I removed. I did remove the stump app after rooting & did not freeze/remove any system critical apps/files. I'm also at a loss.
I would try a restore to stock as the final option. If that doesn't fix it then I dunno man.
Sent from my LG G3 via Tapatalk Pro
haoleflip said:
I would try a restore to stock as the final option. If that doesn't fix it then I dunno man.
Sent from my LG G3 via Tapatalk Pro
Click to expand...
Click to collapse
I plan to do that this evening. Was hoping to not restore to stock... It'd always a pain setting up themes & apps again. Lol.
Syph said:
I plan to do that this evening. Was hoping to not restore to stock... It'd always a pain setting up themes & apps again. Lol.
Click to expand...
Click to collapse
Pssh all of that stuff can wait and can be downloaded again. My main priority would be getting my phone working again lol
Sent from my LG G3 via Tapatalk Pro
haoleflip said:
Pssh all of that stuff can wait and can be downloaded again. My main priority would be getting my phone working again lol
Sent from my LG G3 via Tapatalk Pro
Click to expand...
Click to collapse
Tried to unroot but the phone doesn't move past the "Firmware Update. Do not unplug the phone..." screen after holding Volume Up & plugging into the computer. I installed the drivers before hand. But the "CDC Serial" doesn't update. I attempted to manually update the driver by browsing for the folder, but no go.
I may end up having to go to Sprint and exchange the phone for another one.
Syph said:
Tried to unroot but the phone doesn't move past the "Firmware Update. Do not unplug the phone..." screen after holding Volume Up & plugging into the computer. I installed the drivers before hand. But the "CDC Serial" doesn't update. I attempted to manually update the driver by browsing for the folder, but no go.
I may end up having to go to Sprint and exchange the phone for another one.
Click to expand...
Click to collapse
any updates? did you ever fix the problem?
thanks!
JT-KGY said:
any updates? did you ever fix the problem?
thanks!
Click to expand...
Click to collapse
TL;DR version = Yes, I did fix it. Factory restore did the trick.
A few days after my last post the phone wasn't as bad as the video. It would still crash and reset but mainly after heavy app usage or when trying to clear app cache using any app like Clean Master.
Once my storage reached about 40% used and I couldn't clear the cache, I began to get constant Play Store error messages. No apps would update. I think it was error 483 or something close to hat number.
Since I couldn't flash back to stock because the drivers wouldn't install, I gave up and tried a factory reset. I nearly sh-t myself bc once I confirmed the restore, the phone didn't want to automatically reset per the instructions. I pressed the button multiple times and nothing. I pulled the battery and when I turned it back on, I got the initial screen with the "powered by android" and then black. It did not wanna do anything. Pulled battery again, same outcome. It left it for maybe 10min and still nothing.
I was ready to go back to sprint and see if I could exchange the phone. While researching the closest store, the phone beeped and the initial android setup screen appeared. This was about 25min of waiting on a black screen.
The phone is now back to working order and it's still rooted. There must have been a corrupt file that was erased/restored once the g3 decided to behave.
Syph said:
TL;DR version = Yes, I did fix it. Factory restore did the trick.
A few days after my last post the phone wasn't as bad as the video. It would still crash and reset but mainly after heavy app usage or when trying to clear app cache using any app like Clean Master.
Once my storage reached about 40% used and I couldn't clear the cache, I began to get constant Play Store error messages. No apps would update. I think it was error 483 or something close to hat number.
Since I couldn't flash back to stock because the drivers wouldn't install, I gave up and tried a factory reset. I nearly sh-t myself bc once I confirmed the restore, the phone didn't want to automatically reset per the instructions. I pressed the button multiple times and nothing. I pulled the battery and when I turned it back on, I got the initial screen with the "powered by android" and then black. It did not wanna do anything. Pulled battery again, same outcome. It left it for maybe 10min and still nothing.
I was ready to go back to sprint and see if I could exchange the phone. While researching the closest store, the phone beeped and the initial android setup screen appeared. This was about 25min of waiting on a black screen.
The phone is now back to working order and it's still rooted. There must have been a corrupt file that was erased/restored once the g3 decided to behave.
Click to expand...
Click to collapse
Congrats!
My G3 is crashing in the similar manner as the video you uploaded.
Except that it only happens when I'm in office connected to office wifi with almost no cellular reception.
On top of that, as far as I could tell... only two apps are causing the launcher to crash... the game Clash of Clans and LINE.
Very very strange....
I'm sure many of you are already using @kessaras great AOSCP Oreo Rom!
One small current issue is the ril-daemon sometimes needs to be stopped and started to make your sim card and cellular work properly. In the past, you could just reboot, or stop and start the daemon from the command line. But now you can just tap a button! That's right, just a simple, easy to use app that stops or starts the ril-daemon when you tap the buttons.
This app requires root permission!
This app is open source, licensed under the Apache 2.0, and you can check out the source code here:
https://github.com/alaskalinuxuser/app_ril_control
You can download the app here:
https://github.com/alaskalinuxuser/app_ril_control/blob/master/app/Ril_Control.apk
Get it on the Play Store!
https://play.google.com/store/apps/details?id=com.alaskalinuxuser.rilcontrol
Reserved for Change log.
great tool ! Thank you ! it will make easier this ril restart for everyone
Thank you very much, this is very useful!
I'm using it quite often. It's very useful for me. Thank you so much!
tqwzUX6fn39GZMEzSnDF said:
I'm using it quite often. It's very useful for me. Thank you so much!
Click to expand...
Click to collapse
Great! I'm glad you like it and find it useful!
Have you tried my kppd control app?
https://forum.xda-developers.com/showthread.php?t=3639878
Sent from my Life One X2 using XDA-Developers Legacy app
AlaskaLinuxUser said:
Great! I'm glad you like it and find it useful!
Have you tried my kppd control app?
https://forum.xda-developers.com/showthread.php?t=3639878
Sent from my Life One X2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, I didn't try this app. Color and so on is fine for me.
But I had to reboot very often due to missing sim detection and I'm happy that I don't need to do it anymore.
This will surely save folks the hassle of using the Terminal to restart the Radio Interface Layer.
Muchos gracias @AlaskaLinuxUser
---------- Post added at 08:05 AM ---------- Previous post was at 08:05 AM ----------
This will surely save folks the hassle of using the Terminal to restart the Radio Interface Layer.
Muchos gracias @AlaskaLinuxUser
Just wondering if the change is supposed to be instant when I press the button. I have a newly unlocked H812 and it takes sometime ten tries to get it to work
Hey it is possible to add a function like automatic restart the ril-daemon with different time settings?
Like restart it ervery 24 or 15 hours.
I have problems with my G4 on LOS 14 Roms the ril stop working after different hours.
Hey @AlaskaLinuxUser I am curious, can this be used for newer ROMs? I am using LineageOS 15.1 and experience mobile data drop off all the time. I would like to use this app (Google Play pulled the app, I used your direct download link) to see if it would help.
Any issues doing this?
FirebirdStud said:
Hey @AlaskaLinuxUser I am curious, can this be used for newer ROMs? I am using LineageOS 15.1 and experience mobile data drop off all the time. I would like to use this app (Google Play pulled the app, I used your direct download link) to see if it would help.
Any issues doing this?
Click to expand...
Click to collapse
Yes, I was using it on aoscp Oreo, so it should work on 15.1. :good:
Yes, Google Play is pulling a lot of my apps. Root apps and apps for 32 bit phones are harder to keep on the Play store.
AlaskaLinuxUser said:
Yes, I was using it on aoscp Oreo, so it should work on 15.1. :good:
Yes, Google Play is pulling a lot of my apps. Root apps and apps for 32 bit phones are harder to keep on the Play store.
Click to expand...
Click to collapse
Thanks for the quick response! I am on a Samsung Note 4 with custom ROM based on Android 8.1, so I wasn't sure if this was specific to any make or operating system.
FirebirdStud said:
Thanks for the quick response! I am on a Samsung Note 4 with custom ROM based on Android 8.1, so I wasn't sure if this was specific to any make or operating system.
Click to expand...
Click to collapse
It should work. It may need busybox or toybox installed, which were on the original ROM I built this for.... Of course, root is required.
Let me know how it turns out.
AlaskaLinuxUser said:
It should work. It may need busybox or toybox installed, which were on the original ROM I built this for.... Of course, root is required.
Let me know how it turns out.
Click to expand...
Click to collapse
Hmm, I don't want to get in over my ski-tips here.
I am new to rooting. I was tired of an older phone with a poorly performing operating system, so I travelled down this road to revitalizing my phone - without spending over a thousand dollars for a new one.
I do not know what busybox or toybox is, or if it is incorporated into this LineageOS operating system v15.1 for the Samsung SM-N910V.
I do have root, managed by Magisk Manager v17.3, and use TWRP v1.21 build 34 for recovery.
I do not have a recent backup or anything like that, as I am a noob and use this phone as a daily driver. I don't want to really screw anything up by installing this app. Do you think there could be incompatibilities that could cause issues? I am trying to avoid continually backing up all of my data and files to my computer, as it takes forever. (yeah, I realize that developing new stuff is a gamble, but I am trying to find stable things already built )
The only issue with this ROM is RIL instability when switching towers, and going into buildings that forces the data connection to go from LTE to 3G, and that is when I lose data connection. I have to restart the phone every time, and I end up having to do this a lot while driving and travelling for work.
What are your thoughts?
FirebirdStud said:
Hmm, I don't want to get in over my ski-tips here.
I am new to rooting. I was tired of an older phone with a poorly performing operating system, so I travelled down this road to revitalizing my phone - without spending over a thousand dollars for a new one.
I do not know what busybox or toybox is, or if it is incorporated into this LineageOS operating system v15.1 for the Samsung SM-N910V.
I do have root, managed by Magisk Manager v17.3, and use TWRP v1.21 build 34 for recovery.
I do not have a recent backup or anything like that, as I am a noob and use this phone as a daily driver. I don't want to really screw anything up by installing this app. Do you think there could be incompatibilities that could cause issues? I am trying to avoid continually backing up all of my data and files to my computer, as it takes forever. (yeah, I realize that developing new stuff is a gamble, but I am trying to find stable things already built )
The only issue with this ROM is RIL instability when switching towers, and going into buildings that forces the data connection to go from LTE to 3G, and that is when I lose data connection. I have to restart the phone every time, and I end up having to do this a lot while driving and travelling for work.
What are your thoughts?
Click to expand...
Click to collapse
This app will not cause you any trouble. It will either work, or will not work, but will have no detrimental affect on your phone or files. I'd recommend you give it a try. But it is always up to you.
AlaskaLinuxUser said:
This app will not cause you any trouble. It will either work, or will not work, but will have no detrimental affect on your phone or files. I'd recommend you give it a try. But it is always up to you.
Click to expand...
Click to collapse
I took the leap, and while out and about today I installed RIL Control. And guess what, it worked! I was able to kick the data connection in the butt and it reconnected.
However, I have a big problem now. I got home, and turned on wifi, and it doesn't work now. The toggle switch moves to on, and then right back to off. I cannot get the wifi to turn on! I restarted the phone, and it still won't turn on. Bluetooth works just fine.
So, now what happened? How do I get wifi to work again? Honestly, I need wifi more than data connection at this point.
FirebirdStud said:
I took the leap, and while out and about today I installed RIL Control. And guess what, it worked! I was able to kick the data connection in the butt and it reconnected.
However, I have a big problem now. I got home, and turned on wifi, and it doesn't work now. The toggle switch moves to on, and then right back to off. I cannot get the wifi to turn on! I restarted the phone, and it still won't turn on. Bluetooth works just fine.
So, now what happened? How do I get wifi to work again? Honestly, I need wifi more than data connection at this point.
Click to expand...
Click to collapse
Odd. The commands in the app only stop/start ril-daemon, which has nothing to do with WiFi. WiFi is wpa-supp. So I'm not sure if that is connected to my app. However, if that is the only thing you installed/changed, then I guess that would have to be it.
I'm guessing restarting the phone didn't work? :fingers-crossed:
You could always uninstall my app. But if that doesn't work, I guess you would have to load a backup of your phone. I just don't see how my app is affecting the WiFi.
AlaskaLinuxUser said:
Odd. The commands in the app only stop/start ril-daemon, which has nothing to do with WiFi. WiFi is wpa-supp. So I'm not sure if that is connected to my app. However, if that is the only thing you installed/changed, then I guess that would have to be it.
I'm guessing restarting the phone didn't work? :fingers-crossed:
You could always uninstall my app. But if that doesn't work, I guess you would have to load a backup of your phone. I just don't see how my app is affecting the WiFi.
Click to expand...
Click to collapse
Thanks for the help.
Correct, installing and using your app is the only change I have made, and I have never had a wifi issue in the month or so that I have been running this custom ROM.
Restarting the phone 4 times did not work. I may have panicked haha.
I did boot into TWRP and wipe the Dalvik cache.. and whala, I booted back up and the wifi worked.
I'm now afraid to try your app again when I am out and about, but maybe I should to see if this same condition happens again? What do you think?
FirebirdStud said:
Thanks for the help.
Correct, installing and using your app is the only change I have made, and I have never had a wifi issue in the month or so that I have been running this custom ROM.
Restarting the phone 4 times did not work. I may have panicked haha.
I did boot into TWRP and wipe the Dalvik cache.. and whala, I booted back up and the wifi worked.
I'm now afraid to try your app again when I am out and about, but maybe I should to see if this same condition happens again? What do you think?
Click to expand...
Click to collapse
Well, if you have a good backup, and since wiping dalvik and cache worked before, it might be worth a try. Was the WiFi on when you used my app? As always, if you are worried about it, you should play it safe. :good: