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
Related
I can confirm the following problems with FreeX10-Bet4:
Battery drains incredibly fast, but not always. Yesterday morning the phone got hot and I could almost see battery indicator drop. However, in the afternoon, after a reboot and once I have charged the phone, it was not that bad. At least not hot. No change of apps, environment, whatever.
Problems with BT headset. At least with mediasound. Sometimes the headset connects but most often not. The phone indicates the headset is connected (both phone and media) but mediasound goes to the loudspeaker.
(I have to post this thread since I'm not yet allowed to post to the development thread. The new policy, sorry for this.....)
bengtner said:
I can confirm the following problems with FreeX10-Bet4:
Battery drains incredibly fast, but not always. Yesterday morning the phone got hot and I could almost see battery indicator drop. However, in the afternoon, after a reboot and once I have charged the phone, it was not that bad. At least not hot. No change of apps, environment, whatever.
Problems with BT headset. At least with mediasound. Sometimes the headset connects but most often not. The phone indicates the headset is connected (both phone and media) but mediasound goes to the loudspeaker.
(I have to post this thread since I'm not yet allowed to post to the development thread. The new policy, sorry for this.....)
Click to expand...
Click to collapse
You are not the only one with this problems.. so you didn't have to make a thread for this. Read the official thread and find the answers there
I did read the official developer link and I did not really ask for help on this . My intention was to add some more info for troubleshooting, since I did not find anyone else stating problem vary over time. Since I work with system development myself I normally find all additional info on problems interesting since this could help me pinpointing the root cause.
Maybe XDA should consider open special threads just to report problems and not asking specifically for support. Now everything is mixed up, and this must be quite frustrating for the ones actually working with ROM development.
Yeah, new forum policy....
I have some points too. Maybe someone can give a hint.
I have some trouble with the audio through the headphone jack. The sound is kind of broken like a wrong DSP filter is set.
3G WatchDog does not count the traffic for each app but I am not sure if thats a problem of FreeX10 or 3G WatchDog himself.
I am still stuck on the old market app Version 1.82 and I am unable to do an update. ok, I am now at 2.2.6
Matthias M. said:
I am still stuck on the old market app Version 1.82 and I am unable to do an update. ok, I am now at 2.2.6
Click to expand...
Click to collapse
how did you get the update? manually, or did it update itself automatically?
i have freex10 running for some days now, but still the old market...actually no matter, because it does what it's needed for as well...but the new icon looks cooler...
Petarsson said:
how did you get the update? manually, or did it update itself automatically?
i have freex10 running for some days now, but still the old market...actually no matter, because it does what it's needed for as well...but the new icon looks cooler...
Click to expand...
Click to collapse
Try installing neon market
Petarsson said:
how did you get the update? manually, or did it update itself automatically?
i have freex10 running for some days now, but still the old market...actually no matter, because it does what it's needed for as well...but the new icon looks cooler...
Click to expand...
Click to collapse
manually with xRecovery
Tehouster said:
Try installing neon market
Click to expand...
Click to collapse
hmmm, what is neon market, respectively: where can i get it?!
Matthias M. said:
manually with xRecovery
Click to expand...
Click to collapse
with xrecovery? aint there simply any apk? where did you get the zip to flash from?
thx, mates!
my problem is no market and fren cannot call my phone but i can call them ...
is there no way to store credentials for MSVCHAP v2 ( wifis encryptions for universities) . i had no luck storing the password.
any help?
Matthias M. said:
manually with xRecovery
Click to expand...
Click to collapse
or like .apk with file manager.
Petarsson said:
hmmm, what is neon market, respectively: where can i get it?!
Search
with xrecovery? aint there simply any apk? where did you get the zip to flash from?
thx, mates!
Click to expand...
Click to collapse
you can flash the .zip or install .apk
Your choice.
why the led never change colour although in charging mode?
i mean when the battery is low during charging the led colour still green...
is it me the only 1 who experience this kind of problem? help me guys.. T_T
well, for me its kinda yellow while the battery stat is low and turns green from 80% upwards...or is it 90%...?
Hi
My main problems are :
1-The colors aren't good as se rom,there is some waves
2-The vpn does not connect
Sorry for bas en
Sent from my X10i using Tapatalk
Tehouster said:
or like .apk with file manager.
you can flash the .zip or install .apk
Your choice.
Click to expand...
Click to collapse
Installing .apk failed here so I found a .zip package and used it with xrecovery.
Sent from my X10i using XDA App
Hi
Please excuse my Japanglish, as well.
I had a perfectly working X10i, and installed FreeX10 Beta4. I preferred stock 2.1 rom so I tried to restore the back up I createded Xrecovery. Then it went something wrong, and I get this endless "force close" message saying system failed starting when I start up. So I cannot get to the programs now which can restore the system. No matter how many times I reboot it is same. Is my phone so called "Bricked"? Is there any way I can start restoring program by pushing bottoms when I boot up before Free X10 kicks in? This is a really costly error.
Changed the name, because it really was designed for Nookie-Froyo. Removed MediaServer and cache features because they are irrelevant with 0.6.8 and add a force status bar feature which only works if you are on ROM based off of 0.6.8 and status bar framework update.
I wrote a graphic app that views/changes the LCD Density, restarts MediaServer, allows you to see the CPU usage of the MediaServer, and clears the Market Cache and Dalvik-cache. Let me know how it works and what OS you are using? Also, let me know if you want me to add any additional functions.
why would you want to restart the mediaserver?
thefamousmoe said:
why would you want to restart the mediaserver?
Click to expand...
Click to collapse
Your nook will start to run sluggish or the youtube app is hanging.
This could be handy. Thanks, brian. I'll try it out soon.
Sent from my DROID2
looks good. will test it out soon
Thanks for this. I flashed the BT cm7 over #15. I understand there's a dpi that works for scaling with Google reader. I could use this instead of modifying build.prop?
edit: and i presume a reboot needed for it to take effect.
cabbieBot said:
Thanks for this. I flashed the BT cm7 over #15. I understand there's a dpi that works for scaling with Google reader. I could use this instead of modifying build.prop?
edit: and i presume a reboot needed for it to take effect.
Click to expand...
Click to collapse
It will reboot it for you. If you need a different density then the ones that I have included, just let me know and I will add it.
Edit: Actually, I could get it to work so a reboot is not needed and the change would not be permanent. Would this be a useful feature to add?
brianf21 said:
Your nook will start to run sluggish or the youtube app is hanging.
Click to expand...
Click to collapse
I had to use brianf other app to stop the MediaServer because of youtube keep playing audio. This was with a different froyo 2.2 ROM.
I guess this app has more functions and would also work for that purpose.
brianf21 said:
It will reboot it for you. If you need a different density then the ones that I have included, just let me know and I will add it.
Edit: Actually, I could get it to work so a reboot is not needed and the change would not be permanent. Would this be a useful feature to add?
Click to expand...
Click to collapse
i think so... the stock setting in cm7 works to show all apps in the market, but borks greader. it'd be nice if i could manually edit (permanent) the density to fix greader since i use that regularly but then quickly change it if i need/want to see my apps in the market.
tried installing this, says problem parsing the package
this supposed to work on 2.1 rom?
I think we are overlapping at least two other uses of the term "media server" (not unusual in the world of technology), making a web search difficult.
Can someone point me to an explanation of the Android use of the term?
Thanks !
davidukfl said:
tried installing this, says problem parsing the package
this supposed to work on 2.1 rom?
Click to expand...
Click to collapse
What OS are you running? How are you installing it?
ADude said:
I think we are overlapping at least two other uses of the term "media server" (not unusual in the world of technology), making a web search difficult.
Can someone point me to an explanation of the Android use of the term?
Thanks !
Click to expand...
Click to collapse
There is a service that runs at boot that handles streaming media. This service is called mediaserver. This app restarts the mediaserver binary when it starts using up the CPU.
brianf21 said:
What OS are you running? How are you installing it?
Click to expand...
Click to collapse
running stock 2.1 rom rooted
and installing it im just downloading the apk and running it.
does this need to be manually installed?
davidukfl said:
running stock 2.1 rom rooted
and installing it im just downloading the apk and running it.
does this need to be manually installed?
Click to expand...
Click to collapse
Yes, use the following command.
adb install nookcolorutils.apk
Or download it to your device and install it with astro
brianf21 said:
Yes, use the following command.
adb install nookcolorutils.apk
Or download it to your device and install it with astro
Click to expand...
Click to collapse
tried that and it didn't work
Will try this app on my nc cm7 as soon as my wife is done playing bejeweled on it.
newellj79 said:
Will try this app on my nc cm7 as soon as my wife is done playing bejeweled on it.
Click to expand...
Click to collapse
on the nc cm7 it install fine. The %cpu usage comes up blank.
Installed fine on CM7 SD version. Also shows CPU usage blank here. Nice little utility!
Awesome app!
Any chance you could add 240 dpi?
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.
The camera app on my Droid DNA crashes whenever I open it or another application that uses the camera. I am currently running CyanogenMod (11-20140405-SNAPSHOT-M5-dlx), however it behaved the same way on the stock ROM (4.1.1 and 4.2.2). When this first happened, it would work for about a week, then not work for a week. But now it seems to permanently not be working. I am wondering whether this would be a hardware issue, or if there is something software related that needs fixed. I should also add that the front camera works just fine. I will attach system and kernel logs too. They are filtered to show anything with the word "cam" present. They are in the .docx format because they're color-coded, but plaint .txt files will be there also.
Localhost798 said:
The camera app on my Droid DNA crashes whenever I open it or another application that uses the camera. I am currently running CyanogenMod (11-20140405-SNAPSHOT-M5-dlx), however it behaved the same way on the stock ROM (4.1.1 and 4.2.2). When this first happened, it would work for about a week, then not work for a week. But now it seems to permanently not be working. I am wondering whether this would be a hardware issue, or if there is something software related that needs fixed. I should also add that the front camera works just fine. I will attach system and kernel logs too. They are filtered to show anything with the word "cam" present. They are in the .docx format because they're color-coded, but plaint .txt files will be there also.
Click to expand...
Click to collapse
Can you give a specific set of steps that cause the problem?
crpalmer said:
Can you give a specific set of steps that cause the problem?
Click to expand...
Click to collapse
I just open any application that uses the rear camera, it sits for about 5-10 seconds, and then that application crashes.
I had this when I flashed to the M5 snap from the M4 as well. Clearing the cache from the camera app fixed it for me.
Sent from my HTC6435LVW using Tapatalk
supertoast92 said:
I had this when I flashed to the M5 snap from the M4 as well. Clearing the cache from the camera app fixed it for me.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I actually had already tried this, but figured I'd give it another shot. No such luck.
Localhost798 said:
I actually had already tried this, but figured I'd give it another shot. No such luck.
Click to expand...
Click to collapse
Hmm...Well, this is taking it a micro-step further, and you've probably already tried this: Along with cache, clear the data. Try force stopping the app first, clearing the cache, then the data, in that order. It shouldn't erase your pictures, but as a precaution I'd back them up first.
Maybe even reflashing the M5 snapshot after that, if that doesn't work, would be worth a shot.
Hearing that you've had problems with the camera on the stock rom though makes me feel uneasy lol...it could be faulty hardware at that point.
supertoast92 said:
Hmm...Well, this is taking it a micro-step further, and you've probably already tried this: Along with cache, clear the data. Try force stopping the app first, clearing the cache, then the data, in that order. It shouldn't erase your pictures, but as a precaution I'd back them up first.
Maybe even reflashing the M5 snapshot after that, if that doesn't work, would be worth a shot.
Hearing that you've had problems with the camera on the stock rom though makes me feel uneasy lol...it could be faulty hardware at that point.
Click to expand...
Click to collapse
Still not working. I am almost convinced that it is hardware related, but before I buy a new sensor, I'll hold out for Android 4.4.3 (the next rumored release in a week or two) as this release will supposedly have many bug fixes. That's probably the last step before I call it a hardware issue.
Localhost798 said:
Still not working. I am almost convinced that it is hardware related, but before I buy a new sensor, I'll hold out for Android 4.4.3 (the next rumored release in a week or two) as this release will supposedly have many bug fixes. That's probably the last step before I call it a hardware issue.
Click to expand...
Click to collapse
Before calling it a hardware problem, I would try a clean flash of the latest CM nightly and if it still happens to post logs.
crpalmer said:
Before calling it a hardware problem, I would try a clean flash of the latest CM nightly and if it still happens to post logs.
Click to expand...
Click to collapse
Already done
And the same problem...
The logs are the same as the ones i posted earlier.
Localhost798 said:
Already done
And the same problem...
The logs are the same as the ones i posted earlier.
Click to expand...
Click to collapse
When you say clean flash do you mean not restoring any apps, etc?
If you have nothing but the ROM and gapps installed and it does this (the logs agree with you that not much happened for 6 seconds then the camera stopped) then it is possibly a hardware problem.
crpalmer said:
When you say clean flash do you mean not restoring any apps, etc?
If you have nothing but the ROM and gapps installed and it does this (the logs agree with you that not much happened for 6 seconds then the camera stopped) then it is possibly a hardware problem.
Click to expand...
Click to collapse
I've tried safe mode, and the problem still exists. To my understanding, this is the same as a clean install because only system and gapps are allowed to run.
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: