Related
Is there a registry setting that can be changed that would prevent the phone/radio from starting up whenever the XDA exec is reset?
If I were using something such as the twin sim service from Orange that enabled you to use two sims with the same account, it would be a bit annoying if the XDA rebooted and activated the phone, when I was already using it in another phone.
It might be more effective to switch off the radio before rebooting, as the radio is initialised when you reboot. So if you tried to switch off the radio on reboot, it would start the radio, and then switch off the radio.
However, if you use mortscript or similar to reboot, you could make a script using VJVolubilis to disable the radio, use VJEschaton to reboot, and when you switch on again the radio should already be off (flight mode).
That sounds a bit strange - maybe I'm talking crazy...
V
Aha, didn't realize that the radio state was persistent after a reboot, thanks.
I have the opposite problem
After installing the 2.06 rom whenmy 8525 reboots it does so in flight mode? Any ideas on what may be causing this?
Can this be done? I tried switching on airplane mode, and then enabling Wifi/BT individually -- won't let me.
So, how do I turn off the cell radio, but turn on Wifi to take advantage in-flight wifi?
Also, when using local media, I'd like to sometimes turn off the cell radio to save power but listen with my BT headset.
I'm probably a total dufus and this is obvious, but I can't find it. This was easy to control on my WM Omnia II. I still like my Epic a bajillion times better, but this is a bit annoying.
Airplane mode cuts off all communications. Hence, "airplane mode"
There's some apps that'll let you do that, as well as Froyo when we get it officially, or if you want to run a leaked version.
Sent from my SPH-D700 using Tapatalk
Tasker will allow you to switch off the radio only. You would have to just set up a widget for that particular task.
In the leaked froyo, I had airplane mode on to test it and I put the wifi on byaccident and it was working with no cell signal, but I figured it was just a bug with it considering its beta and when ever I did tht before, airplane mode will cut off. I'm glad to know its a part of froyo now...that's going to come in handy
Sent from my SPH-D700 using XDA App
MrSickle said:
Tasker will allow you to switch off the radio only. You would have to just set up a widget for that particular task.
Click to expand...
Click to collapse
Genius! Thanx!
Forcystos said:
There's some apps that'll let you do that, as well as Froyo when we get it officially, or if you want to run a leaked version.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm running Android 2.2 and it isn't working for me -- once airplane mode is enabled, Wifi and BT will not turn on.
I would hope that in a future version of Android they will simply add the cell radio to the icons so it can be turned off like the others.
Can't you go to your settings, under wireless and networks, and disable 3g data?
Sent from my SPH-D700 using Tapatalk
Muckrak3r said:
Airplane mode cuts off all communications. Hence, "airplane mode"
Click to expand...
Click to collapse
Since they offer wifi on airplanes this is wrong
Sent from my SPH-D700
rangerover_95 said:
Can't you go to your settings, under wireless and networks, and disable 3g data?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
You can however it will still be looking for a cell signal to use for voice.
Exactly. I don't get reception in the building I work in, so I don't want it to drain the battery trying to find signal.
I'm running stock EC05 and I can turn wifi on in airplane mode (I can't speak for bluetooth though). GPS, however, does not work once you turn airplane mode on.
Sent from my SPH-D700 using Tapatalk
That's odd. I am running SFR 1.1.1 and if I turn on airplane mode and then push the Wifi icon, the text changes to "on" but the blue light never turns on -- it's as if it's trying to turn on but can't.
GPS works just fine -- it never switches off in the first place when I turn on airplane mode.
Nerva said:
GPS works just fine -- it never switches off in the first place when I turn on airplane mode.
Click to expand...
Click to collapse
That's because GPS is rx only. It doesn't need to tx to acquire a GPS lock.
Sent from my SPH-D700 using XDA App
Anyone know if Android 2.3 supports turning off just the cell radio?
Nerva said:
Anyone know if Android 2.3 supports turning off just the cell radio?
Click to expand...
Click to collapse
I've been trying to figure this out as well as I'm going out of the country and will be carrying my phone.
Only way I found to do it is:
1. In the dialer press###
2. Click view, and write down your MSID# and msn#, than go into edit
3. You will see your phone number and a box on the bottom that says touch here. Touch there.
4. Keypad should appear. Just press enter.
5. Another screen showing your MSID number should come up almost instantly. Press enter again.
6. Back out of this menu and your radio will be off (may turn off sooner, once it's off it's off)
Done
*MUST USE AREA CODE WHEN INPUTTING PHONE NUMBER*
now for the important part.
Turn your radio back on.
1.same as previous steps except instead of just pressing enter when the key pad comes up, input your phone number than press enter.
2. Input your msid number on the second screen and press enter
3. Click done on the main menu. Phone will reset.
Process honestly takes 30 second once you have your msl.
Edit: only issue I have is after the reboot when u turn your radio back on, the phone asks for your gmail password again.
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
machostallion said:
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
Click to expand...
Click to collapse
Mendanbar said:
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
Click to expand...
Click to collapse
I had the same problems you described back in December when I was running the beta off of the devs site. All seemed fixed when it got released to the play store.
Currently I'm running the CM stock kernel. I haven't made any mods, no theming, etc. It was a clean install with full wipes of everything twice. I flashed it with TWRP 2.3.3.
It is odd that the system clock could be behind the widget clocks. I've seen it the other way around where the widget would be behind the system if waking the phone after being in deep sleep a while. It's more strange that I can't open llama at all when I'm on mobile data now. It will only open when on Wifi. I do have quite a few Wifi dependent actions but since they work fine on the stock rom they should in theory work on CM. Maybe I'll keep testing and try to get a logcat to show something for the dev
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Update: Twice yesterday, I got missed texts and calls (saw them via google voice site on computer). I checked my phone and saw that it was in airplane mode with wifi off. This doesn't even make sense, since wifi is set to only turn off "upon leaving home"
ziddey said:
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Click to expand...
Click to collapse
I have been unable to duplicate the system clock glitch. I don't use llama for any alarms but I do have quite a few time based events to control volume levels and screen brightness. . After further testing, llama seems to do most of the set actions about 80% of the time. Sometimes it will be one of the actions in a string doesn't stick and sometimes it will miss a time based event. For some reason it has consistently missed the event at 11pm when it's supposed to put the phone into silent mode and lower the screen brightness. That time event is based on being in my "home" area, however, usually at that time my other events have been triggered which puts the phone in airplane mode with Wifi. Keeping Wifi on after triggering airplane mode also doesn't happen quite often. I know JB changed the permissions for apps accessing and modifying airplane mode but since I'm rooted and llama was changed to support it, it should work. I think there may be needs to be an option to add additional delays between multiple actions that are triggered by the same event.
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
lilfleck said:
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid :good::good:
I had CM11 on my Nexus 4 and did a full wipe, then flashed the official Lollipop image (using flash-all.sh script). The process went smooth, without any problems.
Now, I am having WiFi issues. When I turn on WiFi from quick settings it changes the icon, but doesn't connect to the network yet. If I try to access WiFi settings it opens them up, but I can see only the actionbar and a blank white screen. No networks shown. Sometimes I even get "The app is not responding dialog". It sits like this for about 30-60 seconds and after that it connects to the network and I am able to access WiFi settings.
Sometimes I can't turn WiFi on at all. Quick settings don't change the WiFi icon to the ON state. If I try to turn it on from the Settings, the switch does literally nothing - not even "Turning WiFi on..." shows up.
I tried to reflash the system - still get these issues. Tried reflashing just the radio module - didn't fix it. No idea what to do. KitKat worked just fine.
Does anyone else have similar problems?
Same issues, but on a Nexus 10.
I have exactly the same issues as you, but on a Nexus 10. Running LRX21P 5.0 Lollipop.
+1
I used Wugfresh 1.9.6
Downloaded and installed LRX21T
Did a complete wipe (cache and factory reset)
Did a selective restore of ~75 apps from Google backup
Played with the machine for hours.
Rebooted, now got no wifi
Anyone suggest a workaround?
EDIT: I came across this post in the Nexus 5 Thread , where he suggests changing your router's channel to something below 12. I changed mine from 13 to 8 and now wifi seems to be working.
EDIT2: Sadly the above was a red herring. The problem seems more complex. Hopefully Google will release a fix soon
fangthorn said:
+1
I used Wugfresh 1.9.6
Downloaded and installed LRX21T
Did a complete wipe (cache and factory reset)
Did a selective restore of ~75 apps from Google backup
Played with the machine for hours.
Rebooted, now got no wifi
Anyone suggest a workaround?
EDIT: I came across this post in the Nexus 5 Thread , where he suggests changing your router's channel to something below 12. I changed mine from 13 to 8 and now wifi seems to be working.
Click to expand...
Click to collapse
I don't think my problem depends on the available WiFi networks. But thanks for the response.
I have the exact same issues, Wifi doesn't turn on at all. It doesn't matter if I press the quick settings button or the button in the menu. It says Wifi on, but nothing happens. After the screen goes dark, Wifi turned itself off again.
Any suggestions? Thank you!
the.best77 said:
I have the exact same issues, Wifi doesn't turn on at all. It doesn't matter if I press the quick settings button or the button in the menu. It says Wifi on, but nothing happens. After the screen goes dark, Wifi turned itself off again.
Any suggestions? Thank you!
Click to expand...
Click to collapse
I'm having the exact same issue. Wiped with ADB and flashed LRX21T factory image from Google's website. No error codes during flash.
Wifi is great - if you leave it on all the time. As soon as it turns off, it will NOT turn on. I get no error message, no timeout like it usually does when Wifi isn't working properly, no crash report. Nothing. Just a stalled Wifi acting like it's turning on. If I exit Wifi settings page, and come back, it shows as being off. Turn it on, and it just hangs the same way.
So frustrating.
It's for sure not the network I'm on, as it also doesn't turn on when I'm not near Wifi, or when I'm at a friend's house. Rebooting the phones makes the Wifi work again...until it turns off for ANY reason. Then we're back at square 1.
I'm having this same issue...
My WiFi seems to turn itself off. Then there is no way I can get it to turn back on unless I reboot the phone.
Very frustrating.
I have the same issue.I sideloaded the OTA and everything went great,no errors during the installation.I was on stock 4.4.4.
When I turn on the Wifi it takes around 30 sec to connect to a network.If i click on the Wifi menu in the setting it usually freezes or I get a black screen.After that Wifi works fine,but another thing I noticed it doesn't remember new networks.I don't know if a factory reset would help...
Anyone find a solution yet? Did a factory reset eliminate the problem for somebody?
I got the same thing. Currently, I'm using Power Toggles to do the on/off setting.
NathanGong said:
I got the same thing. Currently, I'm using Power Toggles to do the on/off setting.
Click to expand...
Click to collapse
Are you saying that Power Toggles fix the problem?
I'm facing a different issue. Whether I have WiFi on or off, it always appears active in the battery usage stats ('scanning always available' is off)
WiFi was off when the screen was off from about 3 am to 2 pm.
Sent from my Nexus 4
I am having the same issue. very frustrating. it was working perfectly last night on my home network, but now it wont connect to my work network. it has the same issues as everyone else. the wifi toggle will turn on, but it will not show any networks. then after a couple of seconds it will turn itself off.
^^i am having that issue as well. the battery usage stat page is showing wifi as on even though it is off.
Have the same issue. After some standby time, turning Wifi on again, it showed me networks where I am not close to anymore and didn't show me the actual networks where I am right now. This seems to be a serious bug that needs fixing. I don't want to reboot my phone to fix it. Didn't Google delayed the Lollipop-Update because of some Wifi issues?
I have all the symptoms listed in this thread. I filed a bug report too: https://code.google.com/p/android/issues/detail?id=80028&q=LRX21T
Found this thread when this problem popped up for me after flashing the factory images one by one. Might try to find a source-built ROM using a later version to see if it got fixed.
quarara said:
I have all the symptoms listed in this thread. I filed a bug report too: https://code.google.com/p/android/issues/detail?id=80028&q=LRX21T
Click to expand...
Click to collapse
Thanks for making the bug report. I've added some details to it.
Ibrahim.Rahman said:
I'm facing a different issue. Whether I have WiFi on or off, it always appears active in the battery usage stats ('scanning always available' is off)
WiFi was off when the screen was off from about 3 am to 2 pm.
Sent from my Nexus 4
Click to expand...
Click to collapse
I have this problem too, in battery status wifi always show on even I turn on or off. It not happen with Kitkat.
anezarati said:
^^i am having that issue as well. the battery usage stat page is showing wifi as on even though it is off.
Click to expand...
Click to collapse
dinhvandinhtu said:
I have this problem too, in battery status wifi always show on even I turn on or off. It not happen with Kitkat.
Click to expand...
Click to collapse
Nice to know I'm not alone in this. Hope it gets fixed soon
Sent from my Nexus 4
I have a stock unrooted Verizon Galaxy S5. For several months my phone has been plagued by several issues at startup. Whether I reboot the phone or start it up after the battery has died, it always enters an odd state immediately after loading and seems to get stuck in this state for an undetermined and variable amount of time (anywhere from a few seconds or minutes to hours or even overnight).
While in this state, this is what happens:
1. Screen stays on. Once I unlock the phone, the screen stays on. The side button doesn't do anything to lock the phone or turn off the screen. Holding down the button, however, still triggers the power menu. The screen timeout never triggers, even though it should turn off the screen after 2 minutes of inactivity.
2. WiFi and Bluetooth turned off. Even if they were turned on before I powered down the phone, they are not enabled when the phone first boots up. I can manually turn them on but the WiFi will not connect to a network, even if one is available. It may show it is connecting to the network, but it gets stuck at "Checking the quality of your internet connection" and continues to use the 4G network for data connectivity. This happens no matter what WiFi network I am within range of, so it's not an issue with the network or router itself. If I am not near a network at all I will still experience the other problems of not being able to lock the phone, etc.
3. Startup applications don't load. I have Tasker on my phone, but it doesn't load and show it's notification bar icon.
Otherwise, I can use the phone normally and open applications, surf the web, etc. It seems that loading some applications and using the phone eventually causes the phone to exit this mode, but I haven't been able to find a single particular application or series of steps to fix the problem. If I power on the phone and don't use it that just seems to make it take even longer to fix itself.
Once it gets out of it's weird state, the WiFi connection will become active (it will turn on WiFi if I haven't done so manually already) and it will connect to a known network if one is available, the phone will lock itself or I can do so from the side button, and things like Tasker and Power Save mode will turn on.
I am stumped as to what could be causing this problem or how to fix it. It seems the phone may be doing some kind of check, maybe related to Knox, that hangs during startup and prevents certain things from working until it straightens itself out.
Any clues into what this problem is, what is causing it or how I could further analyze this problem and determine its cause would be greatly appreciated.
Never heard of or experienced these issues. May want to contact Samsung.
Have you installed any official updates from Verizon at any point? I've heard of phones having phantom problems like this after receiving a bad update. I would definitely contact Verizon if you did update at any point. If not then like BigBot96 said, contact Samsung about the problem.
My wife's Note 2 did something similar when the battery died. I had to factory reset. Her phone was rooted/unlocked & running a custom TW ROM, though. May I suggest doing a complete factory reset and Odin. Backup data to computer or external sdcard since this will clear the entire device.
Edit: After rereading OP's post it actually sounds like an app is hanging at startup which could cause this behavior. A logcat should tell you what's going on.
Sent from my SM-G900V using Tapatalk