Database Develop

CM-5.0.5/6: "akmd" alwasy takes up to 3% cpu

guys, I found out that the G-sensor daemon "akmd" alwasy takes up to 3% cpu on my N1 with CM-5.0.5/6.
I compared with stock ERE-27 rom, in which "akmd" in that takes less than 1%.
While during standby, it take no CPU usage.
Does it matter? I mean, would that kill our battery?
Actually I first found that out when I was using CM-5.0.5. One day I put my fully charged N1 beside my pillow and after 7-hr sleep, only 86% power left..

Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.

I just noticed this as well while tinkering.

Gimpeh said:
I just noticed this as well while tinkering.
Click to expand...
Click to collapse
I realize I'm bumping an older thread now but I still feel this might be relevant.
Running top at any point will still show "/system/bin/akmd" which is the system daemon for the compass.
In my case, it almost always resides underneath "system_server". I've tweeted it at Cyanogen once but got no response to my question.
So, after doing some digging, I pulled down the SDK and fired up the "Dalvik Debug Monitor" here's what I saw (See attached: android-troubleshooting2.jpg)
Edit: i42.tinypic.com/m953rq.jpg
Not that it needed reiterating but the AK8973 is the 3-axis compass chip and something calling it or (the driver itself) is throwing an error almost precisely every 10 seconds. Now, I belive this has only been happening since the upgrade to CM5.0.6-N1 (Although I am now on CM5.0.7-Test1) either way whatever bug there is, still remains.
Edit: i40.tinypic.com/21liauh.jpg
Googling for that error: "Compass driver encountered fatal error2" pulls up a single page in the CyanogenMod Forums and two error logs on PasteBin.

Bump!!-Bumb!!

Thanks for the bump! Being a lurker has it's definite disadvantages.
prophetjinn said:
Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.
Click to expand...
Click to collapse
In my testing, the use of 360º rotation nor the setting of "Launcher Rotation" changed whether akmd was consuming resources.
Full size image link: i40.tinypic.com/dxh0yu.jpg
Just as GaryD had posted here:
forum.cyanogenmod.com/index.php?/topic/3129-ak8973-compass-driver-encountered-fatal-error2
after a reboot the errors disappear for a while. I don't know the pattern to which they reappear (e.g. due to a buffer overflow or some other reason.)

confirmed...
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.6.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...

bubbahump said:
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.5.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...
Click to expand...
Click to collapse
Since I haven't run any other roms I was hesitant to drag anyone else's ROMs into the discussion. I've seen it with InsectrRaven and the Pershoot but they're obviously all pulling from CM's commits on Github. I realize they're not large amounts of cycles but any usage that can be minimized is something. Right? Maybe I'm just a minimalist at heart.
Much appreciated on the bump and the bump towards the devs.

Another confirm here.
I'm on CM5.0.7-test2 with pershoot 2.6.33.4 kernel. Mine was steady at 6% CPU though.

Confirmed..
E/AK8973 ( 101): Compass driver encountered fatal error2 is thrown in every 10 seconds.
CM-5.0.7.1-N1
Kernel 2.6.33.4-cyanogenmod

this TOTALLY makes sense to me. used the stock ROM for last 3 months and had great battery life. after using cyanogen 5.0.7 the last 4 days, battery life is much worse than the stock ROM for me. also different is in cyanogen this "akmd" always shows up in my battery usage, but this never appears in the stock ROM. i'd make a solid bet that this is a cause of the poor battery life on current cyanogenmod, especially if this thing is hitting every 10 seconds with some fatal error. wonder if it can be easily fixed?

I have an EVO, unrooted, no OTA update, fully stock but used the 'top' app to notice the compass /system/bin/akmd consistently using resources.
Disabling auto orientation has fixed it, and done miraculous things for my battery life (battery graphs can have flat lines!), but I want my auto-rotate back. Is this a case of the accelerometer writing out a bad settings file, or it's a bug or what?

