• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [1-21-13][ROM] CM10.1 for the evoLTE!!

so for everyone that is using CMX as a DD, is anyone having any GPS issues. everytime i try to use maps for anything with GPS i can never get a lock. it just says searching for GPS and thats it.

ontop of this issue i can't hear my speaker or media over bluetooth, the volume is way down on these for some reason and i can't get it fixed


any comments on these two issues

What build are you using. I'd highly suggest decks latest, always available from the irc.

I'm on my phone right now so I can't link but there should be one either in this thread or in the jellybean discussion thread
 
  • Like
Reactions: ocnbrze
Upvote 0
@Covert_Death: My GPS locking is sporadic. A couple times I've tried, it gives me the "Searching for GPS" message in the status bar, and my location jumps around every 30 seconds or so within a 2 block radius to my actual location.

However, most times, it locks on just fine (like right now).

I started with the 9-6-12 build, and am now running the 9-14-12 build.
 
  • Like
Reactions: Rxpert83
Upvote 0
Just curious, does this kernel support USB-hosting function through a USB OTG cable?

I would love to get digital audio output to an external DAC/Amp. The headphone output of the LTEvo is really noisy with sensitive IEMs.

Probably not this early on in the aosp custom kernel game, but its possible in the future.

Give it a try though, I may be wrong
 
Upvote 0
Ok here come the issues :) but I didn't know where to put this one bc I'm not sure cm10 is doing it. I noticed right before flashing cm10 ( I was on meanrom4.3) that Google now would say server error. Then it would work. Mind you it has been fine all day. So not thinking anything I flash cm10 well I went to sign into Google and it says server error. But then I go to the play store and I'm signed in? It's saying the errors but still working. Maybe Google is messing with something on their end?
 
Upvote 0
Ok here come the issues :) but I didn't know where to put this one bc I'm not sure cm10 is doing it. I noticed right before flashing cm10 ( I was on meanrom4.3) that Google now would say server error. Then it would work. Mind you it has been fine all day. So not thinking anything I flash cm10 well I went to sign into Google and it says server error. But then I go to the play store and I'm signed in? It's saying the errors but still working. Maybe Google is messing with something on their end?

Since it was happening before, I doubt its the ROM.

You could go into settings and manage apps. Clear data on google play and google services framework.
Then sign back in

Thats the "default" fix for most google issues
 
  • Like
Reactions: 3vodroid
Upvote 0
Hmm still getting the server error message. I did as you said and cleared data on both and now when I go to the play store it says server error. Retry? I've tried it with WiFi on and off with the same results. I have no idea what I could have done to cause this :thinking: it was working perfect.

After turning the device off and back on I am signed back into the play store which should mean I'm signed into Google. I can download apps and see my Gmail. But I'm getting an error alert in my notifications. Ugh.. As much as I want cm10 its just like bad luck for me or something :(


Just noticed someone created a thread stating they were having similar issues a few moments ago. Maybe its not just me after all. He's got the sign in triangle in his notification bar as well. Apparently this is wide spread and going across the boards quickly. Looks like Google broke something :)

This just in...apparently the Google servers are down according to info from xda. So no this isn't cm10's fault. :)
 
Upvote 0
On a more CM10 related issue... im noticing alot of force closes on different things. for example i wanted to change my input method to swiftkey. Settings force closed every time. So i went around to the back door and changed through a text box long press. I know this is being ever developed. So there will be bugs.

Yeah thats a known issue on cm10 & swiftkey, its not a bug limited just to our devices (IE, it happens on other devices like the s3 as well).

Glad you found the workaround. Could change it through the normal settings menu as well. Probably general JB incompatibility issues with swiftkey
 
  • Like
Reactions: 3vodroid
Upvote 0

BEST TECH IN 2023

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.

Smartphones