Question Are 3GPP AT Commands disabled by default? - Samsung Galaxy A32 4G

Can someone check developer settings for me real quick? Are 3GPP AT Commands disable by default?
My thumb toggled it by accident -- maybe a couple times? Then after next reboot I got a message "your phone has switched to dual sim mode." ... not sure if that's related.
Bonus question for anyone: what does the 3GPP toggle do? Beneficial on T-Mobile? Any effect on battery life?

Both developers mode and the 3GPP AT Command are disabled by default.
3GPP is the 3rd Generation Partnership Project (3GPP) is an umbrella term for a number of standards organizations which develop protocols for mobile telecommunications. Its best known work is the development and maintenance of: GSM and related 2G and 2.5G standards, including GPRS and EDGE.
The AT command is the software interface used to control the modem, defined as part of the 3GPP standard. This means all cellular devices are required to support these commands. The commands supported by the nRF91 series is documented in the nRF91 AT Commands Reference Guide.
AT commands enable you to control everything around the modem, device, and SIM: Wake the device or put it in sleep mode. Configuration of power-saving modes.
I hope that answers your question.

Related

[Q] Easy way to switch bands? Lock to GSM or WCDMA only?

On my Touch Pro 2, if I want to lock to WCDMA only, I have to execute the following steps..
start/settings/communications/phone/[network tab]Select "GSM/UMTS Only"/[GSM/UMTS Services tab] Band/Get Settings button/ then..
Select Your Network type and from the drop down select WCDMA.
Even switching to CDMA only mode requires a lot of steps.
Whew! That's a lot. I tried to write a little program to do this in C# for windows mobile, but I got stuck because the RIL interface has no op select mode for WCDMA. (Unless it's undocumented...)
Is it possible to have a "one touch solution" for all my bands in some sort of script so I don't have to navigate that ridiculous menu? Or does someone have a programmatic way to do this?

[DEV] Enable WCDMA/Combi 850Mhz by Default

Hi all,
I'm working on a Galaxy S Gingerbread ROM, and there's something I need help with. I've put out a lot of custom ROMs, and in fact, I work with Android for a living. There is, however, something I'm really struggling with.
I hope one of you guys can help me.
I'm looking to enable the WCDMA OR COMBI-BAND 850Mhz 3G. It has recently come to my attention that the phones support this frequency, but it is not enabled by default. Enabling it is a relatively simple process, but I am trying to figure out how to enable it by default in the build.
To enable it, take the following steps:
*#*#0011#*#*
If you get a summary, press MENU>Back
- Press 8 - PHONE CONTROL
- Press 7 - NETWORK CONTROL
- Press 2 - SELECTION
Then press COMBI, and enable the relevant band without the * in.
So...
All I am doing, is looking to enable this by DEFAULT in a build.
Any ideas?
Does not work that way
When the original 850mhz mobile and then put a European modem to do a reset.
After no more than 850MHz, 1900MHz only
When selecting 850mhz band active no more, is that the modem is not compatible
The best solution is that each person using 850mhz install the modem of your choice
Anyway if you encuantra any way to fix it
would be really useful

[Q] LTE Only?