I'm still seeing this issue in the latest cyan r c 2 nightly. I'm confused why the compass would be used for the screen orientation. As far as I know, we are talking about 2 different sensors. The phone has a compass sensor, which is akmd, and also has an accelerometer sensor, which is used for auto screen rotation. The compass I thought is only used in things like maps street view and Google sky map.
Regardless, is there any solution to get akmd to stop running all the time? What process is calling this to even run all the time exactly?

I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.

dvfk said:
I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.
Click to expand...
Click to collapse
was same for me.. i had disabled auto-rotating in "settings->display" and in cyganamod settings.. AND in launcher pro.. (i always lay down on the side and the phone flips and i dont like it).. i did this 2 days ago.. and phone been laggy as **** since then. akmd have had 70-99% cpu all the time.. so i turned it all back on again. and now akmd takes 1% wake and 0% sleeping.. so wierdo.. shud be the other way around!

any updates on this?
having the issue as well, can't get rid of it.
please someone let me know.

[Q] why do we all have so different results for gps?

So there are people on here that get good (not fantastic) performance from there GPS with stock, while others like myself have terrible gps performance with stock. I can't lock on, only 2 satellites in view ext. ect, ect. I even tried all the lbstest changes people recommended and i had no change, while others say its fixed.
When I flashed JH7 from odin one click download I got really good results, locking on after a minute or less down to 10 M and with 9 statalites in view.
but I've read others didn't have the same result as me and nandroided back.
Are we sure we all have the same GPS hardware? why do all of our results vary so much with the same rom on the same hardware.

mattbeau said:
So there are people on here that get good (not fantastic) performance from there GPS with stock, while others like myself have terrible gps performance with stock. I can't lock on, only 2 satellites in view ext. ect, ect. I even tried all the lbstest changes people recommended and i had no change, while others say its fixed.
When I flashed JH7 from odin one click download I got really good results, locking on after a minute or less down to 10 M and with 9 statalites in view.
but I've read others didn't have the same result as me and nandroided back.
Are we sure we all have the same GPS hardware? why do all of our results vary so much with the same rom on the same hardware.
Click to expand...
Click to collapse
It could be that some people master clear, when others haven't. I use SRE and my performance is amazing with the GPS. DG does some tweaks still i believe, and my gps tracks amazingly.
Other than that, I have NO clue why. Maybe people have more trees in the area and get less lock? Only thing I can think of.

thanks for the reply, it turns out that after doing a master reset and reflashing jf6 my gps is running better. I dont know what changed but it is performing the same as jh7 was. I guess back to the drawing board

my gpa worked better stock, and with the overclock kernel and utb. I then used jf7 and sre and I'm thinking about going without sre, or maybe move ap only version.
I didn't try jf7 without sre though so I can't know what it will do. I actually have a feeling that my recent poor performance is nothing but a coincidence though. I'll give it a few days and a road test.
Sent from my SAMSUNG-SGH-I897 using XDA App

Mine works fine with JF6, utb, and lagfix ext4.
Wife's also works fine with JF6 and utb.
We used google navigation on hers yesterday and it worked just fine.

Part of the problem is not everyone is testing GPS the same way. The best test is using the NAV application - and not just on a simple route in the neighborhood. Combination highway and local driving - see if the NAV thinks you are on the street or keeps trying to reroute you. Does it tell you about turns or think you missed them?
Also Track your travels and view it on Google maps - really zoom in and see if you wander through buildings.
I think some of it may have to do with system blocking - more things running in the background may have to dow ith how often the GPS updates.

[Q] Samsung Galaxy S Terribly Inaccurate Time-Keeping

