yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I always wondered this. But I figured for instance touchwiz uses a lot more resources than aokp and cm so that would make sense.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
This got buried a few pages back. Anyone else experience this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Many thanks Ktoon, I was really missing that!

:):thumbup:

Edit: running flawlessly on AOKP T&K 1.1!!! (Ktoonservative/Row)

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
You could just try moving it to another folder....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Koontz

Question for you:

I'm getting a bunch of Error reading cpu (erros) in the logcat when running with attached settings (see settings file, as well as logcat.

Do they mean anything, and should i be concerned?

I'm on illusion (CM) rom 1.1.1 d2att

running your kernel from 12/21 ---

I tried all the latest test kernels and they all behave weird with streaming audio and video (especially netflix) when i'm watching netflix audio would go garbled up, and video start to stater and eventually just stop.

If i hit pause for a quick second, it goes back to normal for about 15 seconds and starts over again.

I'm not having that issue at all with 12/21

Any ideas why the errors, and maybe just a note about the test kernels as well ;)

When i load default settings the error goes away

Attached is the logcat and settings

Thanks dude

Edit:

I narrowed it down to KT governor. As soon as I flip to it I see these errors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I am running ktoonservative/sio on AOKP (1/1/13) with the 1/1/13 JB AOSP kernel and have no audio or video issues as far as I can tell, I have played some music, youtube, and netflix without seeing any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
I see these as well on 1/1; there aren't any associated A/V glitches that I can see or hear, so they're probably unrelated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
video problems

I'm having problems with h.264 video playback (mp4 or mkv containers) with recent versions of this kernel (under task's 4.2.1 1/1 ROM) - the 12/20 build works but every build since then (12/21, 12/29, 12/31, 1/1) produces no video output (although the audio still works). Xvid video output works, though, and h.264 output works under task's default "underwear" kernel (but I much prefer this one!).

