I've been experiencing a strange problem on my phone lately (It's a Huawei Ascend G600 running AOSP-based ICS 4.0.4, rooted). None of the changes I make in the Settings app (such as toggling data, GPS, accessibility services, data format, anything) apply immediately. As soon as I back out of the screen, the changes get reverted.
However, if I restart my phone after changing them, the new values are applied. Any idea what could be happening? I'm fairly certain that this is a recent (a couple of weeks at most) occurrence. I'd use logcat but my kernel apparently disables logging (the log files are always empty).
Anybody? This issue is getting much too annoying. I managed to get logcat to work but am not seeing anything relevant in the logs.
Related
Hello all, new here, hope this is the right place for this post...
I have looked everywhere and can't seem to find anything relevant, so maybe someone here may have some insight. To start, it is (Kingo) rooted stock ROM android 4.1.2, build M36UP61, kernel 3.4.0, just to avoid confusion... Here's the issues numbered so I can correlate answers for each:
1) WiFi will occasionally drop, but the issue is that after (I assume) 5 retries, it leaves the AP as "disabled", and I want it to never do that, like my kyocera hydro, which relentlessly retries until it gets a connection to a known AP. Essentially, to never give up on a known AP for any reason, even if having to connect at least once first. I can find nothing in build.prop or sysctl that seems to relate to this behavior, unless I missed something. Additionally, WiFi will drop despite >-72dB signal unless I am actually watching the WiFi AP settings screen for some reason. I have made minor tweaks to build.prop, however this behavior was occurring prior to rooting.
2) I am getting what appears to be OOM-related FCs (no toast ANRs, just a halt back to launcher), yet with what should be enough RAM and spare CPU at the time. This behavior also prior to rooting, and have tweaked some improvement, but it is apparently not enough. I have not messed around too much with DavlikVM settings, as it still is as intimidating as sysctl for me as a newbie at Linux. I have tried to logcat, but can't get a dump at all, it just doesn't seem to log in time. Am I looking at the wrong log?
3) Touch screen locks, and takes all hardware function with it, even just on the home screen. Hardware power and volume don't respond and touchscreen coordinates are locked in place (I have show touches enabled) with no change in anything else; game/app keeps running smoothly, but is convinced that I have frozen holding (or not holding) my touches in place. Recovers in anywhere between 15 seconds to never, requiring me to pull the battery. Persistent after factory reset (did prior to rooting), occurs only when cfq(?) governor is topped at 1001MHz regardless of CPU load. Occasionally multi touch (max 2) fails intermittently, or averages between them (hold both ends and it shows one touch in the middle).
Just to add, any way to kill autocorrect's tendency to put the wrong word in place of a correctly-spelled one in its dictionary? (Changed dictionary to functionary for no reason, both in database). Also, smaller functions drop out, like WiFi icon stops responding, autocorrect suggestions disappear at random, etc.
Hi everyone.
I work in the support section of a small software company that supplies a software suite to hospitals, we have 2 PC applications and an Android application that work in tandem. At one of our sites they have been having an issue whereby some of their devices (Motorola Moto G2, Android 4.4.2) will randomly reset the date and time to random years (1970, 2040, etc) which is problematic as our software is a real time system that requires the use of time stamps from the devices. If they don't have the correct date and time then it can impact the way the software works, to the point where the devices will no longer connect into the system. I will also note that we use an application (SureLock) to lock the phone down so that it can only use our application.
I have tried several solutions to this problem, including making sure that the automatic date and time settings are not switched on, making sure that the batteries are not completely draining, etc. but have been unable to come up with a solution and I cannot find other users who have the exact same problem.
Some excerpts from my open ticket:
"...the issue was related to the date and time on the devices changing to random years (i.e. 1974, 2036, etc). This has been an issue in the past and so they now untick the "Automatic date & time" and "Automatic time zone" settings within android and set the date and time correctly which solves the issue. But the phones are still randomly changing their date and time even with those settings unticked."
"...We charge our phones fully every day, so it would be extremely rare for a battery to be fully drained. Think it must be something else happening."
"...
Motorola – Moto G – Android version 4.4.2
Date/Time not set to automatic – but we have noticed that this makes no difference – problem still occurs whether the automatic is ticked or not.
Issue occurs on random phones and at differing times of day."
"... Problem is still occurring but not so often. I was keeping a track of when it happened but there did not seem to be any pattern. The only thing I noticed was that one of our Operators who has a cochlear implant seemed to have it happen by far the most often. Could there be some interference from the implant?"
I found one other thread on another forum but it was in relation to the Samsung Galaxy Centura, and this was solved by either unticking Automatic Date & Time or checking the calendar application's time settings. I have tried both of these to no avail.
I am at a loss as to what to try next, any help or info would be much appreciated.
Hi guys,
First let me explain the situation: I've noticed recently that a lot of my apps, such as Gmail, Facebook Groups, Messenger and pretty much any app I need to have instantaneous notifications, aren't syncing properly. I might get notifications an hour or more after they are delivered. Even when I force-sync an app, such as refreshing the notification feed on Facebook Groups, there are delays that can go on indefinite until I get sick of waiting. I don't even know what the conditions are for this problem to occur because other times such as on WiFi, I have pretty consistent data syncing. Just a couple minutes ago I tried turning on and off airplane mode which seems to have fixed the issue. I'm going to see how long this lasts.
Here is the app I'm currently using that may affect data synchronization.
- Greenify: same problem persists regardless of settings and root. Haven't tried completely uninstalling it.
So just to be clear this issue persists from firmware to firmware regardless of Android version. I've had many android phones and am very aware of flashing procedures and all the ways to enhance my phone. My phone is unlocked and I flash firmwares using flash tool. I've tried fixing this issue by running rooted and unrooted to no avail. I've also taken all these apps out of the doze mode and turned them all on as priority.
Please let me know if you have any solution to this. It's costing me business.
Thanks!
Hello,
This has been an ongoing issue for months now and it's still unresolved. It affects large amounts of the playerbase, who run Oreo.
From what I understand, Google has made some changes to the Location API in Oreo and I suppose Niantic has failed to adapt to these changes in Pokemon Go.
The problem doesn't really concern outdoors location, that seems to work fine.
It's indoors, with no satellites in view, where it becomes a hassle.
Every 20-30 seconds or so, the game throws a 'GPS signal not found' error, which goes away in a couple seconds, and repeat over and over. This becomes extremely annoying and makes the game almost unplayable indoors, since that error blocks various actions in the game.
It feels like the game isn't getting location updates often enough from Google's High Accuracy Location Service (using Wi-Fi scanning for indoors location).
This is, however, not an issue on Android Nougat at all, everything works as it should. It's just some change introduced by Oreo causing this.
Now I know, that this is probably the developers' problem to solve, but anyone who has ever played this game knows that Niantic is... let's say special. This has been going on for months now and they haven't done anything.
Therefore I'd like to ask you - anyone with some developer insight - if there is perhaps any way, this could be fixed from my end.
Is there any way to make the Location Services of Oreo behave like on Nougat? Any system setting to change?
Among other things, I've also tried:
- making sure the game is set as 'Not Optimized' under battery optimization settings
- following this setting, trying to whitelist the game from background location throttling (just gave it a shot really, didn't hope for much, since the game has problems in the foreground as well)
- clean install of the system
I'm running the latest LineageOS 15.1 on OnePlus 3 (with root) personally - this issue is however persistent over a variety of devices that run Oreo - looking at one of the game's reddits
Any help would be much appreciated.
EDIT: This is also a non-issue on Android P. (tested on a friend's OnePlus 6 running it)
quick workaround
Set location to GPS Only, go near window to get GPS lock, and back inside.. no errors so far
Hi to all!
I have the Global Rom, as far as I know!
The phone is in original state, no unlocked boot, no root, no nothing!
Since it updated to the MIUI 10, I get a "malfunction" in the app update, whether it's thru the PlayStore or the MIUI's updating app.
When it senses Wi-Fi, the apps to be updated starts to loop between the "Downloading" and "Waiting" states, but none of them really starts the updating process.
And this is running in background, consuming the battery very rapidly!
In the PlayStore, I can stop the updating procedure, wait a few moments and click to update and then all goes well.
In the MIUI app, I can't do the same because, no matter how many times I click to stop, it doesn't and I can't kill the process.
The only way to stop it, is to shutdown the WiFi. But, as soon as I turn it on, resumes it's strange behaviour.
Would it be because I have a VPN connection always on?
Does anyone has the same problem?
As anyone solved it? How?
After digging a while, I've came to the following conclusions:
-the Xiaomi's update app, for their own apps, doesn't work with a VPN; I need to disconnect from the VPN and allow it to update on "normal" WiFi;
-the PlayStore does work, if I proceed like I've mention before;
Is this normal? Can I correct this privacy problem?
DHeart said:
After digging a while, I've came to the following conclusions:
-the Xiaomi's update app, for their own apps, doesn't work with a VPN; I need to disconnect from the VPN and allow it to update on "normal" WiFi;
-the PlayStore does work, if I proceed like I've mention before;
Is this normal? Can I correct this privacy problem?
Click to expand...
Click to collapse
I´m not familiar at all with this kind of issues, I just think you could start;
- By checking your region from additional settings so miui has different policies for some of them and I guess the apps are slightly different for some countries.
- If your VPN has random locations then this doesn´t match with your region settings.
- Clearing cache and data in updater and downloader manager apps.
- Giving only permissions as your convenience to these two apps.
- Like last resort formatting data in stock recovery.