Hi people,
This is my first post, forgive me if I'm doing it wrong or in the in wrong place...
I have an annoying issue with my Galaxy S that I have googled and cannot find any information about or whether other people are also having the same problem.
When I set the time on my device in sync with the time I get from googling the time in my location, within a day my device is already 10 minutes behind the time google says is the time in my location. (other devices synced with google's time remain synced, its just the Galaxy S that does this).
A bit of information on my Galaxy S:
I am running Android 2.2(beta) I9000XXJP3,
kernel version 2.6.32.9,
build number FRF91.372
Ext3 speed fix running on phone
I am an electronics engineer, so my first guess as to what the problem is is that the phones real-time clock is not keeping time accurately (if in fact it has a hardware real-time clock!).
If theres no real-time clock then I am guessing it may be a problem with a software implementation of the real-time clock.
Has anyone else experienced this problem? Is it a problem perhaps with running the EXT3 speed fix that is causing the software to not keep time accurately? (as i understand it, the EXT3 speed fix and modified kernel reduces the number of writes to the Samsung RFS? Could the reduced number of writes be causing the software real-time clock to not be updated on its regular intervals?)
Any help is much appreciated. I have already been late for a couple appointments because of this problem lol
Thanks peeps

install clocksync that will take care of the time problem if any
http://forum.xda-developers.com/showpost.php?p=8027593&postcount=31
in a way i think the clock problem reported by some people might be lag related
i never have lag on my phone, and coincidentally i have no problem with time being delayed
running stock JH2, no lag fix as it's not necessary, GPS quick lock in 5 sec, no jumping around or to the next lane or next street

Excellent
Thanks a bunch. I may have to consider downgrading back to a working version of 2.1.
From all of my experiences with Android 2.1 on the Galaxy S (and I have tried about 8 different releases) is that I constantly get the "black screen of despair". Installing Froyo fixed that problem to a degree, and I rarely see the black screen with the speed fix. The phone is much faster.
From others' experiences, which firmware do you guys use? Or a more relevant question, which firmware have you found to be the most stable and usable firmware?
Cheers

TeRm!n8oR said:
I am running Android 2.2(beta) I9000XXJP3,
Click to expand...
Click to collapse
There's your problem.
I'm using the JPH Froyo firmware with a lagfix. Works great for me although it has a minor lag now and then.

I'm pretty sure there is a clock in the phone. I don't think there is any phone out there without a real-time clock. I don't see what lag or file system has to do with the clock... Most likely your problem is a syncing issue. Set your time manually and turn off all auto syncing options, maybe there is problem with your operator’s clock or in the app you are using to sync.

Actually, JP3 seems to have a known issue with time keeping. I'd be guessing maybe it runs a NTP daemon with an incorrect clock skew (guessing though). Either way, heard it many times for JP3, but never any other firmware.
The reality is though, only developers should be using beta versions of froyo anyway.

Maddmatt said:
There's your problem.
I'm using the JPH Froyo firmware with a lagfix. Works great for me although it has a minor lag now and then.
Click to expand...
Click to collapse
Are there any significant improvements between JP3 and JPH? Or is JPH just a more matured development from JP3? Are there changelogs/bug fix reports anywhere available for these?
PhoenixFx said:
I'm pretty sure there is a clock in the phone. I don't think there is any phone out there without a real-time clock. I don't see what lag or file system has to do with the clock... Most likely your problem is a syncing issue. Set your time manually and turn off all auto syncing options, maybe there is problem with your operator’s clock or in the app you are using to sync.
Click to expand...
Click to collapse
I'd imagine there would be a hardware real-time clock too. What got me thinking that it may be implemented some other way is that I turned off all syncing and manually set the time last night. I made sure i had wifi off, cellular data off, GPS off, roaming disabled, etc. prior to manually setting the time through the inbuilt clock.
I woke up the next morning to find that overnight the clock had somehow offset itself 5 minutes backwards from the time kept by google for my region. This was what initially made me think perhaps the time was being kept in software with an internal battery backup or something (I haven't cracked open my phone yet to see whats under the hood in fear of hurting it ).
Weird problem however you look at it. Although I don't think the problem occurred under Android 2.1, it seems to be a recent thing (post install 2.2 + Speed Fix).

TeRm!n8oR said:
Are there any significant improvements between JP3 and JPH? Or is JPH just a more matured development from JP3? Are there changelogs/bug fix reports anywhere available for these?
Click to expand...
Click to collapse
Matured. But some people are having probs with JPH corrupting their IMEI's.. But there are no changelogs (because it's a leak). I haven't heard any complaints about the clock being wrong in JPH.
Rule of thumb is to use Eclair unless you are a developer though. Pre-release firmware isn't a good thing to use on a phone you rely on

andrewluecke said:
Matured. But some people are having probs with JPH corrupting their IMEI's.. But there are no changelogs (because it's a leak). I haven't heard any complaints about the clock being wrong in JPH.
Rule of thumb is to use Eclair unless you are a developer though. Pre-release firmware isn't a good thing to use on a phone you rely on
Click to expand...
Click to collapse
Funny you'd say that though, I've had less problems with Froyo JP3 (other than the time problem ^) than I did with any version of Eclair. Especially when it came to the black screen of despair. I could not find a way to minimise its frequency, let alone get rid of it completely with Eclair. Mind you, at the time when i put JP3 on my phone, Eclair was only up to JM6 I believe.
Maybe it'd be worth giving JM7 or JM8 a go...

