I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
nu Maps stinks on Rezound
I unwisely installed the new Maps from Google Play Store.
It forgot my Favorite places and cached location. Experienced
poor location finding and not-fun routing to locations.
After hating it for a week, I searched for Maps 6.14.4.apk
and installed it with Root Explorer. I am very glad to have
a good working version of Maps running again now.
dbighead77 said:
I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
Click to expand...
Click to collapse
To be honest google has been messing up alot of things for the Rez lately and maps being one of them....no matter what kernel you are on or what rom you are on its not gonna fix this maps issue...personally i prefer waze as it is not only free on google play but just works alot better and are even more up to date than google maps....plus it has many cool features like it lets you know if theres a cop or accident up ahead...also to note theres a gps test app out there that gives you a much better lock on your gps so it wont loose its signal as much
I have the same flickering issue until I close the app and reopen it. Seems to work fine after that.
Related
Hi,
I have an issue with the way 2.1 roms handle background processes. Using Cronos 1.4.1 at the moment but the issue is the same in every 2.1 rom I've tried. The issue is not there in 1.5 roms.
In the car I like to run Spotify and CoPilot at the same with Spotify in the background over A2DP. When I do this the music from Spotify starts breaking up and becomes unlistenable. I can fix this by turning off the screen but it starts again when the screen is turned back on. CoPilot isn't a huge amount of good without a screen so this is a pretty bad workaround. I wouldn't complain and just chalk it up to underpowered hardware but I never had this problem with the 1.5 roms.
I've tried overclocking but that doesnt help at all. At a guess I would say that the scheduler is effectively choking Spotify when it's got a another app in the foreground (it isn't just CoPilot that deprives Spotify but most programs that have constantly running processes i.e. games). Web browsing only breaks up the music during page loads.
Is there a way of telling the scheduler to give Spotify a greater or equal priority to foreground apps? Is this something that BFS will solve (or make worse). Is it possible the official kernel will make a difference?
Any help will be much appreciated.
Cheers,
Phil
PS: Apologies if this belongs in the general forum but I thought this is more of a development issue.
You can always try setting a `nice`/renice constant.
I have exactly the same issue with spotify, it seems to have very low priority, I don't know if this is a problem with the spotify app or the way in which android 2.1 deals with it but it does seem to be throttled to the point of stopping when you try and do anything else with your phone while running it.
It didn't appear to be an issue on any of the 1.5 roms and seems to be a lot worse on a Sense 2.1 rom (I don't know if that is because there are a lot more things running in the background)
I used a the "top" command within adb shell and could see that other process, some htc and some standard android were jumping up the cpu usage way higher than spotify and this seemed to cause the music to break up.
I really hope that if the official 2.1 version is released, whatever is causing the issue (sense, android or the spotify app) is fixed!
EDIT: for some reason, trying to load up web pages makes it stutter like crazy!
Hi,
adwinp: you clearly know more than I do. How would I go about setting that?
DarthOps: I'm glad that I'm not the only one that finds this frustrating. I'll check to see if the Music app behaves the same way or if it's just Spotify. If it's just Spotify then maybe it's worth raising a bug report with them. Have you tried it recently in a 1.5 rom? Wondering if the later versions of Spotify still behave fine in 1.5.
Cheers,
Phil
Hey.
I have the same issue with all 2.1 roms. I'm currently using cronos 1.4.1 and it's a bit better than with other roms.
I guess we'll have to wait for the official eclair release before raising a bug report
With 1.5 there's no problem.
I'm using app2sd, are you guys too ?
Yup, but I am pretty sure I've had the same issue using non app2sd roms. I'm trying that scheduler hack somebody put up on the forum, will post my results in a sec.
Update 1:
All the tests were done with Spotify over headphones and not A2DP. Going to test that on my way home in the car.
Spotify and Torque (OBD app that is constantly running and uses BT), saw a possible improvement in that it took a good half a minute before Spotify started breaking up but then it was as bad as before.
Spotify and CoPilot are playing nicely together in the office but the real issue is when the map updates (i.e. moving). Will test on my way home.
Spotify and web browsing: loaded bbc.co.uk and Spotify didn't stutter once.
Spotify and Frozen Bubble: No stutter at all during playing.
This could actually be a workable solution and is promising that maybe BFS based roms will work.
Could you give us some informations about how to do this hack ?
herman3101 said:
Hi,
adwinp: you clearly know more than I do. How would I go about setting that?
DarthOps: I'm glad that I'm not the only one that finds this frustrating. I'll check to see if the Music app behaves the same way or if it's just Spotify. If it's just Spotify then maybe it's worth raising a bug report with them. Have you tried it recently in a 1.5 rom? Wondering if the later versions of Spotify still behave fine in 1.5.
Cheers,
Phil
Click to expand...
Click to collapse
You have to edit your initrd (init.rc) and rebuild your boot.img
You have to find out the resource # of the process choking the system and reduce its nice, and upp the one being slow, for example.
The arguments of setrlimit: resource current max
Sorry, should have said. http://forum.xda-developers.com/showthread.php?t=689829 has all the details.
Turn usb debugging on and open an adb shell to type in the commands from the post above or alternatively use the gscript method (didn't work for me on Cronos 1.4.1, the SU request FC on me).
adwinp: Wow, think that might well be beyond my capabilities. Is there any way to edit that in adb? Also it's not one program being "nasty" but rather Spotify being too "nice" .
Ok thanks a lot, I'm gonna give it a try
I find that I tend to get stutters when the phone changes between 2G and 3G connections too, I remember some Droid users reporting the same problem
DarthOps said:
I find that I tend to get stutters when the phone changes between 2G and 3G connections too, I remember some Droid users reporting the same problem
Click to expand...
Click to collapse
Change your band to WCDMA only:
open dialer, and:
*#*#4636#*#*
Be sure you have good 3G coverage in your region first!
Unfortunately the scheduler hack doesn't fix this for me. Tried it in the car going home and still got lots of stutter when running CoPilot. Possibly a bit better than before. Tried with and without A2DP and it made no difference. Back to the drawing board I guess.
herman3101 said:
Unfortunately the scheduler hack doesn't fix this for me. Tried it in the car going home and still got lots of stutter when running CoPilot. Possibly a bit better than before. Tried with and without A2DP and it made no difference. Back to the drawing board I guess.
Click to expand...
Click to collapse
Are you going to raise a bug with Spotify?
Moved as not ROM Dev.
Just tried with the official release, it's worse than with cronos droid.
Back to cronos...
Hey guys,
am I the only one who thinks that Google Maps has gotten slower and laggier on our Galaxy SII with the ICS-Update?
Panning and Scrolling is a little choppy and the device gets very warm when using Google Maps for more than a minute. I tried to do some investigation and found out that the Latitude process is really heavy on the CPU, which might cause both issues.
Im using the latest Google Maps on the LPQ rom, and though this is not a dealbreaker, it's just not the way it's supposed to be for me.
PS: I'm not using Google's Latitude service at all, but i guess the latitude process is also used for locating you on the map.
Well I can say that yes, it does take some good seconds to switch to that Auto rotation mode (don't know the exact term), but otherwise it's OK. Besides it's not ICS but the app itself may not be well compatible yet!
Yes, it is slower on ICS for me too.
well, good to know it's not just my phone then, let's hope this will be fixed with an update soon, or maybe someone smarter than I will find out what's the cause
Installed CM10-20121205 and the latest GApps. Did not restore any apps or data using Titanium. Flashed to s-off using DirtyRacun method.
Wiped System->Factory Wipe->Installed CM10 Rom->Installed GApps->Rebooted
Alright, so I did all of that and everything seems to be working fine. However I still feel as though the phone is behaving just as badly as it used to with regards to multi-tasking. I'll give two examples with my favorite browser (Dolphin) and music player (Poweramp).
The browser issue I don't think is anything the folks here won't be familiar with. Use browser, exit browser for a bit, return to browser only to have to reload all pages/tabs. Annoying...
My next example involves the Poweramp widget. I listen to a lot of MP3s that call for a functioning bookmarking feature. I like/need to be able to resume tracks where I left off when pausing, putting the device to sleep for later use. When resuming a track by going to the Poweramp app ->Now Playing->Unpause it resumes just fine. If I unpause from the widget on one of my home screens it almost ALWAYS restarts the track from the beginning. This happens with both long (4 hour) mp3s and short songs (2-3 minutes).
Perhaps someone could explain why that's happening? It doesn't appear after about a day of use that the phone is any "better" for multi-tasking. I've heard input from some folks describing this as unusual and others saying that Android is just sort of like that. I don't know. I just sort of got it in my head after hearing so many people complain about how this phone (Sense) handles multi-tasking that I thought flashing to a new rom would fix the problem.
If this is a case of lofty expectations it would be super to know. That way I don't go flashing to a hundred different roms to fix a problem that isn't technically considered a problem by anyone other than myself.
(2)
Second question! I've had no trouble using most every app that requires SU permissions (Titanium BU notably). However I've noticed that I am constantly having to grant SU permissions to apps even when I tell SU to remember my preference to allow. I've also not been able to get Wireless Tether OR WiFi Tether for Root Users to work correctly. I tried FoxFi and that seems to work just fine but doesn't require root (and costs money for the good version.
Any input would be vastly appreciated. Thanks!
Edit: I didn't see the "Is this post a question?" icon before posting this thread. I do apologize! Any input on this matter would be greatly appreciated. This forum and its community have been invaluable up to this point in my making my phone my own!
Just flashed over the MeanRom ICS and having the same problem.
I don't have that many widgets. Weather widget not on my home screen, power settings widget, power amp, and Google Search.
Wireless and WiFi Tether not working. Perhaps there's something wrong with how I rooted my phone? However, I ran a "root checker" app that came out okay, and my phone says s-off when in recovery mode.
It sounds like you have too many apps installed that run as services and are hogging memory. You can use an app like OS Monitor to see what's still active in memory and how much it's using up.
Just tried using the McTweaker Root app cynic method to fix multi-tasking and it unfortunately still seems broken. :/ I'm at a total loss.
xHausx said:
It sounds like you have too many apps installed that run as services and are hogging memory. You can use an app like OS Monitor to see what's still active in memory and how much it's using up.
Click to expand...
Click to collapse
Tested this theory but it doesn't really hold water. I'm not running that many apps all things considered, and I was having this problem when it was fairly app free...
Oi vey this is frustrating. I've spent the better part of a long ass time.
Hey all, wondering if anyone can shed some insight for me on this. HTC Rezound running CM 10.1.1 downloaded the .apk file to install the latest and "greatest" google maps v7.0 and I was having some issues the first day and uninstalled/reinstalled a few times. Just took this video (sorry for awkward quality never videoed myself on another phone before =P) of me just moving the screen around and how it's tearing etc. I also went to the settings menu and it was tearing as well. This also happens on the navigation portion as well, just in the time being (at work) just threw this together real quick.
Any insight would be great! Maybe others are having this annoying problem too =/
Thanks
Video Link
UPDATE (7/11 - 2:36pm): Enabled "Force GPU rendering" in developer options and still have disable HW overlays, haven't had as much of a problem as I did in the video above. Will keep testing it though. I feel that the gpu rendering option did help a tremendous amount as well. I also set my CPU governer to "interactive" instead of "ondemand" and raised the max to 1620MHz up from 1512MHz. Will update if I don't experience anymore issues or do =P
Update (7/11 - 3:42): still having the issue app can be restarted and sometimes work right but will soon stop working properly again...
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Omg. I hate the new version. I'm can't come to grips with loosomg built in latitude either. Any heros out there care to post the last non 7 version here?
Sent from my ADR6425LVW using xda premium
Just Google "Google Maps 6.14.4 apk" and you will find tons of places to download it, it is all over the web on almost every APK repository.
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
gleggie said:
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Click to expand...
Click to collapse
cool, thanks.
When I'm Navigating, the "Turn right in 5 miles" panel keeps flickering every time the map center updates, and each time the panel flickers off, the map panel expands to compensate, then shrinks back when the panel reappears. Sometimes when this happens, the map panel has artifacting, and it gets pretty hard to navigate certain roads I've never been on before.
The flickering rate appears to be about 2-3 times a second.
acejavelin said:
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Click to expand...
Click to collapse
Waze works great still.. just saying.
Same problem on the HTC Desire HD with CM10.1, Jellytime or CodefireX rom.
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk