Ever since the last update to maps the navigation gets stuck on the start up screen and vibrates constantly. I thought it might be because i was running cm7 so i flashed back to stock, 2.2. I still had the same issue so i tried 2.3.5, no change. I am currently back on cm7. I was wondering if anyone else was having this issue. Hopefully it's a simple fix, I rather enjoy that app. Thanks in advance.
I had this issue as well. The newest maps update (6.0.1) fixed it for me.
If it doesn't fix it for whatever reason, you can get around it by opening maps first and then opening navigation from there, but an update should help.
had the same thing when running CM7 nightlies, updating maps and changing to ICS worked mine out just fine.
Related
Some time after I upgraded to froyo, i started finding my phone switched to vibrate mode few times per day. I haven't touched anything, it just goes to vibrate without obvious pattern or reason...
anyone else?
p.s.
i've installed quite few programs since the upgrade as well, so cant be sure its froyo...
but dont feel like uninstalling one by one to locate the problem...
I'm running Froyo leak from day 1 and never occurd this issue. Froyo is running perfectly some problems with few apps but not that big. It has to be a app that you installed.
No problems here with things changing that I didn't change.
Hello,
I'm using the latest Google Maps version on my Nexus One. I regularly get a message saying "Memory is Low, Traffic is disabled".
This is quite odd because I quickly go into my memory manager and see that in this case (and 2 others since Sunday), there are about 210 MB of RAM available.
Anyone else experiencing this?
I'm seeing the same thing on my Evo running cyanogenmod 6.0. Sometimes it happens at all zoom levels, sometimes not all for several days. I can't pin it down. Restarting doesn't seem to help either, & I have the maps update from several days ago installed. I haven't tried flashing back to a Sense ROM, though.
I haven't seen much talk of the problem on google looking back several months.
Setting the VM heap size back to 24m fixed this for me on my N1 running CM6 final.
It's in Settings > CyanogenMod Settings > Performance Settings.
Thanks, dlee. I reduced the heap size from 32 & rebooted, but I still have the problem. Traffic is almost unusable. It will sometimes be ok for a minute, but once it happens the first time, it then happens again within seconds. I haven't tried flashing a nightly since I don't want to worry about backing up and redoing settings. I don't recall ever seeing this on a sense ROM, but I updated my google maps around the time I installed CM6. I'll try flashing back and checking again.
UPDATE: Same thing running Vaelpak sense ROM. Turning on the terrain layer seems to make it happen more quickly.
Hi All
I have yesterday updated my T-Mobile UK Galaxy S to Froyo using the regedit method.
All seemed good and I was very pleased with myself for doing it!
But....
Since the upgrade I have had many Force Close's and there seems to be a fair amount of lag.
The main issue is the messaging app opens but when you go to open a message it FC's.
I am running Launcher Pro so will try running standard Samsung launcher for a bit.
Anyone else had this?
Do a factory reset!!
Yeah I too had loads of problems after the upgrade like you. Very slow, crashing, reboots. Although TWlauncher never worked properly for me before, even on 2.1.
Did a factory reset using the 3button reboot and it's been fine since. I was surprised that this didn't clear the memory card, so still have all my files - which I wasn't expecting.
Thanks guys that did the trick.
And forced me into a bit of phone housekeeping as well!
Hi Guys,
My camera has stopped working. It only turns on when it's on the car dock plugged in.
I have latest Cyanogen Gingerbread, latest radio, and camera just doesn't turn on. It hasn't turned on since Froyo, just very wierd.
Any idea's how to fix or troubleshoot?
gadgeter_1977 said:
Hi Guys,
My camera has stopped working. It only turns on when it's on the car dock plugged in.
I have latest Cyanogen Gingerbread, latest radio, and camera just doesn't turn on. It hasn't turned on since Froyo, just very wierd.
Any idea's how to fix or troubleshoot?
Click to expand...
Click to collapse
have you tried clearing data/cache for the camera app? main phone settings, applications, manage applications, all, camera....
Use the "get back to stock" thread. That's all I can think of.
Have you dropped the phone at all?
So wait, you mentioned it didn't work since Froyo, and now it doesn't work on CM7? Presumably, you did a full wipe. And it still doesn't work? That's weird.
Like wdfowty said - try going back to stock.
Also, wrong subforum.
Yes I've always wiped, and it stopped working since Froyo. It works whenever it is on the car dock plugged in which is very wierd. But when i try to start it, the screen goes blank and it just sits there. Then I get the force close option or wait.
Really frustrating... :-(
Where is the get back to stock thread?
Dropped the phone few times, but it works in the Car Dock no problem.
I had similar issue when I install an incompatible kernel with Cyanogen Mod. Although obviously you're using CyanogenMod's default kernel, but do try a latest kernel for CyanogenMod and see if it can help.
Pershoot's kernel for CM:
http://droidbasement.com/db-blog/?p=1533
Wildmonks:
http://wildmonks.whoisthedrizzle.com/kernel/2.6.35/010611/
IntersectRaven's:
http://www.mediafire.com/intersectRaven (sort by date)
Is there a kernel that is compatible for CM7? I kind of don't want to go back to Froyo...
I'm having the exact same problem; no camera, no torch. Any help would be greatly appreciated
CM 7 Nighties #18
Honeybread theme with minimalist icons
2.6.37.3_CAVS-CM7-NOBOOST_CFS_20110312_2317 Kernel
Mine -
Camera NOT working
Flash IS working.
if my camera broken, should the flash broken as well???
2 separate items i guess.
DONE!
no issue anymore with the camera on Nexus One.
How ?
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
Go back to Stock ROM
FRF91 or lower.
only then flash back ur fav ROM
Click thank you if u appreciate it!
Does anyone have a suggestion on how to get Slacker to work on nightly #32? I have uninstalled, reinstalled, fixed permissions, moved to SD etc, and still get force closes. When I reinstall it gets to the login screen and I put in the info click on sign-in and screen goes dark about 30 seconds later get force close menu.
I am now on rc4 and still having the sane problem any help would be appreciated.
The latest update from slacker seemed to fix the issues for me on phiremod 5.2
Thanks, that did the trick. They must of released a updated version since the last time I tried.