After the update a few issues have risen. I've attempted to search for solutions for each one, with no avail.
These are issues that never happened before the update, and started right on the next day.
1. Audio apps close when locking the screen.
When I have a podcast running (on beyondpod) and I lock the screen from the off button, the app will either keep running, or close.
I have found a few questions like this on here and other forums, but none with a definative answer.
I've done a few of the suggestion, like cleared the cache. But is there an actual solution to this?
2. Bluetooth turns off/loses connection to my pebble 2. I think these might be connected.
While using a bluetooth headset, there are no issues. However I constantly (should) have my pebble connected to my phone. However, very quickly it loses the connection. It randomly finds the connection again randomly, but it wont stay connected for very long. Sometimes I catch my phone with the bluetooth turned off, however turning it back on wont neccessarily connect it to the pebble. I also tested out with IFTT, and everytime the phone cut the bluetooth connection it woul send me a notification. And it happened multipe times within the hour. Sometimes taking tens of minutes to reconnect, sometimes not reconnecting it at all.
3. Google Timeline (the thing that draws a map of where you've been and how you've traveled)
I used this to follow my cycling and walking, since step counters dont recongnize cycling very well or at all. However since the update the pages are all empty. It just wont recognize my movement at all. I later noticed that the location gathering accesses had been reset, but even after giving them access again there is absolutely nothing saved onto my timelines.
Please, if you have any ideas what is doing this, or any ideas how to fix one, or each of these, leave a reply...
If nothing else I'll have to rollback to Marshmallow... And I've really grown to like the split screen!
hi, having same problem as #3 on my brand new Huawei Mate 10 pro. did you ever solve the issue? thanks
Related
Someone help if possible! My GPS on my Tilt was working perfectly with Google Maps and LiveSearch... but today i turned it on and it's locking onto a position about 500+ miles away. I have VisualGPS installed and it now is only locking onto a max of 3 satellites (but sees many more satellites) when it used to lock onto about 6+! It also thinks i'm at 57,000 feet and somewhere over the gulf of mexico when i'm currently in south carolina on a trip! I tried soft resetting about 5x and ran QuickGPS a few times as well... nothing has fixed it. Any suggestions?
did you install anything new or do anything major like settings or drop the phone?
Nope...it was working fine one day, and not working the next... phone wasn't dropped and no new software was installed and no settings were changed. Not sure if the chip is malfunctioning or not...but it does lock onto a location... the wrong location.... but it is consistently putting me in somewhere in alabama at the moment
Hi UTZorro
I can't really help you with your problem but I did notice on mine the other day that the satalites would drop in and out quickly and never lock onto more that 3. It was a very clear day with clear view of the sky. The co-ords were out by quite a long way because of it. The DOP was never very good. I restarted and it seemed to solve the problem but it wasn't a good sign. I know I hadn't dropped mine and the quickGPS data was current.
I also noticed that the voice in tomtom was all over the place.. I had to reinstall tomtom to fix the problem and put the voice on the main memory. At the time I thought it might be my 4GB SDcard but now I'm not so sure.
Dylan
Hi
Have you tried leaving it on for several minutes? GPS on these sorts of devices make several assumptions as they try to lock on quickly so you don't have to wait, sometimes that initial lock is wrong due to these assumptions. Either turn it on and leave for it around 10-15 minutes in clear view of the sky or try running QuickGPS, that may help.
I've had this happen now and again, just leaving it for several minutes to get a "proper" fix and all is well.
Regards
Phil
I saw the same problem, i was driving and according to my gps i was going 485 km/hr and i was "flying": above the sea. kept the copiliot log as thought it was funny
I rebooted my kaiser and it went back to normal
This randomly happens to me also on a Stock HTC rom. Not too often though so not a major problem.
Reboot fixes it ...
I had the same problem last week. I Soft reset the device and removed the battery before it booted back up. After about a minute I put it back in and it was OK again.
happens to me as well, soft reset solves the problem... also if you have your GPS app on your SD card removal fixes this as well, very peculiar problem
PhilipL said:
Have you tried leaving it on for several minutes? GPS on these sorts of devices make several assumptions as they try to lock on quickly so you don't have to wait, sometimes that initial lock is wrong due to these assumptions. Either turn it on and leave for it around 10-15 minutes in clear view of the sky or try running QuickGPS, that may help.
Click to expand...
Click to collapse
I second this: I had strange behavior after a lockup and it took several tries with 10minute or so open-sky accesses to clear up:
http://forum.xda-developers.com/showpost.php?p=1650269&postcount=31
Go sit on a park bench for 15 minutes or so with the GPS on and open in an app which shows the satellites in view - like TomTom/Mapopolis/whatever and see if you don't eventually get back up to the 7+ birds you normally get.
Good luck!
Richard
recently this error has been happening more frequently to me with TomTom, restarting doesnt seem to fix it all the time anymore... does anyone know what causes this? It constantly showes me somewhere in Ontario, Canada about 500 miles from where I actually am.
Is there a way to disable and re-enable the GPS chip via software similar to what a hard-reset does but without the 30 seconds+ downtime associated with the hard-reset?
This is being caused by Quick GPS. If you have not connected to the internet via Activesync for a while then when you first start your internal GPS or lose sat coverage it diverts to the last stored Quick GPS data for the most prominant 3 sats (they show up as full signal when you look a gps data in you mapping SW) that should be in your area.
Either sync at least every 5 days (on a PC with T'internet connection) or disable quick GPS and be patient for a lock.
Hope this helps.
Hi
I had the same problem, but it seems I found a solution.
I'm not 100% shure, but for what I remember I had this problem very often. like every time I was starting navigation it was wrong, so I had to soft reset - Everthing was fine - till next time when it was wrong again - and soft reset and again, again and agian.
It was so annoying - then on a Polish forum a guy wrote somethign about downloading quickGPS data (what he read here) and quickGPS was the solution, but for me it was to disalbe every sync function - because I set to sync evertime it was possible I believie that was it.
Now I'm using kaiser for about a week and testing it 2-3 times a day. and it never failed. I'm not 100% shure it was it - but it looks fine now.
So after a few days after I originally posted with this problem, it noticed it had spontaneously fixed itself after my flight back to town and I pinpointed what fixed it. (keep in mind i have stock Tilt Rom, QuickGPS was updated at the time (about 25x to be exact) and I had even hard resetted and it didn't fix it)... but here's what did fix it interestingly enough:
So, for some reason, if you have flight mode enabled on the phone, then you turn on the GPS (which I admit I did while bored midflight wondering how high up we were) it MAY get messed up like what happened to me. The only way to fix it is by putting the phone back in flight mode turning the GPS back on and then turning it off again and re-exiting flight mode. I have no idea why flight mode and the gps would be related in this siutation (it makes no sense to me)... I didn't believe it myself until I repeated this experiment twice!!! So, i'm posting this for reference to anyone who may have the same problem in the future if their phone was in flight mode and their GPS got activated and then subsequently messed up! Any thoughts?
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk
Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.
Quick back story, bought ZW3 and turns out it never made any sounds. Purchased a second one while the first went back to Asus for repair. When I got it back, I confirmed that it was working fine and then I shut it down, out it back in it's original box and put in closet.
After spending the normal time getting the watch and the phone to work as I wanted, I believe everything was working as it should. Then AW 2.0 finally came, and a little more learning, no problem. But then the phone goes to Android 8.0.0 and and I'm back to frustrations, such as no longer when you select your watch in the BT list of paired devices, does it say "connecting" or does the BT icon ever show it's connected, battery life now sucks, blah blah blah.
About 4 weeks ago, ZW3 #2 half the time the sound is low in volume and distorted like a severely blown speaker. So I shut shut it down and pull out ZW #1 and it doesn't want to connect to AW. Eventually I end up defaulting it but holy shizzle sticks! It takes forever to load ll apps and finally update to AW 2.0.... like more than half a day!
Now I bring you to yesterday and ZW #1 stops making sounds altogether AGAIN and on top of all that, I can't get either watch to be seen or therefore connected to AW on the phone. I have repeatedly uninstalled and reinstalled the app on the phone and 90% of the time it opens and sits on a white screen with the logo. Other times it goes to the "Set Up" screen and the first time I set the permissions and such, and after that it goes to the "Select your device" screen but never sees either one.
Now, if I "forget" the devices on the BT setting screen, it pops up with the request to pair and the code, but that makes no difference in AW functioning.
So, What little hidden step am I missing? I should be able to switch back and forth between to identically set up devices, or at least connect to one. So frustrated, plus now I have to figure out how to get Asus to realize that they didn't fix sh!t.
send all three in and tell them to give one good one.
You know you have to have both watches paired to phone, You cant just take second zw3 out and try to use it like it was the first one, do you? Yes? Ok.
Now if there is still problem:
1.Factory reset watch (unpair from phone from within the watch settings)
2.reset wireless connections on phone (will loose all wifi networks and BT paired devices)-but this helped me get rid of wear app misbehaving (like you wrote-forever sitting on splash screen,etc.),
3.clear data and cache of Wear app and then uninstall it
4.Restart phone.
5.Pair the watch.
Just wanted to ask if anyone else has this issue. Whenever I look to connect my Bluetooth headphones to the phone, it causes a freeze problem. This only seems to have happened the last couple of times I've tried it. Also, it only seems to happen when I've already turned on the Bluetooth setting on the headphones before I then search for devices on the phone. It gets stuck in some kind of freeze loop. Only way out is to try to hard reset the app. Initially, I panicked cos I can't pull the battery out.