Hi all,
Problem with the GPS on my Orbit 2! Though so far I love it to bits really.
I have done a search here but cant find anything.. I really hope it is just me asking the wrong question. Anyway someone must know something.
The problem is this:
The GPS with Copilot was working amazingly when I first got it. I was knocked out by it.
I haven't used it much but when I have I was delighted.
However, recently I have been noticing that the number of satellite signals has been going down. It has also been taking longer and longer to get a fix.
Today I could not use it at all, even when it got a "fix" It was showing me no where near the right road.!! Have some satellites fallen out of the sky!!??
Currently it has 3 days before I need to do the QuickGPS thing. So that should be ok.. I will try again with the update but is there any known problem with the GPS. If there are problems with GPS do they normally behave like that or just stop altogether?
If there is a problem I guess I need to send it back.. :-(
Thanks in advance for any help anyone can give.
Its very painful when you get up in the morning and try to depend on something that is not working!
3Frog
Same problem
I also got the same problem, but I found out that a reboot solved the issue. After the reboot it found the satellites again.
Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...
Hi All,
I am having an issue with GPS on my TF101. ive tried a few different Team EOS and CM roms but doesnt seem to have an effect. I am currently running EOS 81 (last EOS that still works with wiimote). I just get no satellites connected. Below are two logcat logs, one from K.A.T when i try to install the GPS quickfix i get an error, then the other is starting GPS Status.
Im starting to wonder if my GPS is actually broken and it's not a software issue.
Please help, even if it is just to say my GPS is properly shagged.
K.A.T log:
http://pastebin.com/svPCVbYY
GPS Status log:
http://pastebin.com/sYdVfCBX
Edit:
I just tried EOS 113 and the K.A.T. GPS Fix installed successfully, however still no luck in GPS status. Logcat:
http://pastebin.com/4CCQzgjc
Strange not to get any fixes at all, mine takes a while but does eventually lock on
When you say K.A.T, do you mean KatKernel or the Kat-App ?
Kat-App has some GPS fixes in it
And not to sound arrogant but you are trying to get a fix outdoors under a clear sky ?
#
I'm not great with logcats, hopefully a dev will have a look at them for you
*Detection* said:
Strange not to get any fixes at all, mine takes a while but does eventually lock on
When you say K.A.T, do you mean KatKernel or the Kat-App ?
Kat-App has some GPS fixes in it
And not to sound arrogant but you are trying to get a fix outdoors under a clear sky ?
#
I'm not great with logcats, hopefully a dev will have a look at them for you
Click to expand...
Click to collapse
Hey,
Thanks for your response.
I mean the KAT-App, it has a GPS fix that wouldnt apply but i eventually go it that working. it didn't however fix my issues.
As for clear sky, apart from the crappy UK cloudy weather i'm all clear sitting outside on a bench (and within wifi reach, winning!).
Im starting to think its a hardware failure but not sure how to test.
Thanks,
Piercy
Piercy0812 said:
Hey,
Thanks for your response.
I mean the KAT-App, it has a GPS fix that wouldnt apply but i eventually go it that working. it didn't however fix my issues.
As for clear sky, apart from the crappy UK cloudy weather i'm all clear sitting outside on a bench (and within wifi reach, winning!).
Im starting to think its a hardware failure but not sure how to test.
Thanks,
Piercy
Click to expand...
Click to collapse
Don't forget the tf101 was always plagued with a crappy GPS. Some say the aluminum case, some say weak signal from the hardware. There are tweaks and such to the GPS.conf file but I gave up on it.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Don't forget the tf101 was always plagued with a crappy GPS. Some say the aluminum case, some say weak signal from the hardware. There are tweaks and such to the GPS.conf file but I gave up on it.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
yeah, it's a shame cos id love things like google now to work. Plus i wanted to try ingress and as im stuck on this crappy iPhone for a couple more months it would of been nice to get it going.
Ah well, back onto 4.1 and using it as an emulator
Thanks all that tried,
Piercy0812 said:
yeah, it's a shame cos id love things like google now to work. Plus i wanted to try ingress and as im stuck on this crappy iPhone for a couple more months it would of been nice to get it going.
Ah well, back onto 4.1 and using it as an emulator
Thanks all that tried,
Click to expand...
Click to collapse
Until I went back to stock and started over with root and flashing a new ROM, I had the same exact issues with GPS. I know it sounds strange; but, after a year plus of flashing, my system was laggy, the GPS would never work, and had intermittent sound issues. While that may be more than you are experiencing, it still may be an issue. So, after making a huge mistake of wiping everything off my system (no ROM at all) and having nearly having an expensive paper weight, I went back to ground zero. After the process of going back to an Asus stock ROM, rooting, and flashing Team EOS, Kat Kernel, and the Kat app, my Transformer was better than new. GPS works perfect, sound has no issues, no random reboots, and blazing fast.
So, it might be worth a try of starting entirely over... just a thought. :silly:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.
Bump for update, anyone else experiences with new maps?
PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.
I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app
Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.
It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2
possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.
Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.
same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..
Calls drop often. Usually within the first minute, and then every time when Im calling back after 10sec. The phone itself does not lose signal. Strange thing is, if I'm getting phone call after first/second drop, phone continues connection without problems... But Only when Im receiving a phone call not when Im trying to re-call someone.
- I tried replacing my sim and the issue persists. No problems with other phones using this Sim (even in the same locations).
These are pretty annoying issues. Anybody else experiencing them? Is there a different radio I can try for the phone? Is there any log I can access showing a reason for the call drop, or any trouble shooting I can do? This seems to be independent of WCDMA Only/Preferred/GSM/WCDMA (Auto) settings. Or if, how to change these settings?
Note: This has nothing to do with the network. I've been with the same company (Orange Europe) for about 2.5 years, and have never had this happen before. This has been consistent since I got my OnePlus (about 1 week ago)
That's true. I'm experiencing this as well for quite some time now. At first I joked and said: Hey, the NSA joined our conversation.....again. But after some time it really annoys me. This has nothing to do with the ROM or kernel as I have tried out various combinations. What I found out is that it got better after I returned to stock CM 11s with stock kernel. But it's not gone completly.
Honestly I neither know how to fix it nor what is causing the problem. Try to reflash the CM11S 25R firmware and see if it gets better. I think something is wrong with the modem software since CM11S 22R,25R and CM11 builds are using the same modem software. Maybe the announced update for the end of this month or early next month will fix this. I really hope so because a phone which is not able to hold a call, can't be considered as a real phone.
Oh im pitty You, If You'll get something just please let me know. Any advices or help will be appreciated. Maybe waiting for new CM relase will solve the problem, I do rly like this OS even with so many bugs... there is always an option. Move to stock 4.4 published by OP on official website.
Anyone else facing the same issue? Was there ever a fix for this issue? I'm on 38R and still encountering this issue
Same here.
See this thread for answers and work around. No solution as of yet.
http://forum.xda-developers.com/oneplus-one/help/dropped-calls-weak-lte-signal-t2916659