7 days with CyanogenMod 7

This is work in progress and I will update it for 7 days. Original posting can be found here
I'm sure you have heard someone telling you would spend way too much time with your smart phone. As if one could spend time with or without a tool. My phone, besides some rare occasions, is always with or near me. Yet it doesn't mean I spend time with it! I spend time with people, and I might spend my time spending time with using my smart phone to write an email. An if I spend time adjusting it to my needs or the latest desire aroused reading some blogs, so what? I do this for the sake of communication!
How come nobody understands that find difference in concept?
Day 1
25/05/2011, 11 a.m.:
Been checking my emails on the go twice, surfing on xda forum, chatting with the HTC support, writing an email to a friend, again checking my mails but also the market updates - what a pain to see there are no updates available for my installed apps. I check if it is not Sunday. No it’s not Sunday!
I discover how handy Evernotes can be. Copied an address out of the chat conversation and send it straight off to Evernotes. Must admit it was a little fight until I had marked the exact text line I wanted to have copied as it did not recognize it on its own. It would have blown me away had it read my thoughts.
I’m really thinking about one of those tables all the time. I’m kind of pissed somehow about the unfortunate fact there is no real handwriting recognition function on phones or tablets yet that really works - would be mind-blowing! I read the HTC Flyer does make advanced use of the stylus pen for note-taking somehow. I’ve seen some handwritten notes and compared them to the scribbling I am producing this very moment on real paper and there doesn’t seem to be that much of a difference.
However, I will have to type that later and I question this concept of me thoroughly doing it without giving up after a couple of minutes.
I’ve had way too many thoughts die due to the lack of an adequate and effective tool to digitalize my thoughts. I’m way much more impressed by my analogue brain-eye-arm-paper-to-key motion sequence I’ve happily produced as I realize I have really typed and added almost everything I wanted to say.
25/05/2011, 5.51 p.m.:
I wonder if I should give cyanogen latest night builds #87 a try again and get rid of my perfectly working Android Revolution ROM setup. I’m downloading, charging and backing up my phone for every eventuality...
Day 2
26/05/2011, 5.33 a.m.:
I have CyanogenMod Nightly Build #87 setup & running. Will see how it gets through the day. Fingers crossed the battery will not drain exaustingly.
26/05/2011,5.45p.m.:
In the mood for taking some screenshots and willing to do a brief review of my cyanogenmod 7 experiences...
Day 4
28/05/20011, 7.55.a.m.:
Can't hardly believe I haven't changed that much. Phone is working pretty fine, except there seems to be a problem between Fullscreen Caller ID and the call recorder that came with the modified kernel I flashed yesterday. I just won't use FSCI, instead, when I make a phone call it will try to use both the default dialer as well as the full screen dialer as the same time. The result is devastating: it will dial the number twice.
Day 6
30/05/2011, 1.53 p.m.:
Left home at 7.30 pm, battery went down to 51% by 12 a.m. and 32% by 2 p.m., whilst all I did were a few twitter & google mail updates, no phone calls, watching videos or other heavy-consuming processes.
Seems like the un-official CM7 nightly ROM I have flashed (Chezbell-cm7-20110529) is a battery killer! SetCPU is enabled, with a powersave governor profile activated when display is off, undervolted –25mA script running and I am nevertheless more than half-way out of battery within not even 7 hours – not really a full working-day yet!
Feeling unhappy and unsatisfied, after that the phone had been running so smoothly during the weekends ( some heavy 3G and EDGE-surfing in bad reception areas, gps navigation etc etc without a problem and far less battery drain). Phone was way more responsive with CM7 #87. Will switch to LORDmodUE 2.1 kernel tonight and see if it helps.
Day 7
31/05/2011, 3.13 p.m.:
I did it! I ruined it all! My sd card is totally erased! Holy frigging s’#!§t! What happened I still can’t recall exactly but I guess in any case I should learn to be more careful and most important: read and think before I act! I flashed a kernel while surfing the xda on my way home and now I don’t even find that stupid thread.
I guess it is a good point to stop my documentation now and draw my conclusions of my 7 days with cyanogenmod nightlies now.

