Database Info

wifi turns off in 10 secs

Today I turned on my phone's wireless and I noticed it turned off quickly. I thought it was odd so I turned it on again...same thing occurred. The third time I went into settings > wireless and network > wi-fi settings and enabled the wi-fi card from there. It shows it's scanning and then displays "unable to scan networks" along with turning off the wireless card. What the crap?!
I've rebooted the phone a couple of times - still nothing. I'm going to try removing the battery for 10-15 mins and try it again but I don't imagine that's going to fix anything. A quick google search has shown only a couple other people with a captivate are having this problem as well. I have to imagine there are more out there? Anyone have a clue. I'm really trying to avoid flashing back to stock.
Thanks in advance.

Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?

max_warheads said:
Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?
Click to expand...
Click to collapse
How would that affect WiFi??

If the system does not have proper write access to the file, and then a program says to the settings provider "turn on wifi", but the provider is not able to save that setting, it will later turn around and say "yeah... thats not supposed to be on." Which happens to coincide with an approximately 10 second window.

max_warheads said:
Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?
Click to expand...
Click to collapse
Thanks for your help. However I did not edit settings.db. I've only rooted the phone. Haven't done any other manual edits to the system.
The only relevant thing I can think of that might be useful information is yesterday morning I installed wi-fi analyzer from the market on my phone. I'm 99% sure that my wi-fi was working after I installed it but then later in the day the problem started. Last night I un-installed wi-fi analyzer just to be safe.
Could this program have made some edits to Android that is causing the problem?

I found a similar problem in a google code forum from 2008. Individuals were using a G1 and had the same problem. They mentioned that it appears as if the wi-fi driver would load but then wouldn't be able to recognize the wireless card.
Hopefully some useful information to someone. Thanks again guys for taking a look.

sola fide said:
I found a similar problem in a google code forum from 2008. Individuals were using a G1 and had the same problem. They mentioned that it appears as if the wi-fi driver would load but then wouldn't be able to recognize the wireless card.
Hopefully some useful information to someone. Thanks again guys for taking a look.
Click to expand...
Click to collapse
Ran into the same issue, my issue was solved by fixing permissions as mentioned in the previous reply. How did you root your phone?

div3rg3nt said:
Ran into the same issue, my issue was solved by fixing permissions as mentioned in the previous reply. How did you root your phone?
Click to expand...
Click to collapse
Rooted the phone by using the update.zip file from the "Pimp My Captivate" thread.
How could I edit the permissions for the file to see if this remedy's the problem? I already have Terminal Emulator on my phone but I'm brand new to linux commands.

open Terminal Emulator and follow along
Code:
$ su
# cd /dbdata/databases/com.android.providers.settings/
# ls -l settings.db
You should see :
Code:
-rw-rw---- system system <snip> settings.db

max_warheads said:
open Terminal Emulator and follow along
Code:
$ su
# cd /dbdata/databases/com.android.providers.settings/
# ls -l settings.db
You should see :
Code:
-rw-rw---- system system <snip> settings.db
Click to expand...
Click to collapse
Ran the code you gave and it returned what you wrote above:
Code:
-rw-rw---- system system <snip> settings.db
I take it this means that settings.db is already set as writeable which means it's not my problem?

Yuppers... :/

Thanks for trying max.
What about the wireless config file? If this was messed up could it cause it the wireless card to act up like this? Could I simply delete this file and android would recreate it when I turned on the wireless card? Along with - where is it on the captivate?
Just a thought, my knowledge in this field is pretty low.

bumping this thread

Update: A factory reset fixed the problem. However when I restored from a Titanium backup the wireless immediately stopped working. Obviously there is something in the software/files that are corrupt causing this problem.
Anyone have any ideas of which file to attack?

BUMP
I am having this problem too. It is very annoying and I don't want to reflash the rom again. Has anyone else had this problem (and fixed it)?

americanbordercollie said:
BUMP
I am having this problem too. It is very annoying and I don't want to reflash the rom again. Has anyone else had this problem (and fixed it)?
Click to expand...
Click to collapse
ABC: Is there anything you installed before the problem happened that you think might be causing it? I'm guessing since you said "again" that this is the 2nd time or more you'll be flashing your phone if we don't find a fix.

I had to flash it with Odin because my phone bricked two weeks ago trying to enable non-market apps. I don't want to go through that process again.
I didn't install anything except the WiFinder app. It stopped working after a coworker asked me to turn on my wifi to test an app he got for his phone that turns it into a WiFi hotspot through its 3G data connection. The test was unsuccessful anyway, but that is irrelevant.

I had the problem of wifi not being able to scan for devices after 10 sec. This problem was only on my wifi at work.
I set the IP address, IP mack, gateway address and DNS servers statically and saved the config. This got me connected to the wifi at work. You could try this.
Just changed permissions on settings.db and now wifi seems to be working flawlessly without a need for static config.

americanbordercollie said:
I had to flash it with Odin because my phone bricked two weeks ago trying to enable non-market apps. I don't want to go through that process again.
I didn't install anything except the WiFinder app. It stopped working after a coworker asked me to turn on my wifi to test an app he got for his phone that turns it into a WiFi hotspot through its 3G data connection. The test was unsuccessful anyway, but that is irrelevant.
Click to expand...
Click to collapse
I'm curious if WiFinder altered a file that is causing the problem. Mine came just 30 minutes after installing Wifi Analyzer. Just hunch since both programs use the wireless card.

santblue said:
I had the problem of wifi not being able to scan for devices after 10 sec. This problem was only on my wifi at work.
I set the IP address, IP mack, gateway address and DNS servers statically and saved the config. This got me connected to the wifi at work. You could try this.
Just changed permissions on settings.db and now wifi seems to be working flawlessly without a need for static config.
Click to expand...
Click to collapse
It sounds like the same problem I had but I wasn't able to connect anywhere - At either one of my offices or at home. I tried to add in manual settings in the Android menu but it still didn't help.
I'll try messing with the settings.db file if this happens again and report back. I'm crossing my fingers that I never have this problem again but you never know. Hopefully we can get a couple of known working solutions posted on here since it sounds like there are plenty of people out there having this problem.

Wifi scanning when connected

Anyone know why wifi keeps scanning even though you're connected. I can understand when you're looking for a signal but when you're connected already? Ugh...
Sent from my SAMSUNG-SGH-I997R

For when u want to change to a different AP ....
sent from Infuse but miss my captivate on cont. 5.5.... One day this can be as good...

From what I understand, you can change the scan interval in the build.prop file in the /system directory. I have mine set to 120.
If you are looking at wifi settings, depending on if you are stock and what rom you have, you may see it scan every 5 seconds, or constantly (stock).
This only happens when you are looking at the wifi settings themselves. When you exit the wifi settings menu, it goes back to whatever you have set in build.prop

Blade Buddy (in the market), will allow you to change the Wifi scan interval, it's under Advanced Settings, the setting is "wifi.supplicant_scan_interval". The app requires root/superuser privs. Default from AT&T is every 15 seconds, Infused ROM sets it to 120 to save battery. Be sure to hit the menu soft button, apply, then save and restart the phone.

w4rmk said:
Blade Buddy (in the market), will allow you to change the Wifi scan interval, it's under Advanced Settings, the setting is "wifi.supplicant_scan_interval". The app requires root/superuser privs. Default from AT&T is every 15 seconds, Infused ROM sets it to 120 to save battery. Be sure to hit the menu soft button, apply, then save and restart the phone.
Click to expand...
Click to collapse
I was under the impression that blade buddy and build prompt changes are only affecting the scan while NOT connected...
Changing those settings does not appear to change how frequent it scans WHILE connected to an ap

00mred00 said:
I was under the impression that blade buddy and build prompt changes are only affecting the scan while NOT connected...
Changing those settings does not appear to change how frequent it scans WHILE connected to an ap
Click to expand...
Click to collapse
This is correct. After changing it still scans when connected :/
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

iOSlulz said:
This is correct. After changing it still scans when connected :/
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I think there is a miss understanding...give me 20 minutes to test my theory...
be back soon.
VERIFIED ...huge misconception
so...running a log I see that yes
Wifi monitor, process 680, runs exactly every 2 minutes, just as set in the build prop. It always does this.
Wifi SETTINGS, process 5890, runs every time you open wifi settings and updates the access points..once you close wifi settings it stops.
I can see what they did here...Many other devices have a manual scan (menu, scan) they made the scan for ap's auto when you open wifi settings, and only when you open wifi settings. that particular scan (process 5890) is not running constantly. It stops when you close wifi settings.
process 680 runs every 2 minutes while wifi is on. I don't have my other devices with me, and have never noticed or looked at this process before so for all I know it's this way on any device. I will look into that more later. Given that process 5890 is the one that actually updates the list of ap's...I wonder what exactly process 680 is doing.
I am at work and don't have the time that I want to spend on this (my employees have interrupted me 3 times while I typed this lol)

WiFi Power Saving tweak

I would like to share the results I got from tweaking (root needed) this registry:
File:
/system/etc/wifi/tiwlan.ini
Registry:
PowerSavePowerLevel = 1
#0 - ELP
#1 - PD
#2 - AWAKE
The default value was ELP, but that way my WiFi keeps disconnecting from WPA2 AES enabled Access points.
I changed to PD and problem solved.
First a made a copy of the file to backup if something went wrong, I used a text editor to change the "tiwlan.ini" and then rebooted the phone.
But now WiFi wastes more energy, can't have everything.

Change to wpa1, I did it and solve all my wifi problems

Or you can use programm wi-fi fixer

ezantera said:
Change to wpa1, I did it and solve all my wifi problems
Click to expand...
Click to collapse
But clearly this is Defy's problem, and WPA2 AES is very popular where I live, that is not praticable for me.
mainbord said:
Or you can use programm wi-fi fixer
Click to expand...
Click to collapse
I'm going to give it a try. But tweaking powersave can be a solution to many problems, there should be an app to let users switch it easily.
EDIT:
best setting I found in the program is the option to disable wifilock:
http://developer.android.com/reference/android/net/wifi/WifiManager.WifiLock.html
http://code.google.com/p/android/issues/detail?id=9781
It is similar to change power saving...
EDIT:
Until now I haven't been able to reproduce the wifi disconnections after disabling lock using Wifi fixer and rebooting.
Same result as "Power Down" mode (PD), question is, what wastes more energy, if it is hardware mode PD
or software wifilock (not allowing turn off when the device is idle).
in progress

mrolp said:
I would like to share the results I got from tweaking (root needed) this registry:
File:
/system/etc/wifi/tiwlan.ini
Registry:
PowerSavePowerLevel = 1
#0 - ELP
#1 - PD
#2 - AWAKE
The default value was ELP, but that way my WiFi keeps disconnecting from WPA2 AES enabled Access points.
I changed to PD and problem solved.
First a made a copy of the file to backup if something went wrong, I used a text editor to change the "tiwlan.ini" and then rebooted the phone.
But now WiFi wastes more energy, can't have everything.
Click to expand...
Click to collapse
Your tweak don't change anything, the wifi connectivity still don't better

m!k3 said:
Your tweak don't change anything, the wifi connectivity still don't better
Click to expand...
Click to collapse
Your phone suffer from random disconnections (WPA2 AES enabled Acess Point) as mine did?
Are you sure the value of "PowerSavePowerLevel" in "tiwlan.ini" was successful changed from zero to one,
and you restart/reboot your Android after the change?
My ROM is stock Gingerbread -134 (2.3.4), what's yours?

mrolp said:
Your phone suffer from random disconnections (WPA2 AES enabled Acess Point) as mine did?
Are you sure the value of "PowerSavePowerLevel" in "tiwlan.ini" was successful changed from zero to one,
and you restart/reboot your Android after the change?
My ROM is stock Gingerbread -134 (2.3.4), what's yours?
Click to expand...
Click to collapse
Yes, i have made a new zip update with this value in tiwlan.ini.
But i'm not disconnected, this the connectivity with the web.
The link still here, but no page or no dl is possible
my rom is MIUI 1.8.27
Sorry for my english

