Okay so I seem to be having a slight problem.
I've had my Nexus 4 for almost a week now I previously had my HTC dream and I would have an auto airplane mode toggle since the HTC dream didn't have that great of a battery life. So when I got my nexus I got juice defender + which has night schedules and an auto airplane mode toggle as well. It didn't work. First I thought maybe its a bug in the app. Did some digging around and saw someone had the same error and tried the suggested didn't work. I figured okay maybe I'll get the same app I had before for airplane mode toggle. And behold it didn't work either. So this is when I thought to myself I honestly don't know what it could be.
My battery life isn't bad its actually really good with around a day and half of battery and a good amount of screen usage. But honestly I don't use my phone at night and that auto toggle is useful since I don't wake up easily in the morning and I usually wake up for school because my girlfriend would call me to wake up. Several calls. Either way I know I can manually switch to airplane mode but I would really like that auto toggle since I won't get the calls since I'll be in airplane mode. Anyone have an idea what's up? I'm using CyanogenMod10.1 Nightly and I'm running 3.4.0 Franko Kernel Nightly.
I also installed AOSP helper manually since JD couldn't install it.
Sent using XDA app.
phones:
Google Nexus 4
- CM10.1-Nightly - FrankoKernel3.4.0-Nightly
HTC Dream
FroyoSense Rom
Related
Ever since I got Cyanogenmod 7 working on my phone, I've had a lot of trouble getting my 3g to toggle back on after turning my screen on. I'm using JD for the toggle so is it a Juice Defender problem or a modem problem?
Sent from my SCH-I500 using XDA App
I have the same problem, I just switch to airplane mode and back and it fixes it. It only happens periodically, it works as it should more often then not. I attribute it to CM7 awesomeness. At least JD works, Green Power won't even try to manage the data connection.
Ah I wouldn't have thought to try that. Yeah I love this rom compared to stock so I'm more than willing to put up with a few gripes.
Sent from my SCH-I500 using XDA App
TheChillburger said:
Ever since I got Cyanogenmod 7 working on my phone, I've had a lot of trouble getting my 3g to toggle back on after turning my screen on. I'm using JD for the toggle so is it a Juice Defender problem or a modem problem?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I have this same problem and run JD but it's not a JD problem. I would say it happens to me once or twice a day(usually when the phone is powered on for more than 6 hours without a reboot). A lot of people have this and toggling back and forth between airplane mode fixed the problem pretty damn easily.
If you want a quick way to do this go to
settings
cyanogenmod settings
interface
notification power widget
widget buttons
select airplane mode
Now you have airplane mode in your pull down bar and you can quickly enable it and disable it when this happens.
I have two problems relating to this. My 3g wont turn on automatically when someone sends me an MMS. Usually my stock ROM would turn the 3g on and download the MMS, but now I just receive a text message from a number rather than the name of the contact, and I need to press a Download button to download the picture/MMS. Then I have to turn on my 3G manually, then I have to press the Download button, and only then do I receive the picture/MMS.
Also, It has been happening quite often now. My 3G does not turn on, even when I turn it on manually so I have to reboot my phone an only then will it turn on.
Im using CM7 nightly, latest one up to date on HTC Desire HD.
Hope someone fixes this!
Hi Guys,
I work at location just outside of signal reception, therefore while I'm at work for 12 hours my phone hunts for reception and uses more power than it should.
I'm looking for a time based profile app that I can set and it will switch to flight mode at a certain time and then switch off flight mode at a predefined time and maybe even use it at night while in bed sleeping.
Anyone have any recommendations for the best one to go with?
Sorry if this is in the wrong forum, if it is you can all take an open shot at me.
Cheers
I'm actually really interested in an app like that too, most of my classes are in the basement of my school and it's kind of a pain to switch into airplane mode everytime I go to one of the said classes, and if I forget my phone easily eats through 20% of my battery...
Sent from my SGH-I997 using XDA App
This is the closest I have found:
https://market.android.com/details?id=be1ay.flymode&feature=related_apps
but maybe the ability to set more than one profile would be good so you don't have to go in and change the settings, plus one that boots with the phone?
Seems many having various wifi issues and also seems not a lot of fixes. So here goes.
Running EOS JB, and Morfic kernal. I want the wifi to shut down when ever I close my case / or when the screen goes blank (i.e. sleep). I'm sure there a various levels of sleep, but read on:
Setting in advanced to shut wifi down when sleeping, it does. BUT, it wakes up every few minutes. This has to kill the battery. I've turned off every updating I can find but that does not help. When it is asleep, it should stay asleep!
I installed Llama - I use this on my Maxx with perfection. I set the advanced settings wifi to stay on always - then set up Llama to turn it off when screen goes blank, and then back on again when screen comes on. Works perfectly! No through the night updates. BUT - when I'm USING the device, I'll lose wifi completely for no apparent reason!!! I look at Llama event log, no entries there. It is just shutting off. I have to cycle the toggle off then on again for it to restart.
So I removed Llama - it's back to "working" but still updating constantly.
Any one have any ideas on how to control this beast?
Can llama put your tab in airplane mode instead of switching WiFi off? Might be worth a try if so. I use tasker to do a very similar thing...puts tab in airplane mode 2 mins after screen off and cancels it on screen unlock.
Sent from my Nexus 7 using Tapatalk 2
froggy666uk said:
Can llama put your tab in airplane mode instead of switching WiFi off? Might be worth a try if so. I use tasker to do a very similar thing...puts tab in airplane mode 2 mins after screen off and cancels it on screen unlock.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
that is another option I hadn't thought of. I've gone into advanced settings and told the wifi to stay on ALWAYS - and I'm using Llama/screen to see if works. So far so good. The problem I'm trying to solve now it seems, is keeping it on when awake. I like the airplane option an an alternative. I'll update as I go along here.
Thank you!
Kind of hard to explain what I want, but when I'm outside using my phone, and then come inside the house I want to keep the wifi on, but turn off the cell antenna to save battery (I find with just wifi on, the battery lasts a long time). I know I can do this by checking airplane mode, but then that turns off wifi, and I have to re-enable wifi, sort of a 3-4 key stroke that I'm wondering if I can do in one?
I've tried power toggles, but couldn't see the option for what I want to do with it.
You could use an app like Tasker, or Automateit (<---has free and paid version). You could have it execute a task when you enable AP mode that turns wifi back on. You can get pretty creative with the tasks as well. I haven't set it back up on my N4, but on my previous phone my need to enable/disable anything was nearly eliminated.
Thanks CMNein, I'll have a look at Tasker.
NFC tags.... I use Samsung Tectiles
You can Program a tag to go into airplane mode and turn wifi on
Sent from my Nexus 7 using Tapatalk 2
See if Plane Mode Tweaker works for the Nexus 4. https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.airplanemodetweak
It allows you to configure airplane mode so it won't disable wifi automatically. Also allows you to use bluetooth in airplane mode if it's locked.
I've read that apps to control airplane mode don't work, at least with the stock firmware.
http://forum.xda-developers.com/showthread.php?p=29219003
I'm still using an HTC Sensation, but I've got a battery of apps to automate turning airplane mode and wifi on when at home, and back off when away.
ziddey said:
See if Plane Mode Tweaker works for the Nexus 4. https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.airplanemodetweak
It allows you to configure airplane mode so it won't disable wifi automatically. Also allows you to use bluetooth in airplane mode if it's locked.
I've read that apps to control airplane mode don't work, at least with the stock firmware.
http://forum.xda-developers.com/showthread.php?p=29219003
I'm still using an HTC Sensation, but I've got a battery of apps to automate turning airplane mode and wifi on when at home, and back off when away.
Click to expand...
Click to collapse
Maybe time for you to join the N4 club.
https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5nbXN0eWxlcy5hdXRvd2lmaSJd
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: