Related
Has anyone figured out a fix for the GPRS connection with the new T-Mobile ROM 1.60.07? My GPRS used to always be connected and now everytime I turn off the phone, the GPRS disconnects. In addition, I think some of the battery life problems come when the phone turns itself on (screen and all) to check e-mail (as set up in the Inbox settings). It used to check the e-mail silently without turning on the screen and then sound a notification tone.
I wasn't sure if anyone knew if this was a simple registry setting or a problem only solved with a Phone Stack upgrade?
Any help would be appreciated.
JBW
I've just upgraded to 1.60.00WWE (the radio stack is 1.60.01) and noticed the exact same thing. I did a lot af searching on Google and these symptoms are not mentioned anywhere, in general everyone is saying that the upgrade went fine and the device runs better than before, so it seems we are in the minority. Hopfully this is good news, and there's just something dumb that is not configured properly.
I also have the same problem ( and my friends with xda-2 ) all was fine befor the upgrade, But now the GPRS disconets , No good for MSN Messanger
John
I heard this from several users on several forums.. a lot didn't notice, but there was enough who did to make me not upgrade.. once the imate update came out i asked around for people that used that if their grps disconnected.. it didn't, so i upgraded with that ROM instead of the t-mobile one. Sorry for you guys =/
-arebelspy
GPRS Fix
See the post above this one. Apparently if you delete the file TMD_AP_NL.sa.CAB from the extended ROM and hard reset, the GPRS stays on. You do lose the little GPRS timer but who cares!
I'm going to try it tomorrow and will report back.
JBW
Success! Sort of...
Well, I took some advice and changed my Ext_ROM. I took out all of the T-Mobile stuff and put in a bunch of the programs I always have to re-load myself. Then, the Hard Reset!
Bam! Now I have Always on GPRS again. However, apparently, one of the files in the Ext_ROM must also have the Bluetooth Fix with it. Now, I don't have the option of COM4 and COM5 for Bluetooth communications from before.
Does anyone know which of the files in the Ext_ROM this might have been? I am reluctant to try them one by one for fear of messing up the GPRS again.
Any help is appreciated!
JBW
Bluetooth Fix for Serial profile
I believe is between this two
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
Total Success... finally!
Well, thank you thariman for your help. I am very pleased now. I installed the two files from the ext_rom:
OEM_AKU1_WWE_4AP.sa.CAB
OEM_WWE_03120301.sa.CAB
The first gives Bluetooth Settings the option for in and out COM ports. The second assigns these ports to COM4 and COM5.
Now, I have the Bluetooth fix to use my GPS and wireless sync AND the always on GPRS.
I hope everyone figures this out. I guess T-Mobile does not want users to have the always on GPRS connection. In seems to be disabled via there customization. Seems strange though considering their pricing is for unlimited use.
Anyway, I'm happy with my set up now! Good luck to all.
JBW
Hi everyone,
I've been running a WM6.5 ROM lately, and the stability was great - less crashes, hardly any problems with the device just turning off... but it was extremely slow because most of the RAM was used just for running the system.
So I went back to a WM6.1 ROM, and I noticed that the device was freezing in standby mode when left alone for a while - the screen won't turn on any more... apparently the CPU locks to 100% when the freezes happen, because after a restart the battery is drained to 50% (from 100%!) and the device is very hot. This used to happen on other WM6.1 ROMs as well...
Any idea why this is happening? Why only on WM6.1 ROMs? Is my device just ****ed up? Or am I doing something wrong?
same with me.. ..but i think that my device haw this freezing on sms receiving, sometimes it vibrate without stop. ..
Do you use BatteryStatus by any chance? I've just uninstalled it on a whim and so far no crashes. Won't be able to tell for sure until in a few days though...
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
Prophet doesn't have 3G.
bemymonkey said:
Prophet doesn't have 3G.
Click to expand...
Click to collapse
read the post fully he is saying select what your phone supports
Did you try suggestion in post #4 ?
Just might be the answer your looking for
So how would I have gone about selecting something that my phone doesn't support in the first place?
As far as I can tell, there is no possible way I could have set my Prophet to use 3G
Oh and by the way, your ROMs are great and all, but using the comma, period and Shift key every now and then will make what you're trying to say a lot more easy to understand...
As for the problem itself - I've just reinstalled a completely blank ROM (one of dioxda's) and only sync'd my contacts and appointments - NO third-party software whatsoever. And looky here, no crashes. Now I can install one app per day and see which one causes the SODs...
bemymonkey said:
As for the problem itself - I've just reinstalled a completely blank ROM (one of dioxda's) and only sync'd my contacts and appointments - NO third-party software whatsoever. And looky here, no crashes. Now I can install one app per day and see which one causes the SODs...
Click to expand...
Click to collapse
I understand what you are saying on the HTC Tytn II and HTC Touch Diamond 2 the phones I had the Standby of Death with it was due to the phones network/band type being set to AUTO 3G/2G, changing this setting to either 3G only (WCDMA + UMTS 2100) or 2G only (GSM + AUTO) solved the problem completely.
In your case its most probably due to something you've installed which is a lot easier to solve, I suppose when you look in your phones network type setting GSM is the only option and the band is probably already set to AUTO.
I didn't know the Prophet did not support 3G before I posted this, on all phones that support 3G with this problem my solution often solves the problem but it can happen because of certain software installed also.
My installation has been working fine and I even managed to increase battery life by installing "Juice".
Suddenly, about 3 days ago I noticed the phone was saying no signal. I was clearly getting data, as my apps worked and I was getting eMail alerts and downloads, but no calls.
I tried restarts, but to no avail. I am using Rod_100 UK as I am on Vodafone UK... I assume it is correct, certainly worked for the past month.
I have had to revert back to Windows Mobile.
My immediate thoughts are it is Juice that is causing it. I have just logged back in to my XDAndroid to write this and Juice did not load, and guess what, the signal has come back.......
Just in case is there anything else to look for?
Never heard of "Juice". I have heard of JuiceDefender however...
If you don't have the issue on a clean install, I'd say that app (or one of many I'm assuming you have installed) is the culprit. Rename your data.img and boot, see what happens.
Yes, it is JuiceDefender, apologies for the abbreviation.
I un-installed it and I have network again, but I guess I will loose battery longevity again, not that it made a huge difference.
I'll keep my eye on it....
Still no improvement
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
I dont know what exactly but some program is giving android problems
jonners59 said:
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
Click to expand...
Click to collapse
All I can say is do the standard mess.
Make sure you're up to date.*
Delete (move, rename) data.img.
Format SD. Full format. HP tool.
*There's a lot of testing stuff flying around right now too, making that difficult admittedly. Hopefully the auto-build service will return soon, and all the madness will get committed soon!
Check in your startup file forcecdma=0. I had that problem too.
wormy315 said:
Check in your startup file forcecdma=0. I had that problem too.
Click to expand...
Click to collapse
The command is force_cdma=X....
arrrghhh said:
The command is force_cdma=X....
Click to expand...
Click to collapse
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
jonners59 said:
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
Click to expand...
Click to collapse
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
arrrghhh said:
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
Click to expand...
Click to collapse
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
jonners59 said:
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
Click to expand...
Click to collapse
What is not "Executable" any more... haret.exe?
The startup file
Sorry, ignore me.
After the change, I double clicked the Android shortcut to launch Android, but it would not start, so I assumed the file had to be executable (as it was the only item I had changed)... I had forgotten to disconnect my TP2 from my laptop!
I've done so now and it has launched. A stupid user errorhttp://media.xda-developers.com/images/smilies/biggrin.gif
I'll keep you posted on any changes.
Ha, fair enough. Enjoy.
Solved. Keep loosing Radio
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
jonners59 said:
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
Click to expand...
Click to collapse
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
jonners59 said:
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
Click to expand...
Click to collapse
Hrm, didn't realize that app would help out that much. But, it makes sense if it's turning off all your radios lol.
Anyhoo, have you seen the kernel I posted from WisTilt2? It has full panel collapse, and battery life is astounding with it.
Code has yet to be committed, as he still has some work to do for the AUO panels (select RHOD100's basically) - so unless you have one of those you can reap the benefits of his new code .
(bzo got nearly 65 hrs with the radio on, sync off - 100% sleep.)
Looks interesting, but where do I download the latest version... I don't plan reading all the threads! And IF I installed would I loose all my settings and apps?
Update
It has been a while since I did all this tinkering, during which time there has been an update.
What I find I get is sometimes (c every couple of days) the meter says I have signal but nothing connects with a message "no network". Also, but far more frequent, as with today where it has occurred 3 times, I dial a number and nothing happens. It says ringing but there is no ring tone and it never seems to connect. I then shut the call down either by using the hang up button or the soft hang up key. The screen then changes to "Hanging Up" but again sits there indefinitely. The only solution id to do a restart.....
Any ideas?
PS: any news on when the bluetooth and camera will be working...?
I have found that any app that acts as a task killer of any sort (juice defender must in someway stop apps to save battery) can also kill your connection. I found this out while using xdandroid and it became immiediately clear when I stopped using the task killer my bars and data proved to be more consistant! Hope that helps.
-------------------------------------
Sent via the XDA Tapatalk App
I've been playing around with cm7 since release, internal build so I haven't run into the brick problem, but I have noticed a couple issues that I never had with a plain 1.4.0 rooted nook tablet.
First, I am losing wifi connectivity when I let the tablet sleep for more than a few minutes. Wifi will remain on, but just scans indefinitely while finding no networks. Sometimes I have to toggle wifi off and on several times before it starts working again. I have never had it lose connectivity while it was active and doing something, only when I set it down for several minutes and then wake it up.
Secondly the youtube app has locked up my tablet requiring a reboot several times. Sometimes this happens on the first video played, sometimes I can get up to 4 or 5 before the screen just goes black and all input is ignored. I would have left this info on the alpha release thread, but I can't post there yet and wanted to pass this info along. I'm having a great time fooling around with it, and so far these are the only issues I've noticed.
I haven't had the wi-fi isses that I've noticed. Only things I've ran into are those already being discussed in the dev forum - the near-brick experience and larger apps not installing.
In spite of almost bricking, I've still been using the alpha over the last couple days and am definitely loving the freedom and speed over stock. Can't wait to see how awesome it becomes with further development.
The wifi issue can be fixed by adjusting the settings. You just need to turn off wifi sleep. I think this is a long time cm7 bug and not unique to this build. I have reverted to stock for now so I can't guide you through it, but I am pretty sure it's an easy adjustment. (I couldn't go without hulu while in the middle of watching a series.)
StridAst said:
The wifi issue can be fixed by adjusting the settings. You just need to turn off wifi sleep. I think this is a long time cm7 bug and not unique to this build. I have reverted to stock for now so I can't guide you through it, but I am pretty sure it's an easy adjustment. (I couldn't go without hulu while in the middle of watching a series.)
Click to expand...
Click to collapse
Yep, you just go to Settings -> Wireless & Networks -> WiFi Settings then press the menu button. This brings up a small menu bar with two options. Tap "Advanced" and you can change your wifi sleep policy there.
imsoenthused said:
I've been playing around with cm7 since release, internal build so I haven't run into the brick problem
Click to expand...
Click to collapse
I believe the brick issue is in both the internal and SD release. Be sure to stay away from that SD card format button.
RadicalAns said:
I believe the brick issue is in both the internal and SD release. Be sure to stay away from that SD card format button.
Click to expand...
Click to collapse
Yeah, I'm not sure where the misconception that it's the SD-Card version causing the problem, unless it's just confusion because the problem was cause by an SDCard Format....I think the issue occurs in either, and I know for sure the internal is succeptible to it, because mine is internal and I was an early-bricker.
Ok, my fault for not being clear I guess. I have no conceivable reason to format an sd-card from within the cm7 alpha release so I have continued using it. Turning wifi to always on seems to have fixed my wifi issues, with a negative impact on battery life.
Youtube is still crashing my NT with regularity but that probably has something to do with the generally bad video performance.
imsoenthused said:
Ok, my fault for not being clear I guess. I have no conceivable reason to format an sd-card from within the cm7 alpha release so I have continued using it. Turning wifi to always on seems to have fixed my wifi issues, with a negative impact on battery life.
Youtube is still crashing my NT with regularity but that probably has something to do with the generally bad video performance.
Click to expand...
Click to collapse
Yeah, Celtic and Gonce are working on fixing the video drivers. Right now they're a bit iffy.
-Unable to install some .apks and some apps from the market.
-Color is weird in some games (like blue instead of green)
-B&N Nook app not syncing or not working at all.
I have not used Netflix on it yet so I'm not sure of the quality for that or youtube. I have no need to wipe SD card so will continue to explore any bugs.
youtube
imsoenthused said:
I've been playing around with cm7 since release, internal build so I haven't run into the brick problem, but I have noticed a couple issues that I never had with a plain 1.4.0 rooted nook tablet.
First, I am losing wifi connectivity when I let the tablet sleep for more than a few minutes. Wifi will remain on, but just scans indefinitely while finding no networks. Sometimes I have to toggle wifi off and on several times before it starts working again. I have never had it lose connectivity while it was active and doing something, only when I set it down for several minutes and then wake it up.
Secondly the youtube app has locked up my tablet requiring a reboot several times. Sometimes this happens on the first video played, sometimes I can get up to 4 or 5 before the screen just goes black and all input is ignored. I would have left this info on the alpha release thread, but I can't post there yet and wanted to pass this info along. I'm having a great time fooling around with it, and so far these are the only issues I've noticed.
Click to expand...
Click to collapse
I had problems with youtube too ... dolphin browser HD crashed when I clicked on a youtube link . Similar wi-fi problem too . Also the Wi-Fi indicator icon in status bar shows 1 or 2 bars after 10 min of active connection ....
Pretty stable otherwise . btw anyone tried 1080p mp4 videos in HW mode ???
Can someone please send me the internal build zip please
Sent from my BNTV250 using xda premium
CM7 beta bug report
Hello, I can't post to the development forum yet, but I thought the devs working on the next CM7 release for the NT should know about a potential bug. Also, I've only began using an android device about a month ago, so please forgive any noobish remarks. If after reading this, someone thinks it's important for the upcoming CM7 build release, please let someone on the development team know. Thanks.
I've been using an internal install of the beta build since it was released yesterday morning.
Everything has been working, very well, and I haven't been attempting to format sd cards from the device.
I've had one crash of ADW launcher when trying to add a playlist through the music player widget. I had a minor wifi hiccup that required toggling the wifi on and off to resolve. And a crash of the notification bar, when I attempted to click on an email notification message, which resolved by itself, seconds later.
The bug I'm most concerned about happened just about an hour ago. I noticed the battery getting low, so i plugged it in, powered on. It started charging, so i left it alone, a little while later, I looked at it, and the "n" on the charger had changed from orange to green, indicating a full charge. I awoke the nook from sleep to find that it was no longer charging, but that the battery was only about half charged. I unplugged it, and plugged it back in, but the status light was orange for only a second, before changing back to green, and no more charging.
I powered it off, and plugged it it (which of course made it turn back on /facepalm), but then powered it down through the power console as soon as CM7 booted. I has been powered off, and as far as i can tell charging normally, as indicated by the orange status of the charger's indicator. I intend to leave it powered off, and charging, until such time as the charging indicator turns green.
There may be some information here that is valuable to the Developers and you have attempted to articulate everything well.
However, is there some reason you chose to create a new thread instead of posting your issue In This One?
Perhaps the moderators can combine these threads but I'm sure the developers are more apt to look in one thread then trying to chase down multiple ones.
Good luck with your issues.
Aw crud. Totally didn't see that thread. If a mod could please combine, it would be appreciated.
Maybe the bug thread should be stickied?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
daedricgeek said:
I had problems with youtube too ... dolphin browser HD crashed when I clicked on a youtube link . Similar wi-fi problem too . Also the Wi-Fi indicator icon in status bar shows 1 or 2 bars after 10 min of active connection ....
Pretty stable otherwise . btw anyone tried 1080p mp4 videos in HW mode ???
Click to expand...
Click to collapse
I've been having crashing/force closes trying to stream video from sites like youtube.....but with a more mature content....if you know what I mean.
If I'm being too obscure....basically I can't stream porn onto it. Which, imo, is a device-killing bug!
(not really)
On the plus side, it seems like it charges pretty well through a USB connection now, where, if I'm not mistaken, it would not do so on stock. Although I only had stock for like 3 hours before zerging it, so I can't compare it very well....
I was also sitting up waiting on the release of this and have been running it every since then. the only real bugs I have seen is the unable to install alot of apps from the market as it gives the cant write to sdcard which is documented in the dev forums. my wireless does not seem to drain my battery much at all but the device itself never wanted to go into sleep mode unless I forced it into sleep. I changed the screen timeout and changed it right back and the issue resolved itself. Wireless does commonly go from full signal to 2 bars though but even when at 2 bars the connection seems fine and no loss of speed. as far as apps over 20 meg. the only ones I tried I had the apk file stored on my sd card and installed from there and they all installed just fine.
the device seems way more responsive now and I am absolutely loving it although i do miss the nook reader app itself and the one I downloaded from the market gives ab internal error : exception executing the command when I try and sign in Cant wait for the next release alpha or beta I would love to test it.
nocmadman said:
the device seems way more responsive now and I am absolutely loving it although i do miss the nook reader app itself and the one I downloaded from the market gives ab internal error : exception executing the command when I try and sign in Cant wait for the next release alpha or beta I would love to test it.
Click to expand...
Click to collapse
Go to the "Nook" folder on your sd card, then delete it. then try to sign in on the nook reader. This has worked for others who now have the nook app up and running on cm7
StridAst said:
Go to the "Nook" folder on your sd card, then delete it. then try to sign in on the nook reader. This has worked for others who now have the nook app up and running on cm7
Click to expand...
Click to collapse
Deleted nook folder tested same issue. Uninstalled the app and re installed it and now working thank you so much.
joecareytm said:
-Unable to install some .apks and some apps from the market.
-Color is weird in some games (like blue instead of green)
-B&N Nook app not syncing or not working at all.
I have not used Netflix on it yet so I'm not sure of the quality for that or youtube. I have no need to wipe SD card so will continue to explore any bugs.
Click to expand...
Click to collapse
Mostly I'm seeing the occasional app not installing. Every time it has been because "sdcard is not mounted". Even though it obviously it mounted. Aldiko reader is my current villain in this regard. No Wireless problems, but I changed the advanced settings right away. Interface is nice and fast.
Does anyone have any problems with installing games like need for speed
Sent from my PG86100 using xda premium
My issue is that I am constantly stepping outside, out of reach of my modem, and I'll have to turn my Wi-Fi off or my phone will stay connected to the the incredibly weak wifi signal.
So, I tried turning the dev option for "aggressive wifi to cellular handover" on thinking this would help and allow me to just leave wifi turned on while stepping outside and have it switch over to data without my assistance. And it worked, for the most part (it still held on to wifi signals *I* would deem too slow, but not often), BUT whenever I reboot the option in dev settings un-ticks so I have to go back in and turn the setting back on.
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Thank you in advance!
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Juggernaut79 said:
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Click to expand...
Click to collapse
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
6NomoN6 said:
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
Click to expand...
Click to collapse
For me it disconnects from a weak signal.
I'll be back!
6NomoN6 said:
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Click to expand...
Click to collapse
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! I'm googling now for a solution because going into developer options every reboot is incredibly damaging to the smoothness of the user experience I've worked so hard to customize.
Whether I find a solution or not I'll post in this thread again to let you know. If the latter is the result I will personally either write a tasker script, init.d script, or if nesseceary an Xposed module depending on factors I've yet to research. Can you Beta test for me if it comes to that? Maybe it's as simple as editing build.prop, I don't know yet, but I wanted to make this post ASAP so that you know you aren't alone on this and someone capable is working on the issue. For a developer like myself tapping menus every boot is unacceptable! Hopefully there is already a fix out there in the wild and I won't have to do any work.
P.S. Don't forget to also enable cellular radio always active for fast network switching at the price of some battery life. It's a few options below aggressive handover in Developer Options and thank jolly the setting is sticky unlike it's counterpart. Also, sorry for the poor turnout on your thread. I figured there'd be 100 posts by now, but at least you got my attention.
Edit 1: "setprop persist.{i-dont-know-yet}" in terminal emulator may do the trick. Checking for variables for the setting we want now. Hopefully they exist!
Edit 2: :laugh: I FOUND EVERYTHING I NEED FOR A FIX!!! However, an Xposed module will be required. I need some sleep but I should have something by tomorrow night. In case any other developers are reading this, here is the information required to make things work the way Iwe want them to:
http://android.stackexchange.com/qu...-cellular-handover-option-in-developer-settin
https://android.googlesource.com/pl...ndroid/settings/DevelopmentSettings.java#1061
Edit 3: Now that I know how this setting actually works together with wifi_watchdog (see source code WifiWatchdogService.java) I think I may have changed my mind regarding how to go about solving the root problem at hand (network switching) which this setting really does a "hack" job of taking care of. The developer that made it decided on a arbitrary, static number to be used for decreasing the connected WiFi AP's RSSI value (thereby making handover more "aggressive") instead of exposing any kind of grainular control to the user. So yes I could easily make the developer options setting stick but a much better approach would be to hook the method android.net.wifi.WifiManager with an Xposed module and implement additional logic to the network switching. The great thing about this method is there is the possibility for adding additional checks besides just periodically pinging the current primary dns server and monitoring the delay and timeout of the result. I also know for a fact modding the framework persists after reboot which is afterall all we originally wanted to have. The second or alternative route would be to edit the secure settings database using SQLite. The pro of this method is it is guranteed to be compatible with nearly ANY rom, won't break anything after an update, and doesn't use resources like an Xposed module. The con is that you are limited to the variables built into android, can't implement any new logic, and the worst is that I'm not even sure the modified tables would even persist after a reboot (or network state change for that matter) which if true would defeat the original purpose of this expedition. I'll make a fourth edit to this post after I've thought about and considered how to best proceede to reaching the goal of having a solution to our problem. :victory:
FoxysWorkplace said:
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! (...)
Click to expand...
Click to collapse
First of all, thank you so very much for looking into this!
I'm sorry for not responding sooner, but I had honestly lost hope of finding a solution to this issue mainly because I am not a developer myself and haven't the foggiest how to get started with it on Android
But when I opened my notifications and saw a response to this post (!) I got *extremely* excited, and as I read through your post, my excitement intensified to great happiness!
I can't express my gratitude, but I would be more than happy to help with anything that I can!
Any news on this?
Has anyone found a solution?
Had anyone found a solution that doesn't require root access?
Can we expect that fourth update any time soon? Any solution without xposed?
I'm following this thread in the event that someone finds a non-rooted solution. The Galaxy S7 really cannot be rooted without a serious performance hit (and yes I've gone through the two or three best/popular lag-fix solutions) but it works best in stock :-/