my wifi is connected but cant get to internet when AES with buffalo hp-g300n,
I just changed to TKIP and wifi works without problems.
I tried changing powersaving , 802.11n on/off, dhcp/manual ip, and none of them worked fine.

businessman9 said:
my wifi is connected but cant get to internet when AES with buffalo hp-g300n,
I just changed to TKIP and wifi works without problems.
I tried changing powersaving , 802.11n on/off, dhcp/manual ip, and none of them worked fine.
Click to expand...
Click to collapse
I'am too, but in tkip my network aren't in optimal config for other stuff of my network!!

mrolp said:
I would like to share the results I got from tweaking (root needed) this registry:
Click to expand...
Click to collapse
I have to test it more but it seems to fix my problem with WiFi.
My home network is using WPA2 with TKIP. Using CM7 and MIUI I have experienced disconnects while downloading larger files or watching Youtube. Regular browsing was ok but I couldn't really use Android Market. Stock ROMs were fine, even those based on leaked 2.3.4.

miscz said:
I have to test it more but it seems to fix my problem with WiFi.
My home network is using WPA2 with TKIP. Using CM7 and MIUI I have experienced disconnects while downloading larger files or watching Youtube. Regular browsing was ok but I couldn't really use Android Market. Stock ROMs were fine, even those based on leaked 2.3.4.
Click to expand...
Click to collapse
Now we are 2 . Hope it helps more people.
m!k3 said:
Yes, i have made a new zip update with this value in tiwlan.ini.
But i'm not disconnected, this the connectivity with the web.
The link still here, but no page or no dl is possible
my rom is MIUI 1.8.27
Sorry for my english
Click to expand...
Click to collapse
Your english is really good for me, it is not my native language too
I replaced mine the old way, using copy/paste with root access and the app ES Explorer.
I'm attaching to this post the original "tiwlan.ini" that came with my ROM (without the tweak), for you to check if it's equal to your ROM's original "tiwlan.ini".
My disconnection is the same, I only know it because I try to open a site or download and doesn't work, system keeps showing wireless connected.
You can try the program suggested by mainbord (Wifi Fixer), and in "preferences"/"Advanced Options" uncheck "Enable Wifi Lock". This is an alternative that solved my problem too.

mrolp said:
Now we are 2 . Hope it helps more people.
Your english is really good for me, it is not my native language too
I replaced mine the old way, using copy/paste with root access and the app ES Explorer.
I'm attaching to this post the original "tiwlan.ini" that came with my ROM (without the tweak), for you to check if it's equal to your ROM's original "tiwlan.ini".
My disconnection is the same, I only know it because I try to open a site or download and doesn't work, system keeps showing wireless connected.
You can try the program suggested by mainbord (Wifi Fixer), and in "preferences"/"Advanced Options" uncheck "Enable Wifi Lock". This is an alternative that solved my problem too.
Click to expand...
Click to collapse
I can't open your tiwlan.ini... i have test wifi fixer, but i don't see any difference.. I think solve the problem whit any mod in wpa_supplicant...
but I'm not sur...
in the wpa supplicant del the option wpa2

I have experienced disconnects only with roms based on leaked 2.3.4. CM7 was OK. Now I'm using oficial Retail 2.2.1, with tiwlan.ini set with PowerSavePowerLevel = 0 (ELP) and everything is OK.
I'm going to install Motoginger Teaser v4 tonight and, if problem persist, I'll try this tiwlan.ini modification.
EDIT: Problem with Motoginger persists. Testing with option 1 set and no disconnection untill now.
Thanks for the trick.

After using that trick, my phone can't connect to wifi (only tried my WPA AES) and (could be unrelated) can't use the SIM card. Data wipe doesn't fix it...

@m!k3
I'm sorry that it does not work in your case.
@romuleta
now we are 3
geecko said:
After using that trick, my phone can't connect to wifi (only tried my WPA AES) and (could be unrelated) can't use the SIM card. Data wipe doesn't fix it...
Click to expand...
Click to collapse
@geecko
What is the version of your ROM?
Do you have a backup of your original "/system/etc/wifi/tiwlan.ini"
to replace as suggested in the #1 post?
EDIT: I've found your thread describing it.
geecko said:
Hey
I recently flashed Miui English, latest version.
But I quickly faced the following issues :
- It didn't ask for my PIN.
- Wifi worked, but weird bugs occurred.
I found it weird, so I did what a topic advised : I edited /system/etc/wifi/tiwlan.ini
The modifications were only applied to the power saving setting.
I rebooted and I'm not sure if it happened immediately but eventually wifi didn't even work anymore. So I installed CM7, no changes.
Flashed back the 3.4.3-11 Blur .sbf and ... no changes ! Data and cache Wipe doesn't change anything either. Of course I also restored the tiwlan.ini .
So whatever the ROM it is I'm using, "Invalid Sim card" and wifi "connects, disconnects, scans, connects, disconnects" but never ever connects.
How do I fix this ? It seems to be software-side 'cause it appeared when I installed Miui.
Click to expand...
Click to collapse
It seems you already had strange problems with PIN and Wifi before making the tweak, and after the tweak (not sure if immediately) things got worse.
Hope someone can help you find exactly where the bug is.

mainbord said:
Or you can use programm wi-fi fixer
Click to expand...
Click to collapse
A link to that program please?
Thx

Can't find the Wifi Scan Interval in build.prop

I'm on the "leaked" ICS, and I'm trying to change the wifi scan interval. Doesn't seem to be in the build.prop like I'm familiar with. I'm only mildly familiar with poking around in the more advanced settings, and most of that was learned in GB. Any help? Thanks!

WangChung81 said:
I'm on the "leaked" ICS, and I'm trying to change the wifi scan interval. Doesn't seem to be in the build.prop like I'm familiar with. I'm only mildly familiar with poking around in the more advanced settings, and most of that was learned in GB. Any help? Thanks!
Click to expand...
Click to collapse
you can add to build.prop under Additional build props
ex.
Code:
wifi.supplicant_scan_interval=135

Thanks, I'll give that a shot!

wrong thread, sorry

no changed scan interval
biopsin said:
you can add to build.prop under Additional build props
ex.
Code:
wifi.supplicant_scan_interval=135
Click to expand...
Click to collapse
to me with that nothing has changed, 5 seconds were before, 5 seconds are now,
with wifi.supplicant_scan_interval=600 too..
---------- Post added at 01:03 PM ---------- Previous post was at 12:47 PM ----------
netprospero said:
to me with that nothing has changed, 5 seconds were before, 5 seconds are now,
with wifi.supplicant_scan_interval=600 too..
Click to expand...
Click to collapse
found that
Quote:
Originally Posted by TeamERA 
ok Kenny, I didnt read all the thread because time dosnt allow me to anymore. But If you are noticing a scan as your looking at the wifi connections screen it will always scan at a faster interval even when connected, because it is refreshing the list giving you the optuon to switch to a new network once found; But this sHould only happen when in that discovery window. Once connected and out of that wondow it will no.longer scan (but will still scan at set interval, even if set to not motify of new network). When in that window it will scan faster no matter what the set interval is. And 300 is 5 minutes, a perfect scan time if you ask me, if you plan on using wifi some where your gonna be there for more then 5minutes right.
Sent from my SPH-D710 using xda premium
so build.prop scan interval affect wifi functionality, but not when you are in wifi page, that starts monitoring in real-time (4/5 seconds) because if you are there is to look for new connections..

Preferred network type

Many of you are probably aware of the Testing menu containing network and other various settings (you type in *#*#4636#*#* into your dialer).
For years I've used it to mitigate the spotty 3G connection in my house, to keep the phone from 'flickering' between 3G for basically every other room in my house.
Using GSM auto (PRL) keeps me on GSM indoors and switches to 3G as soon as I leave the house. This also has a noticeable improvement on battery life.
Only now it does not persist through reboots. It always defaults back to the original setting, which even includes TD-SCDMA which is a Chinese-only network type that I never want my phone to scan for at all.
So far the only thing I've been able to do that persists through reboots is
Code:
su
settings put global preferred_network_mode 1,20
This will force it to GSM only. Only 2 other codes persist: 18,20 which is another TD-SCDMA inclusive and 20,20 which is the default.
These correlate to the Preferred network type in SIM card settings.
If anyone has any more insight into this, I'm pretty much out of ideas.
EDIT: I realize now that the issue might not be exactly made clear. It's a very specific set of circumstances:
The testing menu (*#*#4636#*#*) applies changes to the network immediately, but not persistently.
Editing the values does not apply changes immediately, and only persists on those 3 values after reboot.

you can use intelli3G, but it requires xposed installed

Thanks, I'll keep it in mind as a last ditch effort.
I'd rather not run so many auxiliary programs, especially when the required function is so minimal, but the program so extensive.

Logic_ said:
Thanks, I'll keep it in mind as a last ditch effort.
I'd rather not run so many auxiliary programs, especially when the required function is so minimal, but the program so extensive.
Click to expand...
Click to collapse
oops, I tried Intelli3G, it does not work well, caused overheat.
maybe you should try smart network, it is more compact, but I am not so sure

Logic_ said:
Many of you are probably aware of the Testing menu containing network and other various settings (you type in *#*#4636#*#* into your dialer).
For years I've used it to mitigate the spotty 3G connection in my house, to keep the phone from 'flickering' between 3G for basically every other room in my house.
Using GSM auto (PRL) keeps me on GSM indoors and switches to 3G as soon as I leave the house. This also has a noticeable improvement on battery life.
Only now it does not persist through reboots. It always defaults back to the original setting, which even includes TD-SCDMA which is a Chinese-only network type that I never want my phone to scan for at all.
So far the only thing I've been able to do that persists through reboots is
Code:
su
settings put global preferred_network_mode 1,20
This will force it to GSM only. Only 2 other codes persist: 18,20 which is another TD-SCDMA inclusive and 20,20 which is the default.
These correlate to the Preferred network type in SIM card settings.
If anyone has any more insight into this, I'm pretty much out of ideas.
Click to expand...
Click to collapse
You can use an init.d script to set the network mode at reboot

ice-it said:
Many of you are probably aware of the Testing menu containing network and other various settings (you type in *#*#4636#*#* into your dialer).
For years I've used it to mitigate the spotty 3G connection in my house, to keep the phone from 'flickering' between 3G for basically every other room in my house.
Using GSM auto (PRL) keeps me on GSM indoors and switches to 3G as soon as I leave the house. This also has a noticeable improvement on battery life.
Only now it does not persist through reboots. It always defaults back to the original setting, which even includes TD-SCDMA which is a Chinese-only network type that I never want my phone to scan for at all.
So far the only thing I've been able to do that persists through reboots is
You can use an init.d script to set the network mode at reboot
Click to expand...
Click to collapse
Sorry, I should have phrased that more clearly. Apart from the 3 that were mentioned, no other values seem to affect the connection. My ideal solution would indeed be an init.d script.
Thanks for chiming in!
Sent from my Mi-4c using XDA Labs

Logic_ said:
Sorry, I should have phrased that more clearly. Apart from the 3 that were mentioned, no other values seem to affect the connection. My ideal solution would indeed be an init.d script.
Thanks for chiming in!
Sent from my Mi-4c using XDA Labs
Click to expand...
Click to collapse
Maybe we're looking at the wrong entry, if i change the type from the menu I always get 18,20 from setting though the network seems to be changed...

ice-it said:
Maybe we're looking at the wrong entry, if i change the type from the menu I always get 18,20 from setting though the network seems to be changed...
Click to expand...
Click to collapse
Yes, that's the issue exactly. From the menu the changes are applied immediately yet the changes don't stick. From editing the values the network remains unchanged until reboot, but only those 3 values will stick.
I wouldn't know what setting the menu would call upon other than preferred_network_mode
but I don't know much tbh, that's why I hope someone does

Logic_ said:
Yes, that's the issue exactly. From the menu the changes are applied immediately yet the changes don't stick. From editing the values the network remains unchanged until reboot, but only those 3 values will stick.
I wouldn't know what setting the menu would call upon other than preferred_network_mode
but I don't know much tbh, that's why I hope someone does
Click to expand...
Click to collapse
I've pulled the settings.db now and i will look into it if i can find some answers
Sorry, I've looked in every table but i cant find anything... I cant understand how you can change a setting without updating the setting.db, only the 3 option of the standard menu are saved (4g/3g/2g)...

ice-it said:
I've pulled the settings.db now and i will look into it if i can find some answers
Sorry, I've looked in every table but i cant find anything... I cant understand how you can change a setting without updating the setting.db, only the 3 option of the standard menu are saved (4g/3g/2g)...
Click to expand...
Click to collapse
Right? I can't find anything on this. There must be a mirrored table somewhere where the value is held. Or maybe the setting stays active in a system app that is kept in memory? Like phone.apk or something.
I might be saying ridiculous things, I'm grasping at straws here.
Thanks for checking man.
Sent from my Mi-4c using XDA Labs

Logic_ said:
Right? I can't find anything on this. There must be a mirrored table somewhere where the value is held. Or maybe the setting stays active in a system app that is kept in memory? Like phone.apk or something.
I might be saying ridiculous things, I'm grasping at straws here.
Thanks for checking man.
Sent from my Mi-4c using XDA Labs
Click to expand...
Click to collapse
I've tried also to edit the build.prop but changes don't affect the system
Code:
#
# System props for telephony
# Start in GSM Auto PRL for Sim1 and GSM Only for Sim2
ro.telephony.default_network=3,1
ro.ril.def.preferred.network=3,1
#
# System prop to turn on GSMLTEPhone always
telephony.lteOnCdmaDevice=0
telephony.lteOnGSMDevice=1
I've tried also to put the phone in GSM Only like that
Code:
#
# System props for telephony
# Start in GSM Only
ro.telephony.default_network=1
ro.ril.def.preferred.network=1
Still no changes at all

ice-it said:
I've tried also to edit the build.prop but changes don't affect the system
Code:
#
# System props for telephony
# Start in GSM Auto PRL for Sim1 and GSM Only for Sim2
ro.telephony.default_network=3,1
ro.ril.def.preferred.network=3,1
#
# System prop to turn on GSMLTEPhone always
telephony.lteOnCdmaDevice=0
telephony.lteOnGSMDevice=1
I've tried also to put the phone in GSM Only like that
Code:
#
# System props for telephony
# Start in GSM Only
ro.telephony.default_network=1
ro.ril.def.preferred.network=1
Still no changes at all
Click to expand...
Click to collapse
Yup, specifically those are ignored. I had tried them previously and thought maybe build.prop changes were ignored entirely (I hadn't made any tweaks or anything yet), but other changes to build.prop work just fine.
Could they have hardcoded these into the radio perhaps? I guess not since it can be affected through the testing menu... I keep going back and forth between theories like this, can't make sense of it.

Logic_ said:
Yup, specifically those are ignored. I had tried them previously and thought maybe build.prop changes were ignored entirely (I hadn't made any tweaks or anything yet), but other changes to build.prop work just fine.
Could they have hardcoded these into the radio perhaps? I guess not since it can be affected through the testing menu... I keep going back and forth between theories like this, can't make sense of it.
Click to expand...
Click to collapse
I start thinking the RIL change the values after build.prop load... Maybe they coded a method that initialize the daemon and only accept the 3 option reachable from settings...
But this is speculation, I need to take a look at the RIL, but I can't find it

ice-it said:
I start thinking the RIL change the values after build.prop load... Maybe they coded a method that initialize the daemon and only accept the 3 option reachable from settings...
But this is speculation, I need to take a look at the RIL, but I can't find it
Click to expand...
Click to collapse
Well sadly that's already beyond my scope of reasoning. Good luck in your search of knowledge, I hope something comes up
Sent from my Mi-4c using XDA Labs

Any news on this? Been having the same issue on miui9 redmi3!