Admins: please delete this thread. I've posted it to HTC DesireHD thread as I think it is more suitable...

CM7 GPS - no lto.dat?

Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Following this thread of thought, I tried the following (The URL is from a google search while I was digging about in gps_brcm_conf):
Code:
adb shell
cd /data/gps
wget http://gllto.glpals.com/7day/latest/lto.dat
chmod 777 lto.dat
I also did
Code:
rm gldata.sto
to remove (I think) stored orbital data from previous fixes to try to keep the results comparable.
Though measuring GPS performance is difficult due to constantly changing constellations and atmospheric conditions, I think this has made a difference in time-to-fix for me. Admittedly this might just be a placebo, so no guarantees.
If anyone wants to try this and post their results, it'd be great. And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering

It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.

Rusty! said:
It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Click to expand...
Click to collapse
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.
Click to expand...
Click to collapse
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.

nrkabul said:
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.
Click to expand...
Click to collapse
don´t have it on cm .64 either ...

Just created the missing file, and got a lock from stone cold, indoors pretty fast. Did that file help? Dunno lol
Will have to test more.

OK... here is my extremely unscientific test...
GPS Status without lto.dat: 43 seconds to lock.
GPS Status with lto.dat: 19 seconds to lock.
aGPS data was cleared before each test. Interesting, but far from conclusive.

Whooo! This is amazing!
Tried to lock inside without lto.dat, no luck at all after 70+ seconds... Copied the file into /data/gps, tested the same spot and got lock after cca 10 seconds!
This is amazing

nrkabul said:
Hi,
And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering
Click to expand...
Click to collapse
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf

nrkabul said:
Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Click to expand...
Click to collapse
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.

TrymHansen said:
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf
Click to expand...
Click to collapse
Ah. Yes, that explains it nicely. Thanks.
Sent from my Optimus 2X using XDA App

aremcee said:
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.
Click to expand...
Click to collapse
Indeed. That matches what I've observed.
Any idea why the download doesn't happen?
Sent from my Optimus 2X using XDA App

Download will happen for the next nightly, this is going to please a lot of people; top bombing.

This is truly awesome, hope it might have some small influence on apps keeping gps alive when screen is turned of too... Maybe a little too much to wish for, but..
Thanks send to nrkabul

It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.

Rusty! said:
It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.
Click to expand...
Click to collapse
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out

Rusty! said:
Download will happen for the next nightly, this is going to please a lot of people; top bombing.
Click to expand...
Click to collapse
Ah, quick work by arcee. I'd already cobbled together an app to do it for me, but this will be a lot better. Fingers crossed for a usable GPS
Sent from my Optimus 2X using XDA App

another workarround: Install this https://market.android.com/details?id=net.canaryx.gpsaids&feature=search_result
and download lto file. open root explorer /data/gps and rename lto2.dat into lto.dat

ionhide said:
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out
Click to expand...
Click to collapse
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster

lto.dat works great for me !!
got a fix in my car in about 5 sec, some seconds later got 10 satelites fixed !
GPS works like it did on MCR Rom for me now !
great discovery !

Rusty! said:
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster
Click to expand...
Click to collapse
I tried that app, and it didnt work for me, thats why i use My Tracks..
Sent from my Optimus 2X using XDA App