There has been quite a bit of discussion about Fast Dormancy, so I thought I would try to investigate it, and to explain things a little.
I don't claim to be an expert on this. Far from it. I'm merely putting across what I have found out about the subject, and what my observations have been on the it.
Firstly a little explanation on what FD actually is.
When your phone is connected via 3G data (not 2G or wifi) your phone needs to enter certain states in order to maintain this connection and allow data transfer. If your Operator does not have FD support or you have it disabled, then basically your states are just connected or not connected. What this means is that every time your phone connects to data, it will have to go through all of its various stages and internal functions in order to make the connection and then perform the actual data transfer. This is slow and obviously the more processing that is required, the slower your experience will be, and the greater the affect will be on your battery.
FD tries to tackle this problem by having several different states so that the full connection/disconnection cycle is not required every time. Each state has a different level of data throughput and power consumption.
DCH - High volume data (highest power consumption)
FACH - Lower volume
PCH - No data but keeps connection
IDLE_CCCH - Not entirely sure about this one but I think its an interim, lower level stage between PCH and:
IDLE - Connection dropped (lowest power consumption)
When in DCH state, your phone is doing the highest volume of data transfer, and obviously consuming most power out of your battery.
The way FD works is when transfer rates drop, the state drops to FACH for less power consumption and then back up immediately to DCH as and when required, or if this transfer state is over for the time being, (eg. you have stopped browsing) instead of going back to IDLE which would mean going through all the connection procedures next time data is required, the state drops down to PCH. This is a very low powered state, and when data is subsequently required, it can then immediately go back up to FACH or DCH with minimal effort. The less stages that is required to get the connection back up and running the better, both in terms of battery and speed.
To turn FD on/off enter *#9900# in the dialler to get into the SysDump screen then select the Fast Dormancy option
Alternatively, gokhanmoral has an app called FastDormancy Toggle for i9300 which can also do the job. I've not tried this app personally, but I've been told it works fine on the i9100.
Whether you keep FD on or not depends primarily on if your network operator supports it.
If your network operator supports it, then enabling it is not necessarily the best answer, as it can depend on the combination of the following things:
1. How you use your phone - Are you a heavy or light data user?
If you are a heavy data user then enabling FD is almost certainly the way to go. The less the phone needs to do in order to fire the connection back up, the better. However, if you rarely use the phone for a data connection, then it may prove beneficial to you to switch it off so that the IDLE state is entered sooner. Bear in mind before you decide on if you should turn it on or off, consider what your data sync options for contacts/calendar/email etc. are. If you dont browse too often, you may still be using data in the background quite often even though you are not physically doing so through various background syncs.
2. How "intelligent" your Operator's FD actually is.
I believe the operator defines the parameters for the timings of these different FD states, so results can vary drastically between different networks. To see how your carrier handles FD can be done via a simple test on a Samung ROM. With wifi off and FD enabled, at the dialler, type *#0011#. This takes you into the ServiceMode menu. The important piece of information here is the RRC State line. Press the home button and open a browser session and go into a web site, then immediately long press the home to get the list of tasks and select the ServiceMode app. The RRC State line should be DCH (or at least FACH) and you should see some activity in your signal indicator arrows on the status bar. Eventually you should see it drop down from DCH -> FACH -> PCH -> IDLE (sometimes you may see IDLE_CCCH). Ideally, the state should stay at PCH for a while, then eventually drop to idle.
My findings so far on JB is that FD seems to be handled differently to the way it was on ICS. In fact, I'm not entirely sure its working on JB at all! For me, it seems to go from DCH -> FACH, and shortly after that (perhaps up to 5 seconds) drops to IDLE. This is not great if your going to be using more data shortly, but ok if you are no longer browsing.
After further testing, it seems on JB it make no difference if FD is enabled or disabled in the ServiceMenu.
The transitional RCC states it enters seem identical regardless of the FD option you have set.
My testing when on ICS suggested that when going from DCH eventually down to IDLE, the handset seemed to go to FACH for a short period, then sit on PCH for sometimes up to 10 minutes. This has a big advantage if you are about to do more browsing shortly, is it will take much less power to resume the connection and enable the data transfer to begin more quickly, but has the drawback of if you have indeed ended your browsing for the time being, it would be using more power compared to if it was in IDLE. So swings and roundabouts.
Perhaps my observations on ICS (ie, remaining on PCH for up to 10 minutes) is how FD should behave.
Remember FD only applies to a data connection. It does not kick in whatsoever when you are connected to wifi or on 2G.
The quality of your data connection (ie. H+, H, 3G) may also have a bearing on how FD will perform. Better connectivity should give you a more efficient FD performance.
Tip 1.
If your wifi sleep policy is set to "keep wifi on during sleep only when plugged in" then this will mean your data will take a hit whenever your screen is off (unless plugged in of course) If you think FD is not for you because "I'm almost always connected to wifi" (ie. at home/work) then you will still need to consider what the best FD policy is for you when on this sleep policy, as obviously, your screen is off most of the day.
Tip 2.
If you are not connected to wifi overnight (either your not at within your router's range, or you have set your wifi sleep policy not to be connected) bear in mind what your phone does overnight in terms of background data activity (ie. your data sync options and widgets such as news/weather etc). If you have minimal data activity overnight (you set your widgets to sleep for example), then it would be better to switch FD off, as less battery would be consumed to go straight back to IDLE than hang around for possibly 10 minutes or more each time in FACH.
Note
You may well have a higher l2_hsic wakelock when FD is disabled, but when FD is enabled you may find this drops slightly, only to find another one called secril_fd-interface kick in instead, so again, swings and roundabouts.
I did extensive testing on this on ICS, and came to the conclusion that was better FOR ME to turn FD off, but the differences were not drastic. It can however make huge differences for others, depending on your Operator and your usage habits.
On JB, I've found it better to keep wifi on constantly, and keep FD enabled.
It would be interesting to compare how your firmware/carrier handles FD.
Bottom line is, try it and see what works best for you.
Note:
I don't think the *# service codes work on CM/AOKP based ROMs but you can certainly give them a try!
If the codes do not work on your Samsung ROM then you will need to install FactoryTest.apk.
Thanks for sharing! :thumbup:
I hear many members asking 'why' when asked to disable it..
"To err is human, to forgive is divine"
Sent from my SGS II
Great work I have been reading up on this lately. Nice to know that in JB it seems almost irrelevant... That's what all my unofficial tweaking/testing was indicating. I thought I must be doing something wrong.
Quick question though, do you know of any ways to turn off Fast Dormancy in 4.2.2 ROMs? I haven't found a way. Using gokhanmoral's app still results in a secril_fd_interface wakelock in BBS.
Related
Download. Simply decompress it and copy it on your Windows Mobile 6 device and run it. (Works on my Polaris.)
Details
Source code
Description
Use your PDA to acquire your GPS position and send it through an SMS.
The GPS position is update every 5 seconds (in order to conserve energy).
SMSs can be sent automatically at regular time intervals.
Do you like hiking?
What if you go out in the wilderness and have an accident? How do you direct a rescue team to your location?
You can use Astrolabe on your PDA to acquire your GPS position and send it through an SMS to your friends / parents / children / rescue team.
Privacy
SMSs are not encrypted, so anyone who tracks your phone number can tell your precise position by reading the SMSs with your GPS position.
However, it's debatable whether this is relevant because if someone tracks your phone number, they may already know the position of your phone in the communication grid.
Power saving modes explained
The following power saving modes are available: none, manual, auto.
None
In this mode there is no power saving. The application and the GPS are running even if the PDA is in standby.
GPS positions are retrieved as soon as they are available and are automatically sent through SMSs as soon as it is mandated.
Warning: In this mode, the battery is drained quickly (because keeping the GPS active requires a lot of power). Therefore, the "Auto" power saving mode is active by default.
Use this mode only when GPS position availability is critical.
Manual
In this mode the power consumption is the same as if the application (including the GPS) is not running.
However, you must keep your PDA on in order for GPS positions to be retrieved and automatically sent through SMSs.
Use this mode only when power consumption must be at minimum.
Auto
In this mode the application is running all the time, but the GPS is sleeping most of the time.
Once every 30 minutes, the GPS is awoken for maximum 5 minutes in order to get a GPS position and automatically send it through SMS. When a GPS position is available, this timer is reset.
In this mode, since the PDA sleeps most of the time, it may miss the narrowest chance it may have to get a GPS signal. In order to be sure that GPS positions are retrieved and automatically sent through SMSs, you must keep your PDA on.
Warning: Do not rely on the ability of a PDA in standby mode to automatically acquire a GPS position in (maximum) 5 minutes. Check this yourself!
Use this mode in most cases.
Tests showed that in this mode the battery (of a HTC Polaris, 1350 mAh) would be depleted in about 16 hours, if no GPS signal is available; if there is a GPS signal, the autonomy should be greatly increased (an informal test indicates more than twice the autonomy). Without power saving, the battery would be depleted in about 6 hours.
Do you like hiking?
What if you go out in the wilderness and have an accident? How do you direct a rescue team to your location?
Click to expand...
Click to collapse
what if there isent any signal?
(joking..)
Nice app btw
If there is no signal, the program waits until it acquires a new GPS position. Then, a new SMS is sent within (generally) 5 seconds.
(Of course, if the repeat time is X, the SMS is sent only if more time than X has passed since the last sent SMS.)
Note: Keeping the GPS active drains the battery quickly.
6ITdtvFQqY said:
If there is no signal, the program waits until it acquires a new GPS position. Then, a new SMS is sent within (generally) 5 seconds.
(Of course, if the repeat time is X, the SMS is sent only if more time than X has passed since the last sent SMS.)
Note: Keeping the GPS active drains the battery quickly.
Click to expand...
Click to collapse
I hace seen many programs like yours, almost all drains battery when there is no GPS signal (inside buildings). Only one programs deals it better, but that has many other issues. One way to stop draining the battery is to read 'N' (say 50) number of NMEA messages from GPS and then turn off GPS for about 'M' (5 - 15) minutes. Then try again. This will save lot of battery. May be you can try implementing it.
You can download a new version which has 2 new features.
You can see the trail of GPS locations where you were. The trail is updated once per minute.
A power save mode is available. If this mode is active, the PDA's power consumption is the same as if the application is not running; however, you must have your PDA on in order for GPS locations to be retrieved and automatically sent through SMSs.
Warning: Keeping the GPS active drains the battery quickly. Therefore, the power save mode is active by default.
Download
Details.
tahdor said:
I hace seen many programs like yours, almost all drains battery when there is no GPS signal (inside buildings). Only one programs deals it better, but that has many other issues. One way to stop draining the battery is to read 'N' (say 50) number of NMEA messages from GPS and then turn off GPS for about 'M' (5 - 15) minutes. Then try again. This will save lot of battery. May be you can try implementing it.
Click to expand...
Click to collapse
As you can see, I've implemented a manual power save mode.
In theory, an automated power save mode can be implemented, where the GPS is woke up every 30 minutes to get a location and then sent back to sleep. However, I have no idea what that would do to the device, that is, waking it up every half hour and then shutting it down.
But most importantly, if a GPS location can't be retrieved, what would the device do? The user could be sleeping in a motel for the night (or move through caves or canyons) and the walls could block the GPS signal. Should the device keep trying and thusly consume energy (for how long?), or go back to sleep and miss even the smallest chance of getting a GPS location in those 30 minutes?
An automated power save mode is in conflict with the criticality of having a GPS location any time it is available. Of course, if the device has no power this becomes irrelevant, so a power save mode is necessary. But it's important for the user to understand what's going on.
The current manual mode allows the user to understand that and allows the settings (especially the trail) to remain active all the time. For the moment I consider this to be the best solution.
Accelerometer
Hi,
Your program i very interesting, it will be great to manage the accelerometer
and send a SMS when the phone do not move or when it goes from vertical to
horizontal position.
What do you think of that?
Regards
doco76 said:
send a SMS when the phone do not move or when it goes from vertical to horizontal position.
Click to expand...
Click to collapse
In what context would someone use such a feature? I mean, what does an accelerometer provide that the GPS's altitude does not?
I guess an SMS could be sent as soon as a significant change in altitude occurs (because this could indicate a fall).
Very good idea, thank you
I know you're still developing this program,
Can you add customizable SMS feature? I might need to send an sms in my native language.
And
The program will send SMS automaticaly to Predefined Numbers feature would be great
May it be easy
I know you're still developing this program
Click to expand...
Click to collapse
The development is actually frozen. I am just implementing critical stuff, like power saving, and doing bug fixing.
Can you add customizable SMS feature? I might need to send an sms in my native language.
Click to expand...
Click to collapse
You can simply send a normal SMS. I'll add a "copy GPS position to clipboard" feature to go with that.
The program will send SMS automaticaly to Predefined Numbers feature would be great
Click to expand...
Click to collapse
SMSs are sent to a predefined agenda contact. Someone who wants to send SMSs with his GPS location should normally do so to a regular agenda contact, so he'll already have an agenda contact or can setup one anytime. What particular usage would there be for an SMS sent to a phone number instead of an agenda contact?
I'll have a new version by tomorrow (if tests are okay) with multiple power saving modes: none, manual (as is now), automatic (where the GPS is automatically woken up to get a location - 5 every 30 minutes). I'll include the "copy GPS position to clipboard" in there.
In automatic power saving mode, tests showed that the battery (of my Polaris, 1350 mAh) would be depleted in about 16 hours (if no GPS signal is available; if it is and reception is good, the autonomy should be greatly increased). Without power saving, the battery would be depleted in about 6 hours.
Although the new version is already up, I'll make a small change later today.
Version 1.3.1 is up. See the first post.
I am going for a hike up the cobbler and Ben Ime in the Arrochar Alps on friday so i will take my polaris and see how things go.
Well that hike went well and i have taken my polaris on a few other hikes.
To be honest you have almost developed a GPS application for your phone. The sms ability is great, but what i really liked was the trail plotting ability.
A standalone GPS will provide you with a line route against gradient maps. I don't expect there to be gradient maps but just a route line sampled at regular intervals would be great. It would be a good aid to plotting your route with a paper map.
Can i ask if the trail samples can be increased?
The current default power saving mode is "Auto", which means that Astrolabe can only take a GPS location once every 30 minutes. As such, the trail can't be updated more often. Moreover, if the 5 minutes window when Astrolabe attempts to get a GPS location is missed (because the GPS reception is poor), the next one is 30 minutes later, which mean that the trail accuracy is getting worse.
You can change the power saving mode is "None", in which case the trail is updated once per minute... but the battery dies out fast.
Instead of changing the power saving mode, you could manually start your PDA every time you think it's necessary to get a GPS location (and trail location). (Just look in Astrolabe to make sure that the time of the last GPS location is the current time.)
(As I said, the power saving modes will cause confusion.)
I added the trail feature after a bunch of us got lost in the woods. After some 2 hours of being off course we were debating whether to return or go further. Fortunately someone went 200 meters further and saw the road (from where we started). With this feature I could have seen that we were going in the right direction.
It's my understanding that the wifi on this phone has a very low power usage when inactive in standby. I'm going to guess, however, that the power usage goes up when it "wakes up" to scan for open and/or configured AP's. I'd also guess that it'd have to take the phone processor out of "sleep" and wakelock in order to perform that function
I'm wondering how often android (or this phone's default ROM in particular) will wake up to perform a scan of access points when it's NOT currently connected (but the wifi radio is left on at all times), and configured to only connected to known AP's.
Anyone?
Thanks
Gary
I've been using the app BetterBatteryStats as recommended by XDA to determine why my RAZR is awake much of the time, even when the screen is off and data is turned off. It turns out the problem is the internal process IMS_Data_Retry. This process apparently keeps attempting to establish a data connection over cellular data, at least 4G LTE. It aquires a wake lock while doing its work. This one process can keep the phone awake 95% of the time. The only way I have found to semi-stop it is to turn on 4G LTE. Even then, while it stops consuming CPU time (supposedly), the count of retry attempts keeps going up. (Putting the phone in Airplane mode also stops it, but then calls are stopped as well.)
There is a setting in /system/build.prop that I thought controlled this process:
ro.cdma.data_retry_config=default_randomization=2000,max_retries=infinite, 0, 0, 120000, 180000, 540000, 960000
I looked at some code references I found ( http://hi-android.info/src/com/android/internal/telephony/cdma/CdmaDataConnectionTracker.java.html ) and learned that the above values are in milliseconds. It seems that the default_randomization value is added to the other values in the list to create a schedule of retry attempts, but I wasn't able to figure out all the parameters to the method, if I even have the right one. I tried changing "infinite" to a small number under 10, but it had no effect - the process just keeps retrying forever.
Is there a dev out there who knows more about this? I want to limit this process because I seldom use cellular data right now and am usually on WiFi. It hinders any attempt to extend battery life. Is it a bug? Is it fixed in a later release (I'm on .748 stock) ? Do any of the custom ROMs have this problem? Can the build.prop setting I found be given values that limit the amount of time this process holds wake locks?
Thanks.
Did you ever get any resolution on this? For me, I think the problem started with the ICS update this summer. I constantly have gsm_data_tracker, RILJ, and IMS_Data_Retry using up the battery (in that order from highest to lowest). I tried wiping cache which helped the 1st time it cropped up and then it came back. I also tried a tip I saw somewhere for turning on airplane mode, rebooting, and turning off airplane mode (though mine as soon as it reboots, it already turns off airplane mode which it shouldn't). That worked for several weeks, but I had to do it EVERY DAY when I got to work. I think it's something with the 3g repeaters in the building. I did have it so it was wifi only (mobile radio off) on my work profile in profile scheduler, but then I needed cell for some mms stuff, so I ended up enabling it again. Basically when I come in the building and forget about my phone for an hour or 2, I go to get it out of my backpack and it will be hot from processing and 20% or more of the battery gone when I've done nothing in 2 hours of being at work. I saw somewhere that someone though either gsm_data_tracker or RILJ was related to something with the alarm, which I do use my phone as my alarm, but I use a 3rd party app. With the time change, there were a few days I woke up before it ever went off, so I turned it off before it did alarm. There were no differences with the partial wakelocks or battery drain in those cases. Unfortunately, I don't have another alarm readily available to get up for work right now and on the weekends when I don't need an alarm, I can't replicate the cell repeater at work issues, since I wouldn't be around the cell repeaters. As fart as in the building at work, until I reboot with airplane mode and all of that, the cell signal will bounce between like 0 bars/3g and lots of bars (no indication of network) and some bars with 1x network. It's all over the place. The airplane mode/reboot used to stabilize that, but it doesn't seem to be doing the trick anymore the last few days that I've tried that. I have to leave my phone on the charger as much as possible at work so that I don't leave for the day with a dead phone.
I have a Star A3 running 2.3.4
The question is more of a general question to the android platform, I don't suspect the hardware matters.
I am running Ttorrent Pro on the phone, and the speeds are less than impressive (everyone else says the same thing) I am on a very fast connection, using speed guide I literally max out the speedtest servers in my local area (20Mb up/down which is the max they let you go to, I would get 100/100 if my speedtest server would allow it) and I have a port forwarded correctly.
but anyways, what I have noticed is, when wake the phone, and open the torrent application the speeds are down to around 3Kbps if I leave it open the speeds immediately start ramping up to 200-300Kbps if I keep it awake.
So this makes me think, when the phone is sleeping a lot of the connections are being closed, or when the phone is asleep it won't try and open new connections to new peers (and the current peer list may go stale while its asleep)
this is with all torrents, now the exact same torrent on another PC with a DSL connection (3Mb down 300Kb up) is downloading faster than the phone.
Are there any developers out there than can explain what processes are going to sleep that may be useful to keep awake for downloading, and also what are the tcp limits on the phone, ie. max open connections, max half open etc?
When the phone clocks down its CPU, of course it'll make your apps run slower. Is that so strange? Leaving it connected to the power seems to keep the CPU at high speed on my devices at least, but I guess that may vary from phone to phone.
A torrent client have a quite intelligent algorithm choosing the numbers of peers it connects to depending on several parameter such as effective bandwidth and so, and if your device lower its CPU frequency, the bandwidth will suffer.
There's also another possibility. Running the task in the background, i.e. without its main window visible, and Android may kill the app. More than 15 hidden apps (e.g. background running), and Android begin to kill the oldest. This is quite invisible to you, because Android must restart them as well. The problem with a torrent app, is that setting up the torrent, connecting to pears etc takes a while, and if the app gets killed and restarted once up running, you'll never achieve great speed. If this is the case, leaving the main activity visible prevents Android killing/restarting it.
I just wanted to post on the XDA forums that there is a thread to help determine what is causing the "heat + battery drain" issue(s) on the Lumia 920.
http://discussions.nokia.com/t5/Nok...n-ATT-Overheats-Battery-Draining/td-p/1606012
Specifically, we've seen fairly normal battery drain when using applications, but when LTE data is introduced the battery continues to drain at a rate of 7-8% per hour even after the applications are closed. For example, streaming something like Xbox Music or Netflix over the LTE connection (wifi OFF), the phone warms up considerably and the battery continues to drain at a high rate even after those applications are closed. The same applications behave normally over 3G or Wifi, and the battery drain is not present afterward.
The "fix" so far appears to be disabling LTE altogether.
• Open Dialer
• Punch in ##3282 and hit Call
• At the Field Test menu, choose more options via the three dots (lower right)
• Select Settings
• Under network type, select "3G only". UMTS should be set to "Automatic".
• Change the "Toggle ENS" setting to OFF
• Back out, power off the phone, and power on again
Definitely interested in hearing other's reports on this issue. Specifically, does this happen with ALL Lumia 920 phones? Is this specific to this particular model phone? Is this a Nokia issue, LTE chip issue, or WP8 issue? Was this introduced with the Portico update?
Thanks.
Upon further testing.........
Disabling LTE is *not* the ultimate fix. Yes, it does help keep the battery drain down to more reasonable levels, but it does not solve the problem. I've subsequently tested with the little brother phone -- the Lumia 820 -- to see if the issue is on all WP8 handsets, on all Lumia phones, or even limited to post-Portico update phones (in other words, did Portico make this issue).
After some thorough testing, I can say with confidence that this issue is specific to the Lumia 920 and not necessarily all WP8 handsets or Lumia phones.
Detailed thread here: http://discussions.nokia.com/t5/Nok...Overheats-Battery-Draining/m-p/1795212#M43837
I am currently working with Nokia to find a long-term resolution to this issue.
Please keep us updated, I'm very interested in knowing how to fix this problem! ??
I found that disabling bluetooth helps out.
Battery drain
To help reduce battery drain I do the following on my WP
I get a connectivity shortcut app. There are a few options available in the store. Anyway I pin airplane mode, Bluetooth, Wi-Fi, and Location on my home screen and turn them off when I'm not using them. Turning off location turns of GPS, so you must enable it before launching Drive/Here. A lot of battery issues I think have to do with the phone being to aggressive (power wise) trying to search for signal. Whether its Wi-Fi a Bluetooth device, etc. I also disable Tap+Send (NFC) because I never use it.
And I go into background tasks and I block every single app from running in the background except the ones I am sure I want to run. Remeber the list where you can block them is for apps that want to run on a timed schedule, they can still run in the BG if you home screen out of them. For me the only one I allow is MS Weather (for the live tile). Disabling Nokia Drive/Here seems to help battery life for some people.
The biggest battery saver I did was forwarding my other email accounts (Gmail & Yahoo!) to Outlook.com, and then set that to only look every 1 hour (instead of the stock 30 minutes). My phone went from lasting 1 - 1.5 days to over 2.5 - 3 days with my typical usage (light usage).
I try not to use Live Tiles, or lock screen pictures unless I really want them (like weather for instance), as they help drain the battery quicker.
Anyway Nokia is really on top of their game so I think they will help contribute to WP to eliminate these issues. The only non-software related issue with the 920 is the dust in the FFC, which personally does not bother me but I could see how it might bother others.
##3282 isn't working for me after yesterday's update. Lets see how I do with the battery today!!!
The earpiece on mine does not work I can't hear anyone and top of phone gets warm I have sent it to nokia repair.
yipcanjo said:
I just wanted to post on the XDA forums that there is a thread to help determine what is causing the "heat + battery drain" issue(s) on the Lumia 920.
http://discussions.nokia.com/t5/Nok...n-ATT-Overheats-Battery-Draining/td-p/1606012
Specifically, we've seen fairly normal battery drain when using applications, but when LTE data is introduced the battery continues to drain at a rate of 7-8% per hour even after the applications are closed. For example, streaming something like Xbox Music or Netflix over the LTE connection (wifi OFF), the phone warms up considerably and the battery continues to drain at a high rate even after those applications are closed. The same applications behave normally over 3G or Wifi, and the battery drain is not present afterward.
The "fix" so far appears to be disabling LTE altogether.
• Open Dialer
• Punch in ##3282 and hit Call
• At the Field Test menu, choose more options via the three dots (lower right)
• Select Settings
• Under network type, select "3G only". UMTS should be set to "Automatic".
• Change the "Toggle ENS" setting to OFF
• Back out, power off the phone, and power on again
Definitely interested in hearing other's reports on this issue. Specifically, does this happen with ALL Lumia 920 phones? Is this specific to this particular model phone? Is this a Nokia issue, LTE chip issue, or WP8 issue? Was this introduced with the Portico update?
Thanks.
Click to expand...
Click to collapse
Thanks for the tip!
I also have 5-8% per hour drain. (actual offi. release .1308...)
all off, sync, loaction, WLAN every thing, fresh reboot, phone on my desk, not working with it, about 2 lines H signal.
when i switch to airplane mode....1-2% battery drain over a complete night!
its also no problem to activate airplane mode ON and afterwards WLAN additionally ON, then about 1-4% over a night!
i tried everything i found on the inet.
and i have my white L920 since Dec.12! (i did a "hard" update over PC in Feb. and also the the last release over the air...nothing changed)
so now i'm checking if this works for me and post results
I'm located in AUT with an unlocked, unbranded GER L920.
and we dont have LTE til now...maybee thats the problem..?!
dj_memory said:
Thanks for the tip!
I also have 5-8% per hour drain. (actual offi. release .1308...)
all off, sync, loaction, WLAN every thing, fresh reboot, phone on my desk, not working with it, about 2 lines H signal.
when i switch to airplane mode....1-2% battery drain over a complete night!
its also no problem to activate airplane mode ON and afterwards WLAN additionally ON, then about 1-4% over a night!
i tried everything i found on the inet.
and i have my white L920 since Dec.12! (i did a "hard" update over PC in Feb. and also the the last release over the air...nothing changed)
so now i'm checking if this works for me and post results
I'm located in AUT with an unlocked, unbranded GER L920.
and we dont have LTE til now...maybee thats the problem..?!
Click to expand...
Click to collapse
UPDATE:
i solved my battery drain issue by setting my "max network speed" to 2G!
by that i now have a drain of 1-2% p.h.!
dj_memory said:
UPDATE:
i solved my battery drain issue by setting my "max network speed" to 2G!
by that i now have a drain of 1-2% p.h.!
Click to expand...
Click to collapse
That is great. To bad that we whom have received the latest OTA no longer have access to that menu.
really?
I'm on FW 1232.5957.1308.0001
and WPH 8.0.10211.204
I don't need to change the network type within ##3282 menu, also worked for me in normal network settings.
dj_memory said:
really?
I'm on FW 1232.5957.1308.0001
and WPH 8.0.10211.204
I don't need to change the network type within ##3282 menu, also worked for me in normal network settings.
Click to expand...
Click to collapse
So then how do you set your network speed?
u don't need access to ##3282...its also possible to "limit" within settings/network. (##3282 NOT working within f.e. Rapdialer!!)
I limit it to "2G" only when its more importand to have less battery consumption than inet speed
limited to "2G" in my region it shows me afterwards a "E" on top.
On this PIC i found in the inet is "roaming" deactivated.
I have to activate "roaming" also when I'm within my own network to have inet access (and the "E").
In my town, network operators share their mobile radio transmitters.
I limited direktly at my provider the access to a "real roaming network" for example a swiss network.
Because i'm most of the time near the border
maybee not possible in your version or provider?
I'm on a free GER version.
Definitely trying this tonight.
For the battery drain try light (white) theme. intresting but that help my battery drain problem
Same issue here...Any updates?
Battery drain and over heat
moshepupkin said:
Same issue here...Any updates?
Click to expand...
Click to collapse
My experience is that, I reset the cellphone and after doing this twice and connecting to the internet and waiting for one hour, Microsoft gave me an update for my battery saver and since that time everything is ok, including the battery. I always believed that the updates have problems to be installed completely most of the time, so it's better to reset or download it via the computer and instal it with a cable( using Nokia Software Update). But if it doesn't work, please don't panic. The updates are coming and just be sure that you have reset your device without choosing the setting backup, for you must start afresh. Good Luck.