I have an SGS2 running KJ3 firmware with speedmod 2-17test.
I have a mandatory security lock set which locks the device after 10 minutes. The corporate rule is I believe less than 30, but the system settings dialogue doesn't allow anything above 10 minutes.
Since a alpha pass is so annoying, is there any manual way to modify this setting higher (I'm not switching rom though). I am rooted
Related
Is anyone else seeing a large amount of clock drift on their thunderbolts? I gain 122 seconds a day and 14 seconds at every boot according to ClockSync. ClockSync has been keeping my system clock corrected to date and I suppose that works but still, 2 min a day and 14 seconds at a reboot? That seems to be an awful lot.
So, is anyone else seeing this?
TB - Rooted, Das BAMF 1.4 but not OC'd.
mezman said:
Is anyone else seeing a large amount of clock drift on their thunderbolts? I gain 122 seconds a day and 14 seconds at every boot according to ClockSync. ClockSync has been keeping my system clock corrected to date and I suppose that works but still, 2 min a day and 14 seconds at a reboot? That seems to be an awful lot.
Click to expand...
Click to collapse
There's the actual time, there's Linux system time, there's the time kept by the RTC hardware, and there's cellular network time. They're all a bit different.
Clocksync is an NTP client, and tries to keep Linux system time in reasonable sync with external NTP servers, which should be in reasonable sync with the actual time (UTC). That's all on the order of milliseconds, if everything is working as it should.
CDMA and LTE network time is required to be in close sync with UTC, too - on the order of microseconds. This is a better source than a remote NTP server. In fact, some Stratum 1 NTP server get _their_ time from a CDMA network.
Most CDMA phones get their time from the network, and I suspect the TB does, too. I don't know if Android uses the kernel time discipline to keep the system time in sync with network time, I suspect it does.
I doubt Clocksync does anything good on a CDMA/LTE phone, the time received from the network is better, and probably being used to begin with. As I recall, GSM/UTMS base stations only need frequency accuracy, so Clocksync is probably useful there.
The difference you're seeing on boot is probably the difference between RTC time and system time, after the latter has been synched with network time. The RTC is only there to keep time when the device is powered off, so not much money is put into keeping it accurate. A CDMA/LTE phone is expected to be getting time from the network while in use.
So you're saying that I shouldn't be using ClockSync then as it's setting my system time different than the CDMA/LTE time my TB should be getting from the network? Or is it just redundant and unnecessary?
Also, I could see the RTC being 14 seconds off network time but once the phone is up and connected to the Verizon network, shouldn't it sync it's time with the CDMA/LTE time? Until I force ClockSync to update the system time, it remains 14 seconds off from NTP time, regardless of time since the phone booted.
It appears that Android may be setting system time to match GPS time. See the issue discussed at code.google.com/p/android/issues/detail?id=5485
Huh, that's a good read. Seems that no only is Android setting the time to GPS time, but doing it incorrectly. I guess though, if I turn on my phone in a building where it can't get a GPS signal, will my phone sync the system time to GPS time next time it can see the sky?
I've installed Lotus Traveler and IBM Endpoint Manager apps. Both are required for me to be able to get my work email on my phone. Both contain security features. I've discovered that issue in my prior thread regarding changing the clock on the lock screen (well, the lack of ability to do, so is more precise) is directly attributed to these apps (I believe that someone had a similar issue due to the security "features" of MS Exchange server, too).
My phone is currently rooted, unlocked and running TheBase 0.7.2. The only issues that I'm having is that I am having another security conflict with the lock screen. This time, it's the ability to set the timer to a value besides "immediate" (which is quite inconvenient, when you have to enter an 8byte PW that meets company standards). I can uninstall/deactivate the Traveler app and the settings are available, but once I reinstall/activate the app, the choices disappear and the setting reverts back to "immediate".
Now the truly odd parts:
1) 2 1/2-3 days after I install/activate Traveler, the time out selections reappear and I can set the timeout to values between 30 sec and 28 min.
2) The lock screen setting for a timeout that does not lock out, not requiring a password, have reverted to the default, phone settings (so I essentially have 2 different lock screen set ups, 1 for when the screen deactivation exceeds the time limit and 1 for when it doesn't).
Anyone have thoughts on how I can "fix" these oddities or is this just something that I'll have to live with? (btw... going back to stock step up is definitely not an options, I'll live with the quirks, if I have to).
Hi,
Since two weeks I'm having GPS lock problems on my Samsung Galaxy SII. It had been working fine for two years.
I'm not sure if it's related to the 4.1.2 upgrade I did two weeks ago.
If I go outside and start any sport tracking app I almost get instantaniously a GPS lock. Opening GPS Fix shows 11 satellites and 9 satellites with a lock.
When I start the sporting activity after a variabel number of minutes (could be 12, could be > 30 minutes or could be even > 60 minutes) I get a GPS signal lost. Opening GPS fix shows a large number of satellites but no lock. At that point rebooting the phone (but this is not an option while sports tracking) is the only solution.
I've tried everything related to this subject. (factory reset, playing with the Google location services, etc). The only thing I haven't done is downgrading the Android version.
Any thoughts on this subject?
Thanks
Try a clean install of the stock rom you're currently running (get one from Samfirmware), then try downgrading (not 4.0.4 tho). Or perhaps try a custom rom/kernel ?
Hi all,
I have an AT&T Samsung Note 3 SM-N900A running Android 4.3 (baseband version N900AUCUBMJ5, kernel v3.4.0-1625098). I rooted it using Kingo, installed Tasker (with Secure Settings plugin), and created 2 profiles: one with a 'Home' location context, and one with a 'Work' location context. In the 'Location Edit' map screen for each, I set a pinned location w/ a radius of 200m. I also de-select 'GPS' (leaving only 'NET'), since I don't want GPS enabled all the time (to extend battery life). I confirm that these work when I'm actively using the phone.. the profile becomes active when I'm at the specified location (as expected). I know it's active because it's displayed in the Notification Panel (and it's also shown in green in the Tasker profiles list).
The issue I'm having is that after ~10 minutes of idle time (i.e. when the display is off and I'm not using the phone), I find that the profile is no longer active when I turn the display back on and start using the phone again. I confirmed that this *doesn't* happen after 1 minute, 2 minutes, nor 5 minutes… only > 10. I also confirmed that it happens for both profiles consistently. However, as soon as I start Tasker again from the Apps Drawer (or from Recent Apps screen), the profile is immediately activated again, and my Enter task is re-run.
I enabled the run log in Tasker prefs, but it basically shows a clean activation of the profile (with no warnings or anything that looks weird to me).
I know there's a 10-minute timeout in the Display Off Monitoring prefs, but that doesn't seem to be related to my issue. I tried reducing the All Checks Seconds from 600 to 90, rebooted the phone, and it still took ~10 minutes before the profile would become inactive after the phone being idle.
Any thoughts as to what the culprit might be? Are there any system logs I can look at that might shed some light here? I'm new to Android, and this seemed like the place to ask..
Thanks.
Ok, not solved..
Alright, bumping this, as the problem is back again after some time.
Has anyone ever seen Tasker exhibit the behavior I described? Again, I start the phone and Tasker profile is active, let the phone go idle for >10 minutes, the profile is no longer active and I need to restart Tasker manually to make it active again.
Still trying to figure out what logs are best to look at..
I have tried now on two newer Android phones (Huawei Mate 20 with Android 10, Samsung Galaxy A7 2018 with Android 9) what happens if I track my position with GPS and then stop for 30+ minutes.
The result is every time, on both devices, that the GPS signal is lost after stopping for 10-30 minutes, and it is not regained without manually waking up the phone (wakeup Apps don't work, moving again doesn't work).
This happens with all tracking apps I've tried (about 10); I tried the different location modes; I have turned off ALL options which are for power saving, for all apps; I even deinstalled PowerGenie and the SystemManager on the Huawei device via ADB. Therefore, this is definitely NOT a problem of settings, nor of a specific firmware.
I now suspect that the aggressive "Doze" feature that was introduced in Android 6 is responsible for this. So is there any way to completely disable it?
I want that GPS tracking will continue regardless of whether I move or not, will always try to reconnect when signal is lost, until the battery is at 5% or less - without me touching the phone even once after starting the tracking app.