I'm happy to live with the 12/20 build at this point, but I thought I'd mention it in case the issue is more general (and I'd rather not get left behind!).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
What are you using to play back those videos? I ask because with my normally-used video players, h.264 video playback is working just fine for me (12/29 and 1/1).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
mVideoPlayer (free) or MX Player Pro - same behavior in both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I am also experiencing screen scroll lag that will sometimes scroll the opposite direction and key presses sometimes don't register. This only happens with ktoonservative governor. Very debilitating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Which governor are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
What kernel version? This was fixed in the 1/1 build a few pages back, AFAIK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
He explicitly stated Ktoonservative but not which particular build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Weird....I thought I was on the latest but I am indeed on 12/29 build. Downloading it as we speak.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Will there be any more updates for JB 4.1 kernel? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rekzer:
So if i flash this, then do a CM update, there shouldnt be any issue flashing the kernel back on after each update then? Are there any non-standard risks when using this kernel regarding the ability to switch back to others?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
With touch boosters off I get a good but of lag in scrolling and typing after a few minutes.

Can anyone recommend a good mhz to set touch boosters at to avoid this? Have it set to 486 and 810 now. Ktoonservative with row here,working great otherwise.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
bfq got rid of my lag on illusion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im guessing they have some kind of ROM mpdecision enabled from the log entry. I dont get those errors on CM or AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
so in-other words ignore them?

THanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing new right now so no need to update. Im stick sick as hell and barely getting by at work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
I've been seeing the errors on CM10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It can effect performance with the error reoccuring if it is doing it more than once a second.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Ok so stay away from that governor then I'm guessing.... I'm new back on tasks ROM and not seeing these errors
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You can use ktoonservative on mine and task's ROM, working fine for me :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I noticed using ktoonservative governor gives me a lot of lag and it's slow. It's never been like that. It's so bad I have to switch to on demand or pegasus to get it back to normal. Weird.. Used to work just fine before.

Btw I'm using the latest aokp

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Which release are you using? one from 1/1 - i thought it was only for CM rom's?

Any suggestions on which one would work with Task's?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Testing with CM 1/2 and running perfect:good:

I cant remember if I have told you guys in this thread or not but there is most definetely something WRONG in 4.2 ROMs. The CPU usage goes up and down like a freaking yoyo and reaks havik on governors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I would've remembered that. That said, I don't think you've said it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
any of your kernels will work well with AOKP (Tasks?)

There are a number of posts in his thread stating to stay with underware, but KT has much more control, and if there is a version that works with his ROM i'd like to give that a shot.

thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You're welcome to try it - Task has just tried to make it clear that if you have weirdness (which Ktoonsez is having too) then you need to go back to his for any support. They're still really early in ironing out 4.2 bugs. That said, make sure you stick to the most recent KT kernel - he keeps working on it and experiments get posted in the thread every time he nails one down :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Srsly, On 1/1 aokp I my phone gets crazy hot while playing nova. 2 restarts on stock task kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Ah. Makes sense. I Noticed it sticks to 1500mhz so I know it wasn't working but still didn't explain the sudden lag and freezing at times. Weird. Oh well. Every other governor works and it's smooth so it's all good :D almost got 4 hours of screen time today so I'm happy

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats odd, unless I misunderstood u. Ktoonservative is the only one actually working right. The rest of the govs spend 90% of the time at MAX Mhz. Which is why most people are saying that ktoons gov is laggy, they got used to all the other govs that constantly are at MAX Mhz and never/rarely hotplug. Hope that makes sense to you guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Really? Intellidemand seems to be behaving on my end according to ktweaker. Stays fairly low on the frequency spectrum. Do you know of a way to watch the frequencies on the fly via the device and not via pc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
CPU Spy from the Play Store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I just tried it on CM, intellidemand spent 2 straight minutes at 1674, it did shutdown the second CPU for 37 seconds. Really odd! Using KTweaker is a good way to look at live and CPUSpy for a list of the steps it is using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I just saw that on cpu spy. It does like to hang out at the high end but most of my usage over the last two hours had been deep sleep and the lower frequencies. It would've been longer but I've rebooted a couple of times because I was changing some files around.

Have it. I don't think it tells you what you're running on the fly like a widget or something. Haven't checked. Going to now.

Edit-nope. No widget.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Like I said above, use KTweaker to see it live, you will seeit yoyo and spend most of its time at max Mhz, at least my phone does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Yeah. After you said it, it is pretty weird to see it hang up there so long.

Edit-Just played around with it and your governor is the only one switching off the second core. That being said, damn you Google AGAIN for mucking things up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
As long as you getting great battery it doesnt really matter in the end, I was just surprised to see u had good battery with a gov acting like that. This really cant be compared to your battery, but here is what I got with ktoonservative today

1:12 minutes screen on.

17 minutes of calls

Got home with 84% battery left.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I just edited the previous post. My battery for today is crap. Not my usual usage plus I'm trying out another ROM and have been modding things left and right. I'll give it another few days to settle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
Use cool tools..it will put a live CPU frequency in the status bar..it also has lots of other gauges..i use CPU freq. And battery temp..it will also show more then one core i believe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Any chance you can send your settings file?

I'll give your config a try?

Also another question 1/1 is the latest kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Be careful when using that app, it is waaaaaaay cool but unfortunately for cool things like that it is using up alot of CPU to tell u all that stuff, thus messing with the real CPU usage, make sense?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
1/1 is the latest.

I cant upload right now but here are the settings, real simple.

ktoonservative gov

ROW scheduler

-75 mV all steps

486 for Screen OFF max Mhz

Stock TOUCH BOOSTERS

Thats it :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Sweet, thanks, will give it a whirl! :good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Actually, I'm interested in this as well.

Edit-just saw your post. I'm too slow. Touch boosters enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Modified, my original post and yes Stock TOUCH BOOSTERS ALWAYS. Thats the heart and soul of project butter :highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] furntree:
Hey ktoonsez I have been messing around with editing the BFQ scheduler and every time I open ktweaker I get a warning saying my saved I/O scheduler does not match current. Are the settings sticking even though it's warning me? Or is there some sort of work around?

Love what you have done with the kernel! Keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I may have changed TOUCH BOOSTERS sock values,

Are they: 1st =1134

2nd = 810

?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They should be sticking, but just to be sure answer no just to check. I believe there is an issue when editing schedulers and govs that have unchangeable values (like bfq). Its something I need to look in to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Yes they are. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats correct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
I'm wondering the same. Also a 4.2 kernel will not work on a 4.1.2 aosp rom correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
4.2 wont work on 4.1. If anything new comes along, yes I will update 4.1. There is just nothing new to update for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Hmm. I always turn off the touch booster. Now that I have them on there is no lag with ktoonservative. I'm running it with row and - 125mv all is well :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Same here. Turned them back on and all is well. Who would've thought?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Do you tend to lock freq? I've noticed some apps kick them around if they are not locked...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
-75 mv for all voltages?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Those are his settings. Each phone is different as far as what they can handle. Mine is -100 for all frequencies. Another user has his at -125. You just need to experiment and see where yours is stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I'm getting whole bunch of those error reading cpu load crap with kt again. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Running "stop mpdecision" in a terminal stops it for a while, but it only seems to work temporarily for me. Tried putting it in an init.d script, but that didn't seem to help either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
+1

Edit: better example

http://www.imgur.com/rjgL5.png

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
On the topic of logcats, this particular error is absolutely flooding mine...

hwcomposer [E] ioctl MSMFB_BUFFER_SYNC failed, err=Invalid Argument

Running T&K AOKP 12/23 (for working Bluetooth) with your 1/1 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AWESOME FIX

Go to /system/bin and move mpdecision to /system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I dont want this to turn into a LOGCAT fest. All these errors are created and are the fault of the ROM (99.999999% of the time). They will get fixed in time, 4.2 is still fairly new guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Renaming /system/bin/mpdecision has stopped this from happening on mine, and does not appear to have caused any issues that I have noticed.

Edit: Didn't see your one before I posted it ktoonsez.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably noop and ondemand, thats what I told people to use. It will drain about 2-5 percent in a 8 hours period with no use (I.E. while ur sleeping). As for when ur using it, people have reported good battery for those settings as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Works just fine here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
How does smartass v2 compare?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MysteryOfTime:
Hmm with the new kernel and root, SetCPU is still only showing 1350MHz, even though I have it set for 1890/1890 MHz on boot. And I have rebooted the phone many times now. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Your phone isn't suicidal? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Your SetCPU is either outdated or broke, use Voltage Control
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
I've tried those settings and my phone battery drained 15-20% in two hours with 1 hr screen time..is that normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MysteryOfTime:
Hmm same thing is happening with Voltage Control, I deleted SetCPU. I have it set to 1809/1809 but it doesn't go any higher then 1350MHz. I am using Diet ICS ROM and your latest Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
My battery is horrible with any settings i choose...kinda sad lol

I'm using latest kernel, ondemand noop 384/1350, auto screen brightness, no sync, 30 minutes of screen time and I'm at 76%
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Did you clear your cache and dalvik cache before flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
I cleared them after flashing

Also:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Here you go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Voltage control has not been working for me. The init.d script does not work either when I set it with voltage...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
Reading through this thread a few pages back, it seems there was some trolling and some off-topic posts but it looks like it is back on track.

Thank you all!

FNM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
Not huge on benching but my first stock run when day I got the phone was 6500 something. I wonder if 1890 just isn't really sticking?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Try to set min/max to 1890 and test to see if there is a difference in score.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
I have only had the phone for a week, but I might try a factory reset...

Already turned off LTE.

Things I tweaked to make it better:

SetCPU:

Screen off Max 486, Min 384

CPU Above 50C - Max 702, Min 384

Down clock max to 918, min 384

- All Power Saving turned on....

- Installed JuiceDefender

- Installed Lux Auto Brightness, set brightness lower

Compromised with all that effort and now my phone is running with acceptable temperature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
Every time run it my score goes down lol. Its probably a rom thing. Diet is what I am using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vashht:
Here is what I got after flashing the newest kernel with OC. I have it set at 384min/1890 max using ondemand and sio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LMAO, those apps are hilarious. It is just a random number generator as far as I can tell:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Look 3 posts up. And yes your method will work too.:good:. There is no side effects to this if you are going to use a manually hotplugging governor like ktoonservative, pegasusq and so on. All this does is keeps mpdecision from poking its nose in where it doesnt belong (in the hotplugging of CPUs when the gov and kernel can do it).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
So in other words, all this is really doing is preventing an error message that is generated, that has no effect of performance or stability?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Is it possible to include row scheduler in 4.1 kernel? Or is it a 4.2 thing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
This worked great! Only consistently reoccurring error i have left is the accel handler, and that was there the whole time i was on 4.1 as well

---------- Post added at 09:16 AM ---------- Previous post was at 09:13 AM ----------

If anything it should make it more stable as long as you're using a kernel/gov that manages it's own hotplugging. I'm assuming the errors it's generating are the rough equivalent of trying to use two different CPU control apps at the same time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rekzer:
Still have 1 quesiton RE: that warning on main post. There are currently no issues with switching to this kernel and say CM stock back n forth for daily updates that requires any sort of driver weirdness? Just wanna make sure I dont end up with issues

I basically wanna Flash this kernel, do nightly updates, and reflash after. Someone said before its no longer applicable but wanna be sure..cause the warning is there for a reason and not sure how to fix it if it goes bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
The drivers come with the ROM, so any weirdness you encounter as a result of using this kernel can be fixed by a dirty flash of the ROM and gapps.

The only potential issue you may see with the application you're talking about; is if you try to flash just the cm kernel after you flash this one. If you're flashing the full ROM (ie. A nightly update) you will be just fine. On a full ROM flash, this kernel will be replaced by the one that came with the ROM and it's associated drivers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrvirginia:
i had a question. any reason why CPUSpy says 1512 is an unused state even though it has been used? lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I had the same issue I was using the GPS and playing music and the GPS was lagging so bad that it was almost a mile behind. I switched to on-demand and sio and the problem went away, I never excited the apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
When I get time I will.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I actually went to the agps fix thread in android development and flash one of their zip. My gps has been on point ever since. Locks 2x faster with more accuracy.

Here's the link to the thread..

http://xdaforums.com/showthread.php?t=1881660

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Flicker?

Great kernel performance as always, but I'm curious if anyone has had any luck resolving screen flicker on CM 10.1 nightlies. I keep crossing my fingers that development on the nightlies will squash that bug for me, but no luck so far. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I cant even imagine how anyone could get screen flicker with CM 10.1. That hasent been present in the 4.2 ROMs at all, only 4.1. Thats one for the books for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
:highfive: :D :victory:

I agree. I've never even heard of screen flicker on this brand new OS that has so much work that needs to be done to it that I actually hate 4.2. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
+1, 4.2 sucks!!!!!!!!!!!!!!!!!!!!

Floam
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrvirginia:
any ideas as to why it says 1512 is unused??? is this a kernel error or CPUSpy reading it incorrectly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I kind of like it. Then again, I'm not cooking anything for it. Either way, the work you guys are putting into it is commendable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I don't think you're understanding what I said, the phone lagged so much with the settings row and kservative that it couldn't keep up with my driving I had to go to on-demand and sio.then it worked flawless the rest of the trip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
My GPS on GoogleMaps and Google Navigation, and Ingress as well, does seem laggy. It will be good for a little bit, but then hang in one spot without crashing, and then refresh itself to real-time. this is using ktoonservative and row. switching to ondemand and sio like you said fixed it up immediately
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
That sucks...it must be an issue with my phone. I'll keep fooling around with it.