- 1 Adding your carrier apn settings
- 2 Fast dormancy – the whole story — xda developer tv
- 3 Fast dormancy in release-8
- 4 Finding out your mobile carrier’s plmn number
- 5 Let’s talk about fast dormancy
- 6 Modifying the network info
- 7 Now on to the guide itself!
- 8 Puzzling out the fast dormancy problem
- 9 Setting the dormancy policy (dormpolicy)
- 10 Setting the network info (nwkinfo)
- 11 What is fast dormancy?
- 12 Why on earth would i want to disable it then?
Adding your carrier apn settings
I think this part is optional if you want to put the APNs in through the normal Android interface. Since we’re in here it might pay to put the correct APN settings in anyhow.
Select Carriers and you will see the field names for this table.Select Data and you should see a screen that looks similar to the one belowIf you can see a record that says the plmn number you wrote down earlier (mine is 53005) then you will need to edit the existing record by selecting Edit next to the record. Otherwise note down the highest ID number in the table (that’s the first field in the table) and press New.Now here’s the tricky part. You are going to need not only the plmn number but also the primary data APN details for your carrier. For comparison’s sake here are the Telecom NZ details to enter:Enter the details for your carrier using the interface shown in the screenshot below. Make sure the id is one number greater than the highest id you saw in the table. For example if there were 3 records the highest id would have been 3, so your record needs to have an id of 4. If you are editing an existing record then ignore this. You should now have several records, at least one for Internet and one for MMS displayed in the carriers table as per the screenshot below. Note that there may also be records for other carriers, or other plmn numbers for the same carrier.Now press back so you can see the list of tables and we can continue to the next section.
Fast dormancy – the whole story — xda developer tv
On today’s XDA Developer TV Erica is back to talk about the interesting topic of fast dormancy again. In last week’s video Erica gave an overview of Fast Dormancy, what it is and how it works. After weeks of research and hard work, Erica submits a great doctoral dissertation on Fast Dormancy.
In this video Erica talks demonstrates the 3G state changes and discusses their impacts on the phone and battery life. She talks about how her network changes 3G states. Finally, Erica talks about what happens if you disable or enable Fast Dormancy and how your cellular network provider’s policies can impact the state changes. Lastly a demonstration of XDA Elite Recognized Developer supercurio’s application Voodoo RRC Tool is given. Be sure to join in on the discussion in this thread.
Be sure to check out other great XDA Developer TV Videos!
Link to items mentioned:
Check out Erica’s YouTube Channel and the Samsung Smart App Challenge 2020!
Fast dormancy in release-8
The test was conducted at Nokia Siemens Networks’ Smart Lab in Dallas using Nokia Siemens Networks’ Flexi Multiradio Base Station and Radio Network Controller and Qualcomm’s QSC7230TM smartphone optimized chipset. The test showed how smartphones can act dynamically, exploiting Cell_PCH on Nokia Siemens Networks’ smart networks or adjusting to Fast Dormancy on other vendors’ traditional networks.
To explain the problem, lets look at the actual signalling that occurs when the UE is not transmitting anything. Most probably it gets put into CELL_PCH or URA_PCH state. Then when keep alive messages need to be sent then the state is transitioned to CELL_FACH and once done its sent back to CELL_PCH. Now the transitioning back from CELL_FACH (or CELL_DCH) to CELL_PCH can take quite some time, depending on the operator parameters and this wastes the UE battery life.
To speed up the transitioning to CELL_PCH state in Release-8 when the UE sends SCRI message, its supposed to include the cause value as «UE Requested PS Data session end«. Once the network receives this cause it should immediately move the UE to CELL_PCH state.
This is a win win situation for both the network and the UE vendors as long as a lot of UE’s implement this. The good thing is that even a pre-Rel8 UE can implement this and if the network supports this feature it would work.
GSMA has created a best practices document for this feature which is embedded below.
Finding out your mobile carrier’s plmn number
In Android Terminal Emulator perform the following:
Let’s talk about fast dormancy
Well first off I’d like to answer two fundamental questions when it comes to Fast Dormancy (FD):
Modifying the network info
Now since you’ve installed aShell open it and follow the steps below:Click root and press File Explorer (If it asks for Root access then grant it)Browse to /Data/Data/com.android.providers.telephony/databases so that the path is showing as followsSelect nwk_info.db and click Yes to the warning. You will be asked which application to open with. Select aSQLiteManager. Select Open database with aSQLiteManager
Now here’s the fun/dangerous part: modifying or adding the database entries for your network carrier.
Now on to the guide itself!
Updated Method as of 2 July 2020The complicated part of disabling Fast Dormancy detailed in this guide has been superseded by a new app by the recognised developer of the Siyah kernel — Gokhanmoral
This app allows you to click to add or remove the records required to disable fast dormancy. You may still read the rest of the guide to get an idea of what the app is doing, as well as adding in the APN records for your carrier. Also if you wish to modify the timing of FD then the guide may still be useful, until Gokhanmoral adds this functionality in a future release
DEPRECATED GUIDE BELOWRead this if you want to know the specifics of how disabling fast dormancy works.Install the following free apps before you begin:Android Terminal Emulator— for finding out your operator’s numeric identifieraSQLiteManager — for editing the SQLite database entriesaShell — for opening the SQLite database files in the system location
Puzzling out the fast dormancy problem
I spent a huge amount of time trying to work out why this secril_fd-interface wakelock was causing me battery drain. Eventually I worked out that this was due to Fast Dormancy not being supported by Telecom NZ, my network of choice.This was the first clue to puzzling out this enigma of a problem.
Setting the dormancy policy (dormpolicy)
Open the dormpolicy table so you can edit the dormancy policy, or timeout settings for your carrier. Press Data to view existing records.As before if a record exists for your carrier’s plmn press edit on that record, otherwise press New.Since you are disabling Fast Dormancy you want to set the lcdontime and lcdofftime to zero. If your network supported fast dormancy you’d want to set this to 60 or something similar.
Setting the network info (nwkinfo)
The next step in this process is to add the correct records in the nwkinfo table so select that and press data to view the current records for the table.
You may not have any records in this table, but if you do identify whether or not they have the correct plmn number. If there is an existing record for the plmn number of your carrier then press edit, otherwise press new. There should only be one record per plmn number in this table.Enter the details as per the screenshot above and your carrier’s plmn. The key part here is setting the dormancy field to off. Press OK once this is complete.You can check that the records are correct and then press back to return to the list of tables.
What is fast dormancy?
Fast Dormancy is a relatively recent technology that is aimed at saving battery life on your phone as well as reducing congestion on mobile networks. Essentially when your phone stops submitting data, it waits for a message from the mobile network telling it to close the connection. On some phones you might notice this is when the H or H symbol becomes a 3 or 3G symbol. Essentially its a fast way of making the mobile data connection become dormant, thus saving battery. Many recent devices, including the Samsung Galaxy SIII support Fast Dormancy and in general that is a good thing.
Why on earth would i want to disable it then?
Even though Fast Dormancy sounds like a brilliant idea (and it is) some mobile networks choose not to implement it citing reasons such as cost and network congestion (I call bs on this one though). Unfortunately if Fast Dormancy is not supported by your network and it is enabled on your phone it can cause problems. This is because your phone is sitting around waiting for a message from the mobile carrier telling it to make the data connection go to sleep.Here’s an easy way to tell when Fast Dormancy is effective: