Hello,
I'm actually CM 7.20 and thus completely satisfied.
Only 2 things "trouble" me.
GPS does not work. I GPSFix and GPS status. I will see satellites, is also well fixed, but my Garmin says he has no signal.
What can that be?
The second thing that strikes me ... my Legend reacts after running extremely slow. I close out the lock and it takes quite a long time to see the widgets on the screen, if I want to have another desktop, it takes too long until you see it.
Does anyone have any idea what could that be?
I did not overlocked CPU, and it do not run too many apps especially.
Sorry for Englisch....its translate with Google
Regarding GPS, have you looked at this link yet?
http://forum.xda-developers.com/showthread.php?t=1793698
You might find it very usefull.
Sent from my Legend using xda app-developers app
Hello,
thanks for the reply.
The thread does not help me really, the steps I've already been through.
Today I am with my Legend happening something. Since it is extremely slow over time I've asked the CPU to 768 (?) MHz and started the phone again.
Subsequently, all contacts were gone and I have the phone set up from scratch.
What have I done wrong?
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
Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
check your battery info,get cpuspy to see what speed your cpu has been going at and the deepsleep and betterbatterystats for wakelocks etc
this guy has similar issue
http://forum.xda-developers.com/showthread.php?t=1571518
i already checked with all mentioned tools.
strange thing is there is no wakelock... it's only when screen is on but application is in background.
i have this problem on different ICS Roms. at the moment i am on cm9 and it is still present. when i check with "top" in terminal i can see that facebook.katana is at the top keeping the cpu pretty busy.
with samsung roms and the original samsung task manager i can see that it's always using over 50% cpu power.
i tried older versions. tried deinstalling. nothing helps.
i just dont know what it is doing in the background. cpuspy shows me that the cpu is mostly in 1ghz and deepsleep.
edit: i double checked and its also killing deepsleep. sometimes it enters sometimes not...
pmcee said:
Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
Click to expand...
Click to collapse
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
NothFlo said:
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
Click to expand...
Click to collapse
It happens to me on cm9 also... Every ICS Rom.
So No one has a solution for US?
Just to let you guys know that this also happens on my Nexus S with ICS 4.0.4 stock
In fact it happened also with Gingerbread... it started happening when Facebook made a major app overhaul to what is currently the new "user experience" for the past 4-5 months or so... that's when Watchdog which I have installed suddenly started complaining
Sorry for digging out this bit older thread, but have you found a solution yet ? I got the same problem since i changed to ics roms - first sammy leaks, then official, now nightlies. Tried wiping cache, dalvik, userdata, reinstalled app, ... to no effort.
Thinking about coding a facebook-killer widget. Take a look on this screens, 2 hours of cpu time for nothing...
Sent from my GT-I9100 using xda premium
I just use Watchdog what normally complains about Facebook a few minutes after I stop using it. Then I just kill the process from within Watchdog.
Using the browser is fine though.. however some things don't work so well in the mobile browser version.
To me this problem is quite symptomatic however from what I read on the internet it doesn't happen all the time.. even sometimes for me it doesn't stay clogging the cpu but most of the times it does.
I guess they will fix it one day but I wouldn't hold my breath that it will be soon. I read that on the iPhone the way they designed the app is pretty bad (it's sort of a skin over the actual mobile website). For Android it might be the same..
That the facebook devs are coding big BS (sorry) is really known.
Can you provide me a link to the google play site of Watchdog ? Too many results, i don't know which one... thanks
Sent from my GT-I9100 using xda premium
Here! This is the one I use
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite
Thanks.
Which modem do you use ? I am on XXLPS, and afaik with XXLPQ i did not have the problem - will try at home
Edit: tried, the same with lpq...
Sent from my GT-I9100 using xda premium
I'm using the XXLA2 radio that came with the yakju update. But I got the same problem with the XXKK6 yakjuxw radio
smells more like programmer error than phone configuration..
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Seems that it's a problem with the official ICS ROMs. Try Friendcaster and see if that's any better.
drizzle1 said:
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Click to expand...
Click to collapse
Theres a funtion which kills a process if you hold the back key.
i360* said:
Theres a funtion which kills a process if you hold the back key.
Click to expand...
Click to collapse
even by closing with a short press on the back button it will end the process
i uninstalled facebook for this
friends caster is A LOT better than facebook app
personally I didn't like Friendcaster. It was smoother in operation that Facebook's official app but it had some quirks (now can't remember them but there were a few things you couldn't do as opposed to FB's official app). But what stopped me from using it was the extended awake times I was getting even without automatic refreshes set up.
Haven't got a single problem
Sent from my GT-I9100 using Tapatalk 2
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'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.