I often do live streaming of events and from time to time I am forced to tether my cell to my laptop for internet access. This actually works better than you would expect. Anyway, back in the ICS (Task650 AOKP) days anytime I needed to do this I would use the old *#*#4636*#*# code and select "LTE only". This worked great, it disabled CDMA (so no calls or texts), and most importantly it prevented the phone from switching between CDMA and LTE (which obviously would be disastrous during a live stream).
Now that I am running JB (tried CM10.1 and Task650 AOKP), this doesn't work anymore. Even though LTE works perfectly fine under normal circumstances, when I select "LTE Only" the phone simply disconnects everything and I never get data back. It seems like there was a change in the modem options or something. When I go into Settings->Mobile Networks->Network Mode I can select LTE/WCDMA, LTE/GSM/WCDMA, GSM/WCDMA. If I select any of these options and go back to the phone info screen using the *#*# code, under "preferred network type" it says "Unknown."
I've tried two modems with the same results:
I747MUMLL1
I747MVLLH1
Any ideas on what I can do?
A quick update. I did try the stock modem firmware. No change. I went back to a stock ROM, which no longer accepted the *#*# code, but did accept the *#2263# code which allowed me to select LTE band preference and locked it into LTE. Is there a way to get into this menu from an AOSP ROM? Is this specific to the dialer?
Maybe a APN change could help this but I don't think you can perma lock LTE as it's not available everywhere.
Also, mind if I ask why you wanna have LTE only? It's already set to use LTE when needed, therefor, you don't need to lock it on.
BWolf56 said:
Maybe a APN change could help this but I don't think you can perma lock LTE as it's not available everywhere.
Also, mind if I ask why you wanna have LTE only? It's already set to use LTE when needed, therefor, you don't need to lock it on.
Click to expand...
Click to collapse
Hi BWolf,
I had mentioned it in my first post but the reason I want LTE only is so I can prevent the switching of bands between LTE and HSPDA when I am live streaming. Anytime a switch occurs there's a down period of a few seconds which causes the live stream to freeze. Even with full LTE bars, the phone seems to switch every now and then.
I know it's possible, because I can do it on the stock ROM, and I could do it with the older AOSP ICS ROM's. After decompiling the stock FactoryTest.apk file it appears that everything is controlled using invokeOemRilRequestRaw commands. I'll dig into it a bit further, I'm sure there's a way to replicate the functionality.
Ugh. I was hoping the setting was actually achieved using some sort of simple command send to the baseband. That is not the case. Apparently the whole menu system resides in the baseband, and the serviceModeApp.apk app simply provides a dummy interface to display the choices and respond back with selections.
I think at this point it's a little more work than it's worth. I can always flash a nandroid of a stock rom for the streaming and then flash back afterwards. Not ideal, but it'll have to do.
Well, I've solved it. After more effort than I care to admit to, I've found the cause of a lot of the grief with the network mode settings. I'll leave this info here in case someone else ever comes looking for it.
First off, it appears selecting "LTE only" wasn't working due to some sort of bug either with the radio baseband or with how some of the custom roms deal with the baseband. This bug was persistent across ROM reflashes because persistent data in the baseband remained. It appeared to have fixed itself when I flashed back to a stock rooted rom and did a factory reset. Other people have found this solution to work for other bizarre radio related issues, such as no LTE. Anyway, that fixed the LTE only selection.
In regards to the apparent disconnect between the list of preferred networks and what the radio was actually doing, as it turns out there is a mismatch. At some point in my search I downloaded the CM10.1 source and started digging around. I found in the ril directory the reference-ril.c file which describes the network modes:
Code:
static int net2modem[] = {
MDM_GSM | MDM_WCDMA, // 0 - GSM / WCDMA Pref
MDM_GSM, // 1 - GSM only
MDM_WCDMA, // 2 - WCDMA only
MDM_GSM | MDM_WCDMA, // 3 - GSM / WCDMA Auto
MDM_CDMA | MDM_EVDO, // 4 - CDMA / EvDo Auto
MDM_CDMA, // 5 - CDMA only
MDM_EVDO, // 6 - EvDo only
MDM_GSM | MDM_WCDMA | MDM_CDMA | MDM_EVDO, // 7 - GSM/WCDMA, CDMA, EvDo
MDM_LTE | MDM_CDMA | MDM_EVDO, // 8 - LTE, CDMA and EvDo
MDM_LTE | MDM_GSM | MDM_WCDMA, // 9 - LTE, GSM/WCDMA
MDM_LTE | MDM_CDMA | MDM_EVDO | MDM_GSM | MDM_WCDMA, // 10 - LTE, CDMA, EvDo, GSM/WCDMA
MDM_LTE, // 11 - LTE only
};
These correspond directly to the spinner selections in the phone info activity, which are:
Code:
private String[] mPreferredNetworkLabels = {
"WCDMA preferred",
"GSM only",
"WCDMA only",
"GSM auto (PRL)",
"CDMA auto (PRL)",
"CDMA only",
"EvDo only",
"GSM/CDMA auto (PRL)",
"LTE/CDMA auto (PRL)",
"LTE/GSM auto (PRL)",
"LTE/GSM/CDMA auto (PRL)",
"LTE only",
"Unknown"};
If you compare the two, you can see that the descriptions are not entirely accurate. In particular, many of the mode strings do not indicate they would select EVDO (even though the mask from reference-ril.c clearly shows they would). On devices which don't support EVDO, such as the i747, selecting these modes fail.
With the LTE only network mode now working, I see no need to implement the service mode band selection menu. With that said I did have a few solid strategies for doing it, if I decided to go that route. I peeked into the SecFactoryPhoneTest.apk a little bit, which is the service Samsung uses to communicate between the RIL and userspace java apps. It connects to a local socket named "Multiclient". I found this really bizarre because the telephony stack already connects to the RIL socket, and second the socket is typically named "rild". I believe Samsung has a custom implementation of rild (the linux userspace daemon which passes RIL requests to the kernel) which implements this extra "multiclient" socket. I could not find this socket on my AOSP based ROMs, so I assume it is a proprietary Samsung thing.
Instead of connecting directly to an RIL socket, you might be able to send the bytes associated with pulling up the band selection menu, and then blind sending the correct menu selections. The samsung service uses reflection to try and send RIL requests through the ITelephony interface (and then falls back on making a direct RIL connection). Here's how it does it:
Code:
Method localMethod = localITelephony.getClass().getDeclaredMethod("sendOemRilRequestRaw", new Class[] { [B.class, [B.class });
Now I think the sendOemRilRequestRaw method is another proprietary function, but a similar one exists in the AOSP RIL implementation which is invokeOemRilRequestRaw. Using the same technique you might be able to send raw bytes to the RIL without messing around with sockets.
Ironically I just found in the source a c program that connects directly to the rild and issues commands to select certain radio options. Path is hardware/ril/rild/radiooptions.c. It connects to the debug ril socket to issue commands. A potentially super easy route to issue commands in the future would just be to modify that and run it as a command with superuser from java.

[GUIDE] [AT&T Z999] Unlock hidden GSM & LTE bands for international use

Hello.
AT&T has disabled all the international GSM\LTE bands on Z999, making it unusable outside of USA (at least in countries with GSM 900\1800, UMTS 2100 & LTE B3 & B20, like the one I live in). In order to change that, we need to turn on the Qualcomm USB Diag port, and for this, the phone has to be rooted.
I've been trying to root my AT&T Z999 for some time now, without any success, unfortunately. However, searching forums after forums, sites after sites, I've discovered the surprisingly easy method of turning on the Diag port without root.
It appears, that Axon M shares a lot with Axon 7, at least the secret key combination to enter Factory Test Mode:
Turn off the phone
Press and hold Power + Vol DOWN buttons until you see the screen "FTM" (see attached screenshot)
You have to press both buttons for the long time, do not release them when the phone starts - just wait until you see the screen. And that's it - you are now in Factory Test Mode and PC sees your phone as "ZTE Handset Diagnostic Interface (COMxx)"
Now, in order to change the bands, you have to follow these guides one after one:
Backup IMEI and NVRAM (ignore all the steps to turn Diag port on, you've done that already)
Unlock LTE bands
Mod edit: Link removed! (this guide in in Russian, but all screenshots are in English & every step is pretty clear)
You would need this tool also.
Please remember, these things are complex, and require considerable experience with Android & Windows. DO NOT START unless you feel confident that you know, what you're doing. I'm serious. Do not try this, if you're not experienced.​
WBR,
Draco.
Why mods deleted the link? Google translate exists.
Edit:
I've managed to get the data from the phone using QXDM.
lte_bc_config contained the value of "2251800618993690" now I'm parsing the info how to edit this. Seems like the tutorials don't really match this device. Now I wonder if the chipset can handle invalid data and just input all 1's. Unsupported frequencies just won't work.
Edit2: Writing all 1's didn't work.
Edit3: I wrote this value: "2251802901219551" Calculated with CDMATool. But it seems like the AT&T firmware only finds edge network. I've double checked the bands to be correct ones. So now I will switch to the chinese firmware.
Edit4: Final edit. Turns out you cannot flash chinese firmware on AT&T device. Sigh so my unit is stuck to EDGE/wifi only.
Drakosha said:
Hello.
AT&T has disabled all the international GSM\LTE bands on Z999, making it unusable outside of USA (at least in countries with GSM 900\1800, UMTS 2100 & LTE B3 & B20, like the one I live in). In order to change that, we need to turn on the Qualcomm USB Diag port, and for this, the phone has to be rooted.
I've been trying to root my AT&T Z999 for some time now, without any success, unfortunately. However, searching forums after forums, sites after sites, I've discovered the surprisingly easy method of turning on the Diag port without root.
It appears, that Axon M shares a lot with Axon 7, at least the secret key combination to enter Factory Test Mode:
Turn off the phone
Press and hold Power + Vol DOWN buttons until you see the screen "FTM" (see attached screenshot)
You have to press both buttons for the long time, do not release them when the phone starts - just wait until you see the screen. And that's it - you are now in Factory Test Mode and PC sees your phone as "ZTE Handset Diagnostic Interface (COMxx)"
Now, in order to change the bands, you have to follow these guides one after one:
Backup IMEI and NVRAM (ignore all the steps to turn Diag port on, you've done that already)
Unlock LTE bands
Mod edit: Link removed! (this guide in in Russian, but all screenshots are in English & every step is pretty clear)
You would need this tool also.
Please remember, these things are complex, and require considerable experience with Android & Windows. DO NOT START unless you feel confident that you know, what you're doing. I'm serious. Do not try this, if you're not experienced.​
WBR,
Draco.
Click to expand...
Click to collapse
Does this really work? Anyone else tried?
Sent from my SM-N950F using Tapatalk
can you repost the 3rd link?
I can't "repost" the 3rd link, but I can suggest you to open the well-known (and the best) Russian web-site with the name starting with "4" (and having something like "...pda" also), and then add this to the address: /forum/index.php?showtopic=546814&st=4640#entry35702698
Well that russian site has pretty good instructions on how to do it. I tried with one program and it didn't work on AT&T ZTE. I'll try with that qualcomm app again this weekend but if I remember right the last time it had trouble writing because it had no correct service mode code \o/
Drakosha said:
I can't "repost" the 3rd link, but I can suggest you to open the well-known (and the best) Russian web-site with the name starting with "4" (and having something like "...pda" also), and then add this to the address: /forum/index.php?showtopic=546814&st=4640#entry35702698
Click to expand...
Click to collapse
that website's address ends with ".RU", doesnt it?
i accessed that website as your given link, but i cannot see any related threads about ZTE on that, seems all they disscussed about is Lenovo K910SS. was something wrong with my searching?
gaosilver1000 said:
that website's address ends with ".RU", doesnt it?
i accessed that website as your given link, but i cannot see any related threads about ZTE on that, seems all they disscussed about is Lenovo K910SS. was something wrong with my searching?
Click to expand...
Click to collapse
Every Quallcomm device has almost the same NVram configuration rules, the difference is usually on how to enable diagnostic port, but for Z999 I have figured that out already. So, for the configuration process, every Quallcomm guide should work.
I've successfully enabled Z999 to work with 2G & Edge in my country using these guides. 3G & LTE don't work yet, but I'm sure they will eventually. I don't believe Z999 lacks the hardware ability to use LTE B3 & B20 (and other bands), it has to be something wrong with NVram parameters.
For me 2G and Edge worked out of the box in Finland. Tried to enable more but only thing that changed was power usage. Not worth it
Drakosha said:
Every Quallcomm device has almost the same NVram configuration rules, the difference is usually on how to enable diagnostic port, but for Z999 I have figured that out already. So, for the configuration process, every Quallcomm guide should work.
I've successfully enabled Z999 to work with 2G & Edge in my country using these guides. 3G & LTE don't work yet, but I'm sure they will eventually. I don't believe Z999 lacks the hardware ability to use LTE B3 & B20 (and other bands), it has to be something wrong with NVram parameters.
Click to expand...
Click to collapse
It means success unlock 2G/EDGE, not yet with 3G and LTE? When buy the device, it can use other carrer to call and 2G.
When you finger out the way to unlock LTE, please share me.
by the way, do you have the way to enter fastboot mode? I tried the "volunm + &power button" but it just do a normal restart into android.
Fair warning to everyone trying this, make sure you actually do a backup of your IMEI. I didn't and after screwing something up my SIM is no longer detected, and my IMEI is no longer available.
Hello folks!
I have an AT&T phone. I cannot connect to ANY (even EDGE) network!
I modified the configuration several times:
---
I have EDGE with this config:
00441: 0 and 0xFFFF
00946: 0 and 0x06A8
01877: 1677472
02954: 0
06828: 524356
06829: 524356
I got no LTE
---
test2:
06828: 524485
06829: 524485
I got no LTE
----
00441: 0xffff (but 0x380 is recommended)
00946: 0xff8
02954: 0 and 805765120
01877: 3460734838925427584
06828: 1904863
06829: 1904863
I got no LTE, just continous dropping network, useless config.
----
00441: 896
00946: 0 and 0x140
02954: 0 and 131072
01877: 562949974393728
Only edge network, error while searching for networks.
----
06828: 524485
06829: 524485
I have EDGE with this config, but no LTE.
----
Anyone has a good and working LTE mode?!
edit: "The bands on the AT&T z999 are: 2, 4, 5, 12, 29, 30, and 66. "
So, there won't be any Band 1,3,20 for us?!
Thanks!
No one has gotten LTE work on AT&T model. I wouldn't try this.
hene193 said:
No one has gotten LTE work on AT&T model. I wouldn't try this.
Click to expand...
Click to collapse
I had nothing, now I have EDGE, so I am glad to did that modifications...
Drakosha said:
Every Quallcomm device has almost the same NVram configuration rules, the difference is usually on how to enable diagnostic port, but for Z999 I have figured that out already. So, for the configuration process, every Quallcomm guide should work.
I've successfully enabled Z999 to work with 2G & Edge in my country using these guides. 3G & LTE don't work yet, but I'm sure they will eventually. I don't believe Z999 lacks the hardware ability to use LTE B3 & B20 (and other bands), it has to be something wrong with NVram parameters.
Click to expand...
Click to collapse
Have you been able to make 3G & LTE work? I just got my ZTE AXON M from ebay and since I can't use data or make calls/unlock the phone I was thinking of trying this.
Drakosha said:
Every Quallcomm device has almost the same NVram configuration rules, the difference is usually on how to enable diagnostic port, but for Z999 I have figured that out already. So, for the configuration process, every Quallcomm guide should work.
I've successfully enabled Z999 to work with 2G & Edge in my country using these guides. 3G & LTE don't work yet, but I'm sure they will eventually. I don't believe Z999 lacks the hardware ability to use LTE B3 & B20 (and other bands), it has to be something wrong with NVram parameters.
Click to expand...
Click to collapse
Can I describe in detail how to enable 2G?
Thanks !
Hello guys. I've tried all configs mentioned by @ugynok and some of my own - the result is still the same, no 2G network and all options in mobile connections are disabled not clickable. Can you please advice which config worked for you to enable 2G network?
Any luck?
Hi all. Was anyone able to get a useful set of bands working in the UK for this phone?
Many thanks.
V
Drakosha said:
I can't "repost" the 3rd link, but I can suggest you to open the well-known (and the best) Russian web-site with the name starting with "4" (and having something like "...pda" also), and then add this to the address: /forum/index.php?showtopic=546814&st=4640#entry35702698
Click to expand...
Click to collapse
It's the mistake. I don't know how to delete it, sorry.

Question Battery drain with bad LTE signal but with Wifi on?

Hello everyone,
on my companies area I have a really bad phone signal (LTE). How ever, I am constantly connected to my companies WIFI.
I now wonder if being connected to the WIFI will reduce battery drain due to low LTE signal?
I was hoping that the phone then only needs to search for better reception if the signal for phone calls (bot not internet) goes completely off?
Another solution would be to use Tasker to switch to my company SIM with full signal strenght (I am using dual SIM) for data/internet when on my companies area.
In any case, my private SIM will still always have bad signal but will be active for phone calls. However, my data reception will be very good (while I am still also connected to WIFI).
Just looking for the best solution in terms of battery drain.
Thanks!
VoWifi is a boon for low cellular coverage area usage while saving battery life on WIFI and still being available for phone calls. Ask your provider for specifics
Ahh thanks for that hint!
So if I enable Voice over WIFI, then my phone will stop searching for better radio signal if the WIFI signal is good enough?
Yes, in fact you can enable Airplane Mode which switches off all radios, turn on wifi radio manually to enjoy great battery life and VoWifi calls.
miravision said:
Yes, in fact you can enable Airplane Mode which switches off all radios, turn on wifi radio manually and enjoy great battery life and VoWifi calls.
Click to expand...
Click to collapse
Hmm except that I can't seem to find the option on Android 12 to enable wifi calling :S :S
Even without VoWifi you can save battery life by manually switching to 3G or even 2G for calls while using high speed data on wifi
Your carrier must support VoWifi to be seen as an option on your device.
Here is a list of US carriers that use the newer advanced Vo technologies:
T-Mobile
– VoLTE: Yes
– VoWiFi: Yes
AT&T
– VoLTE: Yes
– VoWiFi: No
Verizon
– VoLTE: Yes
– VoWiFi: No
Sprint
– VoLTE: Yes
– VoWiFi: Yes
I am from Europe so I use a different carrier. That carrier has VoLTE and VoWiFi enabled.
How ever, it seems like the carrier also has to approve each specific devices to be allowed to use VoWiFi.
As the P6P is not being officially sold in my country, I suspect that my carrier doesn't have my device on their whitelist :/
VoLTE/VoWiFi Activation
It is mandatory to have your Pixel rooted with Magisk to install this module. Make sure that Magisk is installed properly on your system, then proceed with these steps:
Install this module (Zip file) on Magisk and reboot the system.
After rebooting, the phone may be showing "No service" due to the parsing of new configurations, so please wait until the operator name showed up.
Go to Settings -> Network and Internet -> Mobile network and enable "Enhanced 4G LTE Mode" and "Wi-Fi calling".
Turn off Wi-Fi
Go to Phone -> dial *#*#4636#*#* -> Phone information tap at the top-right button, select "IMS Service Status".
Check if IMS Registration is Registered and Voice over LTE is Available then, congrats, you're succeeded.
(Voice over Wi-Fi will be activated upon the "Wi-Fi calling" option in 2.)
GitHub - thongtech/voenabler-th-p3: Thai VoLTE/VoWiFi Enabler for Pixel 3/3a/4 series
Thai VoLTE/VoWiFi Enabler for Pixel 3/3a/4 series. Contribute to thongtech/voenabler-th-p3 development by creating an account on GitHub.
github.com
After rooting, try this with any terminal app like termux from f-droid
Code:
su
settings put global wfc_ims_mode 2
Toggle Airplane mode on and then off
Enable Wifi preferred toggle in settings
miravision said:
AT&T
– VoLTE: Yes
– VoWiFi: No
Click to expand...
Click to collapse
ATT supports VoWiFi on the pixel 6/plus
miravision said:
VoLTE/VoWiFi Activation
It is mandatory to have your Pixel rooted with Magisk to install this module. Make sure that Magisk is installed properly on your system, then proceed with these steps:
Install this module (Zip file) on Magisk and reboot the system.
After rebooting, the phone may be showing "No service" due to the parsing of new configurations, so please wait until the operator name showed up.
Go to Settings -> Network and Internet -> Mobile network and enable "Enhanced 4G LTE Mode" and "Wi-Fi calling".
Turn off Wi-Fi
Go to Phone -> dial *#*#4636#*#* -> Phone information tap at the top-right button, select "IMS Service Status".
Check if IMS Registration is Registered and Voice over LTE is Available then, congrats, you're succeeded.
(Voice over Wi-Fi will be activated upon the "Wi-Fi calling" option in 2.)
GitHub - thongtech/voenabler-th-p3: Thai VoLTE/VoWiFi Enabler for Pixel 3/3a/4 series
Thai VoLTE/VoWiFi Enabler for Pixel 3/3a/4 series. Contribute to thongtech/voenabler-th-p3 development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
miravision said:
After rooting, try this with any terminal app like termux from f-droid
Code:
su
settings put global wfc_ims_mode 2
Toggle Airplane mode on and then off
Enable Wifi preferred toggle in settings
Click to expand...
Click to collapse
Thank you very much. I will probably root soon and will give it a try then. Although there is an github issue open which says that the module is not support by the Pixel 5.
Just a bit annoying that I would have to apply this after every OTA but I guess it's doable
I also talked to my carrier today. They are saying that only phones that are being sold by the carrier support VoWiFi as the phones OS needs special settings that are being provided by the carrier. That is why usually the Android updates from phones bought through our carriers come later than the official google updates (due to the carrier updating the OS himself first).
On the other hand it seems like google could integrate those "special" settings right out of the box.
How ever, google seems to say the carrier has to get in touch with them and start the procedure whole the carrier says that is google who has to take care of it by them self.
Since the phone signal for my SIM is really bad on my companies area but the WIFI is very good, this should then hopefully help a lot with battery drain.

Categories

Resources