I am not sure if its related to the rom or maps but since i flashed the rom (when it came out) I havent gotten a chance to use the map feature until today. When i navigate, it showed me the correct way even the turn by turn movement on the map BUT the voice was telling me something else. And it got stuck, repeating the same thing over and over. I exit the app and restarted it again and its does the same thing. any ideas?
DroidForums.net | Android Forum & News
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
AOKP Rom and Maps issue
- Thread starter ntrddragn
- Start date
GalaxyFlatulence
Member
why use Aokp? they've been on build 1 forever. flash jb sourcery, cna, or xenon. much better at this point. more features and no map probs with either.
Last edited:
Try uninstalling and reinstalling the app?
AOKP is a great ROM, been running it since release too. Stable, quick, and everything else expected of AOKP.
didnt want to start another thread so..
Dezymod, is your nexus running hot? mine is running pretty hot. I have it set at 1.3 MHZ max and 1.2min, governor = performance, IO scheduler cfq (not sure what is does), and everything else is default from the rom. i tried to set it to 1.2 max but it run hot also.
cupfulloflol
Senior Member
didnt want to start another thread so..
Dezymod, is your nexus running hot? mine is running pretty hot. I have it set at 1.3 MHZ max and 1.2min, governor = performance, IO scheduler cfq (not sure what is does), and everything else is default from the rom. i tried to set it to 1.2 max but it run hot also.
How hot is pretty hot? There are tons of things that could come into play here. Radio issues, app issues, settings issues, issues with ROM/kernel, ambient temperatures....etc
Given the information you have given, I would start with settings. The performance governor locks your device into the max speed at all times. Use a less demanding governor, interactive perhaps, and lower the minimum clock speed and your temperatures should go down and your battery life should go up.
Edit: Ideally you want to use as conservative of a governor as you can stand to use, as it will help save battery. Some governors are a little too conservative for a lot of usage. Interactive is probably the default on most kernels, and is kind of in the middle, leaning more toward performance than battery savings. Kernel devs have made their own tweaks to governors (which I discuss in the thread I linked below), so this may not be entirely true for all kernels. Generally, I think most people would be best with interactive. If you don't care at all about battery life, and your device isn't getting dangerously hot, then performance is fine choice as well.
Your scheduler shouldn't be a problem here, unless the kernel dev has modified it somehow and made it unstable.
http://www.droidforums.net/forum/galaxy-nexus-kernels/221485-kernels-cm10.html <-- I made a couple posts there giving a general overview of some of the terminology of kernels, and linked to a couple threads that went into detail about governors and I/O schedulers. If interested those threads (not so much my ramblings) are decent reads, even though they are for another device.
Of course it could be one of many other things too, or perhaps a combination of things.
Last edited:
Nope, never had an issue with my Nexus running hot.didnt want to start another thread so..
Dezymod, is your nexus running hot? mine is running pretty hot. I have it set at 1.3 MHZ max and 1.2min, governor = performance, IO scheduler cfq (not sure what is does), and everything else is default from the rom. i tried to set it to 1.2 max but it run hot also.
Right now still on AOKP with Franco kernel on 1.3Mhz max and 234mhz min on lazy governor. I'm been doing alot of testing of kernels, governors, and speeds lately and found this to be the best so far (in terms of battery life), though I only made these settings last night. So far it's provided the best battery life and no issues with lag or anything.
And as Cup said, your Nexus running hot may be due to other issues.What kernel are you running? I've had bad luck with Franco in the other times I used it, but so far so good.
thanks guys. when i say hot is around 123* surfing the web or talking, when its plugged in at night its around 79*, in my pocket its 90ish. I am using the kernel that came with the AOKP rom, i think. I dont remember flashing a separate kernel.
You're pretty close or even at the temp where there should be some concern, I forget if it's 120 or 125, either way you're close. How long are you surfing the web for and how "heavy" are these sites?
syndicate0017
Silver Member
Why do you have your min set so high?...
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
+1Why do you have your min set so high?...
Sent from my Galaxy Nexus using Tapatalk 2
This could be the reason why your phone is running hot. If it's idle state is 1.2ghz that'll drain your battery fast and warm up your pocket quite fast as well.
cupfulloflol
Senior Member
I find that if it low, I find it take it sweet time waking up. Can't have that when I'm surrounded by 9 iphone users. Lol... I guess I can lower it and see.
So its 125* now. 30 mins of reading on the forum. And I dropped the min to 800.
120 is fairly hot, I personally wouldn't worry too much at that temp, but I still wouldn't want it to stay there for an extended time. If it goes much higher like to say 140ish, I would definitely start worrying, as I believe that is what the CPU is rated for. Realistically it can probably handle more than that, but definitely not for an extended amount of time. Personally I wouldn't be happy with 120 for any extended period of time, especially if I was doing simplistic tasks like just browsing a forum for a few minutes.
If you are still using the performance governor, you can drop the minimum to zero or even a negative number and it wouldn't matter. The performance governor locks your CPU into the max slot regardless of what is happening. The only other slot it may hit is deep sleep, when idle, but that doesn't matter if you are using the device for 30 minutes straight.
Theoretically if you use the interactive governor, you shouldn't see lag unless you have some sort of intense setup. Process intensive widgets, animations, live wallpapers....etc Interactive should ramp up to higher speeds pretty quick. Perhaps give a different kernel a try. Tons of options out there, some with different governors or tweaked versions of governors. LeanKernel, Franco, Trinity, Glados, Air, KernelSanders, or even newer Faux kernels (this is what comes with AOKP, but there are newer versions). Definitely missed some that I can't think of off the top of my head. Also if you are feeling adventurous, give the kernel/governor some tweaks. You can make a governor more performance minded or more battery conservation oriented with a few tweaks. There are also some tweaks you can do for each kernel (these depend on which kernel you choose) which can possibly make a difference.
I am tired, so I apologize if this post doesn't make any sense and/or has typos (essentially been typing this with one eye open haha).
OP take a look at this thread and it'll help explain what governors are and what each of them do: Android CPU governors explained - Android Forums
Similar threads
- Replies
- 3
- Views
- 3K
