[Q] android most annoying bugs - Sprint Samsung Galaxy S III

hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A

1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing

CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....

nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.

tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds

Related

[Q] How to modify radio CDMA parameters?

I have been having a lot of trouble with my Epic's radio behavior since the EC05 radio update. It seems that the normal Samsung "radio stupidity" that I have seen in several of their devices is worse than ever now. The best radio for call performance I have used so far was DG27's (though not data). Essentially, what it is as far as I can determine by using utilities to monitor radio operation, is poor CDMA handoff configuration.
What it does is, for no good reason, switch from a cell site providing a good signal level, to one providing a bad signal level for no reason. Either this, or it holds onto a weakening set of towers while moving, until it goes out of their range and the call drops. The phone will then display the no service message for a few seconds, and then will pick up perfect signal from a different set of towers. I can even watch this happen by driving down a given road while on a call, with another phone in my cup holder. The Epic will start to break up and show very low signal levels, while the other is doing perfectly. Additionally, the direction you drive down this (2 lane) road also has an effect.
I have fixed this before on non smartphones by altering some of the CDMA radio values. T_Add, T_Drop, T_Comp, T_Tdrop. My solution is to increase the threshold on T_Comp a little bit, and drop the T_Tdrop also a little bit. The problem is that I cannot figure how to do this on this phone. Very little radio information seems to be available, and the utilities I have do not work completely on this model.
This issue with how they program their radios seems to be a common Samsung problem, to a much greater degree than with other manufacturers. Sanyo, Palm, and Motorola seem to do a much better job with this, even in cases where they use the same radio chipsets.
I am feeling like a lot of people will find this matter interesting and/or of benefit to resolve.
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
Sent from my SPH-D700 using Tapatalk
Maybe try ##3282# or *#147852#
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
musclehead84 said:
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
It isn't the data driving me nuts. Data sessions pick up again quickly. It's the dropped calls. Either way, it is partially a symptom of the same problem. The phone is promoting weak towers, sometimes in favor of strong ones, to the active set - which it should not be.
MysteryEmotionz said:
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
...
Click to expand...
Click to collapse
No and yes. CDMA support was a hack in versions prior to 2.0. Android 2.0 (and later) has inbuilt features intended to support CDMA networks. Some of the companies are still using some legacy code, and some of nomenclature used within the system parameters still reflects GSM however.
This, however, is irrelevant in my belief. I do not think that these parameters are a function of RIL, as RIL is simply the intermediary between the "computer" and "telephone" components in a smartphone. I believe that these issues exist purely, or nearly so, within the "telephone" section of the device.
running_the_dream said:
Maybe try ##3282# or *#147852#
Click to expand...
Click to collapse
What is this ##147852#? I cannot find it in any information I have, and it has no effect on the phone itself.
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
running_the_dream said:
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
Click to expand...
Click to collapse
Yes, totally misread that. Nothing seems to apply however, as I do not think it is a software parameter on the phone end. The WiMAX radio is software controlled, through a driver in the operating system. The combination of CDMA radio and baseband processor are more or less an independent device which essentially lives on its own, with its own configuration. It is told what to do through the RIL, which is a piece of software that allows the computer aspect of the phone to talk to the radio, passing it instructions which it then acts upon according to its own programming and configuration. The RIL also allows the radio to communicate its status to the rest of the system.
I am really thinking that this will not be a setting that can be modified from within the phone itself, but will require some external involvement, similar to QPST. On this chipset, however, QPST does not appear to be able to manage these parameters.
If you find out any more info please pass it along. Thank you.
Sent From My Evo Killer!!!
Ah that's really interesting. Wish I could help.

Model iterations & WIFI Problem

