this happens to me as well, I have never really worried about it, I just turn it off once it has booted up.
Upvote
0
Do you have an app that could be turning it on, like juice defender or Superpower?
this happens to me as well, I have never really worried about it, I just turn it off once it has booted up.
i installed juice defender just to look at it and uninstall again
do you think that did it/
please advise.
If it still does it after the uninstall then no. I was just thinking how juice turns the radios on and off for you. But since it's gone then disregard.
anyone else having issues with google navigation ???
anyone else having issues with google navigation ???
Is this the first time you tried navigation since flashing MikFroyo?
yes, i was just reading through the forum and found someone having issues so i tried.
i installed 4.5.1 and it worked but before that i uninstalled 5.0 using TI and then reinstalled from market but still it did not work. i downloaded 4.5.1, 4.6 and 4.7. i'll try the other two and update.
Edit: 4.6 and 4.7 are working fine
What exactly is the problem you're having?
it looks like it stops or loops at the part where there is a message searching for direction.
I responded in the other thread. Did you try what I suggest there or what evoX2 suggested here?
EDIT: Just saw your edit. That doesn't change the fact that you should be able to use the other versions. Still try both suggestions with 5.0 if you like.
i updated to 5 again then tried evoX2 suggestion, oh actually that is how i always do it search first then navi, and still its stuck in getting directions message
what the .... i did not know it was using the tts service and i have that frozen in TI. Unfreeze it and now its working.
Now i know what TTS is and learned it the hard way geeez
you just click on the app, and then press the button to turn it on, once it's on your other device will recognize the signal and it gives you a password t type in (like 1234567890) thats it
kernel is here
[GPL][Kernel]netarchy-toastmod, Stable: 4.1.9.1 Beta: 4.3.1 - xda-developers
first you need to update the radios, then once you confirmed that you did that correctly (unless you have already done it) then flash the rom (factory data wipe, cache and davlik) once the rom is installed successfully then flash the kernel (go into recovery, wipe cache and davlik, then choose zip from sd card) then there is a little trick I learned from akazabam on how to calibrate the battery with the new kernel, let me know when you get that far and i'll tell you that along with the setcpu settings that I'm running
very nice rom 4.4, now I need to experiment on the 4.5 on wifeys Evo 4G.jebus i just got 4.4 running right
Thanks for the update. I wonder if maybe we should start keeping all these mikfroyo updates in one thread so that we don't have to keep jumping around
Quick question...I've done a lot of reading and was curious if the zip Here will move the apps to the sd or do we need to do what's here? The way I am understanding it is that the first link is a zip to do what is all in the second link. Correct me if I am wrong. Also should I wipe calvik/cache prior to flashing that zip?
I am looking to do this tonight. I am nandroid backing up now.
TIA
Nick
Those are two different things. The first is a simple way to move dalvik cache (*not* apps) to the /cache partition. Basically, you have 1 GB of internal storage that is partitioned into /system, /data, and /cache. Your usable space is in /data, and it's about 430 MB. For whatever reason, dalvik cache is in /data. To keep it from taking up space you could otherwise use, that first flashable zip is a simple way to move dalvik cache to the /cache partition, then link the normal location to the new one so the system can find it. /cache is used by the system, and you have no control over its space; therefore, when you move dalvik there, you reclaim some usable space without actually moving anything off internal storage. Note that this has nothing to do with moving your apps anywhere.
The second link is for darktremor a2sd. It's main purpose is different, but it can do the one thing that other flashable zip does. A2sd is meant to be used with an ext3 partition on your sdcard. It needs this because that is the native filesystem to linux, which is required for actually executing things. Android can't actually do a whole lot with the normal fat32 filesystem on the card. Having these two separate partitions on the card allows you to use a2sd to do a number of things, including but not limited to:
- Move all apps to the sdcard
- Move dalvik cache to the sdcard
- Move dalvik cache to the /cache partition
As you can see, a2sd can be used to move dalvik cache to the /cache partition as well. If you intend to move dalvik cache to the /cache partition only, just use that flashable zip. If you want to move your apps to the sdcard, even if you want to move dalvik cache to the /cache partition or sdcard as well, you should use a2sd.
EDIT: you edited your post before I finished this. Dalvik cache to /cache and the main purpose of a2sd are two different things. Your current sdcard (stock) has nothing to do with moving dalvik cache to /cache. Go ahead and move it with that flashable zip if you want to clear up a good 60 MB at the very least from /data.
Thanks for the answer. Funny thing is I edited my edit as I was editing. Just thought about it a little more and figured it was two different things. Appreciate the response.
Do I need to wipe the calvik prior to flashing that? Reason I ask is that I am going to flash a new kernal and from what I understand it's best to wipe cache/dalvik cache prior to flashing kernal. Can I just flash both of those in the same recovery or should I flash one first then reboot, then flash the other after I see it's stable?
Thanks.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.