I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
cognus said:
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
Click to expand...
Click to collapse
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Aerowinder said:
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Click to expand...
Click to collapse
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
cognus said:
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
Click to expand...
Click to collapse
Well, as far as how many there are? A LOT! LOL! I'd imagine a few hundred thousand US variants, and for the T999 and its variants, close to a hundred thousand maybe? I really don't know, and those numbers did not come from anywhere but my head!
But as far as manufacturing, I am pretty sure they are all built in the same place. But, this does not mean that all of the components are from one location. In fact, from batch to batch of the same part, it can vary by where it was made, but also by what company made it. This is unlikely when dealing with the critcal parts such as the SoC, but the WiFi chip is a Broadcom chip. I have no idea if there are multiple manufacturing locations for it, but it is possible. The memory in all devices often varies greatly by the manufacturer.
Anyway, I do agree with Aerowinder. It is most likely hardware related. I'd look into a Warranty or Insurance exchange.

Note II Bluetooth issue

Trying to find a kitkat ROM that supports Voice dialling via Bluetooth on my note II sgh-i317m. If I role back to 4.3 it works fine (like DN3). I am currently testing CM11 and it does not work (unless somebody has a work around)
Most bluetooth functions work fine except voice dial. I hit voice commands on my Jabra and it does hear my commands. I also tried a Motorla bluetooth device and experienced the same.
Moved to Q&A.
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
FYI, over the last few days, I installed both Official AT&T / Samsung KitKat 4.4.2 and Ditto Note 3 v5.2 (based on 4.4.2) and they both properly support Bluetooth audio and microphone for voice command after a button press.
AT&T / Samsung Official:
Unfortunately comes with a version of Google Search (v.3.6) that provides the terrible Google Voice Dialer in response to a bluetooth button press, so if you were planning on using that, be prepared to root, move it from /system/ to /user/, uninstall, and then go find and install Google Search v.3.4.
S-Voice works fine, but you may need to switch your APN from "phone" to "nxtgenphone," if you haven't done so already. Else, S-voice may only work on wi-fi, not mobile data. Check out the thread on doing so here:
http://forum.xda-developers.com/note-3-att/general/psa-s-voice-stops-volte-markets-using-t2848929
Ditto Note 3 v5.2:
Comes with Google Search 3.4 which gives correct "Listening.." when bluetooth button pressed. Be sure to uncheck auto update in google play store until Google gets their crap figured out. Phone will flash as N7105, so download and use the build.prop for i317 from their extra files and turn on the telephony.lteOnCdmaDevice=1 setting. Set also ro.product.locale.language=en_US and ro.product.locale.region=US since you're an AT&T customer. You'll also need to add the nxtgenphone APN as above, I'm afraid. It's not rooted as it comes - use your recovery to flash the SuperSU binary of choice from your SD card after installation if you want root. It all works, though, and is my OS now.
rmzalbar said:
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
Click to expand...
Click to collapse

how do i help fix this [wifi with many same SSIDs]

Ok let me start my wifi at any normal sports works fine, however at work i can not connect.
Before we start the usual "reset the router" or "its your networks admin, he is MAC address filtering", no they are not, I asked and my galaxy nexus/nexus 4/nexus 7 never had not a single problem with connecting. Or anyone with acurrent android smartphone, or iphone, or the odd guy out with a windows phone
While i am noticing that its not android version issue, as 4.3 stock color OS has this issue as do every 4.4.+ rom has this too
I believe the problem is our phone will get confused with which access point to connect to as it sees many (and we only see one), is this a kernel issue as i am guessing all the devs are pulling all the good bits from oppo for hardware support
Question is how to I help fix it
BrianDigital said:
Ok let me start my wifi at any normal sports works fine, however at work i can not connect.
Before we start the usual "reset the router" or "its your networks admin, he is MAC address filtering", no they are not, I asked and my galaxy nexus/nexus 4/nexus 7 never had not a single problem with connecting. Or anyone with acurrent android smartphone, or iphone, or the odd guy out with a windows phone
While i am noticing that its not android version issue, as 4.3 stock color OS has this issue as do every 4.4.+ rom has this too
I believe the problem is our phone will get confused with which access point to connect to as it sees many (and we only see one), is this a kernel issue as i am guessing all the devs are pulling all the good bits from oppo for hardware support
Question is how to I help fix it
Click to expand...
Click to collapse
Unfortunately, while it may not be an issue on other devices, there IS something weird about your network and I don't know what.
I can't reproduce the multiple SSID problem when I open up wifi settings to scan for networks at work - I see one entry per SSID even though I KNOW there are multiple APs.
Our kernel drivers come from CAF - https://www.codeaurora.org/cgit/qui...b496862222c0a89d&id=LNX.LA.3.2.5-00210-8x74.0 (that tag matches the CAF tag Oppo based their platform bringup on.)
Entropy512 said:
Unfortunately, while it may not be an issue on other devices, there IS something weird about your network and I don't know what.
I can't reproduce the multiple SSID problem when I open up wifi settings to scan for networks at work - I see one entry per SSID even though I KNOW there are multiple APs.
Our kernel drivers come from CAF - https://www.codeaurora.org/cgit/qui...b496862222c0a89d&id=LNX.LA.3.2.5-00210-8x74.0 (that tag matches the CAF tag Oppo based their platform bringup on.)
Click to expand...
Click to collapse
this is troubling then, if your connecting fine to a similar network then I might be up ****s creek with connecting. Thanks for the info

SOS! Please HELP - XM10T5G Down[&up]grading..

Have the Xiaomi Mi 10T 5G, which comes with Android 10 / MIUI 12 [Sort of combination of them i think], and i wanna install an older version of android only, lower than 10 [Preferably 7.0], is it possible to do at all? If so, then how exactly can i do that? if possible with exact instruction or guide to it..
Thanks ahead..
PEACE AND LOVE!
Not possible. I am really curious why would you even want that.
_mysiak_ said:
Not possible. I am really curious why would you even want that.
Click to expand...
Click to collapse
For many reasons.. They changed it in some very bad way for my opinion.. like the auto turning on WiFi by some apps, like some apps that don't have widgets, the call recording issue and many more very annoying unreasonable changes they did on A10 on.. saw also they only allow FBE encryption instead of FDE which is much better [That i can see for huge 128, 256 or maybe 512 Gigs Storages but still it should be up to the user decision not forcing]
So you say it's completely impossible? even if flash universal / rooted ROM? no way at all?! cause man those are really annoying stuff especially to the tech Pros and/or savvy's like us, and i know that since i saw many threads and posts in other forums about those issues too.. Maybe some giving up or thinking it's advancements, but really, maybe big money involved, espionage, and many more possible reasons they doing it.. It's bad, really bad..
* BTW sorry for the multiplication threads didn't knew it's SPAMing and not very involved it forums world..
Thank ahead.
Jeff1976A1 said:
For many reasons.. They changed it in some very bad way for my opinion.. like the auto turning on WiFi by some apps, like some apps that don't have widgets, the call recording issue and many more very annoying unreasonable changes they did on A10 on.. saw also they only allow FBE encryption instead of FDE which is much better [That i can see for huge 128, 256 or maybe 512 Gigs Storages but still it should be up to the user decision not forcing]
So you say it's completely impossible? even if flash universal / rooted ROM? no way at all?! cause man those are really annoying stuff especially to the tech Pros and/or savvy's like us, and i know that since i saw many threads and posts in other forums about those issues too.. Maybe some giving up or thinking it's advancements, but really, maybe big money involved, espionage, and many more possible reasons they doing it.. It's bad, really bad..
* BTW sorry for the multiplication threads didn't knew it's SPAMing and not very involved it forums world..
Thank ahead.
Click to expand...
Click to collapse
To be honest I don't understand none of your points.
1. Wifi can be still turned on by apps, you just need to enable the permission (allow always vs. allow only when app is running in foreground).
2. Call recording is working in regions where it's not forbidden by privacy laws.
3. FBE is much better because it allows you to start the phone with basic service without using the password. Not sure why do you consider FDE to be superior.
4. Well, you can try to build your own Android 7 ROM from old sources, but you're going to have a fun time adapting to vendor partition/proprietary files created for Android 10 or 11. Also using several years old code which is not supported or patched anymore is quite interesting approach to security.
_mysiak_ said:
To be honest I don't understand none of your points.
1. Wifi can be still turned on by apps, you just need to enable the permission (allow always vs. allow only when app is running in foreground).
2. Call recording is working in regions where it's not forbidden by privacy laws.
3. FBE is much better because it allows you to start the phone with basic service without using the password. Not sure why do you consider FDE to be superior.
4. Well, you can try to build your own Android 7 ROM from old sources, but you're going to have a fun time adapting to vendor partition/proprietary files created for Android 10 or 11. Also using several years old code which is not supported or patched anymore is quite interesting approach to security.
Click to expand...
Click to collapse
Maybe it's regional or SROMs based issue, but the vendor of the app said it's not allowed on Android 10 and on, and i did confirmed the permission to turn on WiFi automatically, but maybe there's some other settings that i missed and that guy was wrong, i'd love if you can show how to enable it globally and/or to just the auto file sync i use, cause i tried many times even with manual syncing [by clicking the Sync button when WiFi is off, it started and turn it off automatically on Android 7.0.. Of course also for time interval based sync]..
Jeff1976A1 said:
Maybe it's regional or SROMs based issue, but the vendor of the app said it's not allowed on Android 10 and on, and i did confirmed the permission to turn on WiFi automatically, but maybe there's some other settings that i missed and that guy was wrong, i'd love if you can show how to enable it globally and/or to just the auto file sync i use, cause i tried many times even with manual syncing [by clicking the Sync button when WiFi is off, it started and turn it off automatically on Android 7.0.. Of course also for time interval based sync]..
Click to expand...
Click to collapse
App info, permissions.
_mysiak_ said:
App info, permissions.
Click to expand...
Click to collapse
Hi.. Thanks for your reply.. i did that already before, but still it doesn't work.. i use FolderSync, that currently in my old Android 7.0 device, does syncing when i click Sync from within the app, while i was totally offline [Data and Wifi] so it turned on the Wifi connection [Specific home network], and also on Scheduled i inserted the Allowed Networks SSID [Which BTW when i turn on WiFi manually and it does sync it with GDrive, it say on top 'Unknown SSID' for case it matters {Had the feeling that it very much does}], I also switced it on in Data and WiFI limit it does on that Security app, which i guess is kind of firewall, and BTW i remember like 5-6 years ago i had the Lenovo A8 "Golden Worrier" has that same kind of Security app built in with firewall and all that, but still manually at least, as i checked, it doesn't turn on the Wifi via FolderSync app.. Got a strong feeling it's due to that Unknown SSID stuff or that Security app.. Could it be?..
Jeff1976A1 said:
Hi.. Thanks for your reply.. i did that already before, but still it doesn't work.. i use FolderSync, that currently in my old Android 7.0 device, does syncing when i click Sync from within the app, while i was totally offline [Data and Wifi] so it turned on the Wifi connection [Specific home network], and also on Scheduled i inserted the Allowed Networks SSID [Which BTW when i turn on WiFi manually and it does sync it with GDrive, it say on top 'Unknown SSID' for case it matters {Had the feeling that it very much does}], I also switced it on in Data and WiFI limit it does on that Security app, which i guess is kind of firewall, and BTW i remember like 5-6 years ago i had the Lenovo A8 "Golden Worrier" has that same kind of Security app built in with firewall and all that, but still manually at least, as i checked, it doesn't turn on the Wifi via FolderSync app.. Got a strong feeling it's due to that Unknown SSID stuff or that Security app.. Could it be?..
Click to expand...
Click to collapse
FolderSync doesn't turn Wifi On automatically, this feature seems to be missing in the app. But I've just tested with Tasker and it is able to turn Wifi On and Off, so it's not a problem of Android version.
For Allowed SSID feature in FolderSync you must enable permanent location access.
Btw. I see no point in turning Wifi Off at any point, it uses so little power that there is next to none benefit in doing it. If you insist on some kind of automation, use Tasker in a fully controlled manner.
_mysiak_ said:
FolderSync doesn't turn Wifi On automatically, this feature seems to be missing in the app. But I've just tested with Tasker and it is able to turn Wifi On and Off, so it's not a problem of Android version.
For Allowed SSID feature in FolderSync you must enable permanent location access.
Btw. I see no point in turning Wifi Off at any point, it uses so little power that there is next to none benefit in doing it. If you insist on some kind of automation, use Tasker in a fully controlled manner.
Click to expand...
Click to collapse
Well your first argument is actually not tru, FolderSync does turns on Wifi automatically as i do for like 4 years with my older Galaxy s6 [Great dev BTW, Samsung's first 64 bit device i thinks] running now Android 7.0, and also the other day and im sure if ill try this right now it will actually turning on WiFi from off mode and also automatically closed it when done syncing, but no matter what i did it doesn't doing it on the XM10T5G, and it both updated to the latest FolderSync version the one with those tiles.. so it must be something with the operation system.. again it's some kind of Andro/MIUI OS so it has to do with one of them..
About the SSID, i did confirmed the location access all the time [not just when it's used] on the Security app, is there any other place that i should enable location or any other settings that may be relating to this?..
And really? you don't see the point in using Wifi? It's much more faster, secure, and reliable than data.. of course i don't care if it'll be 4G or 5G even better to sync, but obviously not any connection, but thanks for the Tasker Tip, i'll try that.. i've heared that somewhere i think from the gut of FolderSync..
And BTW, the call recording is legal in my country, so i did also many years but here only after trying several apps i found Cube ACR working good.. And also, some apps ask you if you confirm that Call recording is legal in your country but of course if you flash custom or different ROM, the system obviously can never tell..
Peace..
Jeff1976A1 said:
Well your first argument is actually not tru, FolderSync does turns on Wifi automatically as i do for like 4 years with my older Galaxy s6 [Great dev BTW, Samsung's first 64 bit device i thinks] running now Android 7.0, and also the other day and im sure if ill try this right now it will actually turning on WiFi from off mode and also automatically closed it when done syncing, but no matter what i did it doesn't doing it on the XM10T5G, and it both updated to the latest FolderSync version the one with those tiles.. so it must be something with the operation system.. again it's some kind of Andro/MIUI OS so it has to do with one of them..
About the SSID, i did confirmed the location access all the time [not just when it's used] on the Security app, is there any other place that i should enable location or any other settings that may be relating to this?..
And really? you don't see the point in using Wifi? It's much more faster, secure, and reliable than data.. of course i don't care if it'll be 4G or 5G even better to sync, but obviously not any connection, but thanks for the Tasker Tip, i'll try that.. i've heared that somewhere i think from the gut of FolderSync..
And BTW, the call recording is legal in my country, so i did also many years but here only after trying several apps i found Cube ACR working good.. And also, some apps ask you if you confirm that Call recording is legal in your country but of course if you flash custom or different ROM, the system obviously can never tell..
Peace..
Click to expand...
Click to collapse
I see no point in turning wifi OFF.
Anyway, good luck finding/building your perfect Andoid 7 ROM.
_mysiak_ said:
I see no point in turning wifi OFF.
Anyway, good luck finding/building your perfect Andoid 7 ROM.
Click to expand...
Click to collapse
Again security and energy reasons.. Think about it..
Anyway i barely know how to flash ROM, so i'm very far from building a custom one.. But at start you said it's impossible to install / flash an older Android ROM to it [XM10T5G], so you say it's possible with custom ROM?
Jeff1976A1 said:
Again security and energy reasons.. Think about it..
Anyway i barely know how to flash ROM, so i'm very far from building a custom one.. But at start you said it's impossible to install / flash an older Android ROM to it [XM10T5G], so you say it's possible with custom ROM?
Click to expand...
Click to collapse
Again - not possible, such ROM doesn't exist.

Categories

Resources