I rooted my phone for the first time this weekend and loaded Cyanogen MOD. Everything is working GREAT, except for one issue with Locale. When I go in to setup a a new situation it won't let me add a location condition. I hit the "Add Condition" button, hit Location, and all it does is go to a black screen for a second or two and then takes me back to the "edit situation" screen. After I hit location it looks like it's trying to load the normal location select screen but can't for some reason. Anyone ever see this or have any ideas why it might be doing that? Any help would be greatly appreciated.
The app has worked flawlessly for me and I have always had root but I think the latest update made this feature not work which is unfortunate.
I installed the 4.0.2 Cyanogen ROM yesterday and setup a new location in Locale as recently as an hour ago. Do try an uninstall and reinstall of locale and make sure you're running the latest version of Google Maps.
I already tried un/reinstall of Locale to no avail. I just tried un/reinstalling Google Maps as well, but that didn't work either.
Any other ideas?
Try opening google maps and finding your location in there first. I did that and it magically started working again.
So, nothing I tried worked (even opening google maps first). I started to get more suspicious when I noticed a few other map-enabled apps would work as well (mymaps editor, weatherbug, etc). So I decided there must either be something wrong with the version of the ROM I loaded or something else I had done messed up something with the maps. Loaded the latest version of cyanogen and now it works great. Go figure.
Thanks for all the suggestions anyway.
According to the developers website they know about the issue and its being blamed on people with rooted phones. Their solution is to go back to an OEM build of Android which is total bull**** so I sent them an email letting them know.
"Why can't I open Locations after the latest update?
This happens frequently on rooted phones, phones running unofficial installations of Android, or phones modified in some non-standard way (e.g. running apps off of the SD card). Try restoring your phone to an officially supported version of Android."
http://www.twofortyfouram.com/support.html
Locations doesn't work on hacked phones, because the Android on these phones has a problem loading the Google Maps libraries. This is NOT a bug in Locale, and there is no code change in Locale that would fix the issue.
In order to investigate this issue, I've taken these steps:
1. Contact Google: Initially, this appeared to be a bug in Android. Google investigated and found that only hacked phones had problems, at which point they considered the issue closed.
2. Contact Steve Kondik (e.g. Cyanogen): He is looking into issue, but I haven't heard anything further from him.
At this point, there's just nothing else I can do. I can only suggest reverting to an official version of Android.
- Carter
Hi everyone
Yesterday rooted my phone using the one click root program on Mac.
Rooting and later on installing Titanium Backup and ROM manager went smoothly. Made backups as well.
However this morning I noticed something peculiar.
Clicking my phone from standby, I saw the browser opened with a site I don't know and not visited before and a pop up if I want to continu with loading the digital/SSL certificate. In the afternoon for a second time again, but this time a known site.
Checked google if such a malware exist on Android. And whether it is possible to set a root password in android. But both questions were not answered positively yet.
Have any one of you seen such a behaviour before?
did you install any illegal software in the phone?
as in those full copies of software not from Android Market?
not that I am aware of.
Most of them were from Android Market.
it is very suspicious that issue popped up after rooting.
I removed all apps that got default root access.
Will report again if issue reappears.
most people visiting this forum have their SGS rooted, and i've not read about this sort of weird issues until now.
myself included.
it'll be good to find out what is causing you to have those random pop ups of websites.
did you install VNC server or something similar by any chance?
That Security warning seems to be Browser bugs.. It pop up on my Nexus one after official Android 2-1 update1 and Android 2.2(Froyo ) update.(OTA).
=> All update are done with files from Google server direct.
Likewise the same happened after updating Galaxy S with the new FW..
Along the way, during update, the digital signature get messed..??
So, bought a nook color yesterday. It came loaded with 1.2, and the first thing I did after registering is root. No custom ROM, but have superruser and official Android Market access. I can even install a few apps. However, there are a few that I expected to see (Kindle, Astro in particular) that dont show up via a specific search for them in the Market. Did I do something wrong? Did I somehow half-root this? Any thoughts would be appreciated!
There are issues with the market after rooting. One of the devs seems to have finally figured it out (apparently it's been quite a ***** to sort out), but he's validating it before publishing it.
Same problem
I have the same problem with the market place. Where will the fix be posted?
After manual rooting Calendar issues
After doing the manual root the one application that seems to be the trouble for me is Calendar. The Google Calendar does not allow to add an account calendar to use. I have tried several other applications with no luck either. One indicates there is a issue synch information.
Then the other minor issue is within the Market has been fun. While in the Market it will decide to either go back a screen, go to the main area of the Market or exit completely out of the Market. That created issue when I was in the middle of downloading an application.
Any suggestions? The Calendar is more important but it would be nice to get both issues resolved.
This worked great for me.
http://forum.xda-developers.com/showthread.php?t=1066969
The Calendar issue was resolved with CalenGoo. It is able to synch and update information.
Market is getting better with the steps.
Let the fun begin.
found this
this worked partly for me. shows all the apps now, but they still wont install. ha
http://forum.xda-developers.com/showpost.php?p=13298075&postcount=92
It can be an interesting read!
Hi everyone! Do you use Avast Anti-Theft? ...
I have a problem and I'd like to check for possible reasons. Please help me!
I hope someone can send me the apk for Motorola Services (com.motorola.blur.service.blur.apk),
in a list of stock Razr i system apks the one for Motorola Services is called CCE.apk. (for stock Razr i ICS)
I think I need that app cause since it's gone Avast Anti Theft commands sent from the Avast site are not working,
the phone doesn't receive the commands. Sms commands sent to the phone do work.
I wanted to freeze these apps but forgot it and uninstalled them :/ These: (com.motorola.)atcmdlauncher.apk,
atcmdplugin.epu.apk, atcmdplugin.apk, atcmd.apk, atCommandService, AtProxy, BrowserMessage,
omadrm.apk, modempanicreporter.apk, meter.wisl.apk, smspush, DeviceStatistics, ModemStats,
OMAclienteprovisioning, OMAdownload, and others different other days.
Do you think this problem can be because of the lack of some of those apps?
If so, although I can't be exact, the last location hour reported in the avast anti theft maps is near the time I was
playing with my device. Which one can be the problem? Although, as of now with 5 days with this problem the location,
batery state and some configuration changes have been updated some times, but the Commands [still] don't work.
Everything else is working fine (wifi, 3G, Play Store, G+, online Gameloft games, maps, browser, etc).
And what is weird is that backups for all those apps are not working. The one for Motorola Services
shows only some kb of size (unusable). And other bad thing is that even if I restore the other missing apps they don't stick
and don't work, they're gone after reboot. :/ How to restore them?
I hope you guys can help me get back those apps so I can see if that's the problem.
Another reason can be: I was annoyed by the several Google Services (Google Play Services app) processes
running all the time. So I used ROM Toolbox's Advanced Freeze feature and unchecked to disable some of them.
It was all good for some days ("got rid" of them) untill I noticed my location in the Anti-theft maps wasn't updating... it all begun.
I had disabled Google Cloud Messaging (GCM.service) without knowing it (+ others) u.u But, I really think everything
else was working fine, though (even with GCM disabled o,o).
I noticed this because Avast site reported something like "GCM service is disabled in your device. Communication is not possible.
You'll be notified when it's back" when I tried to send commands. So I restored all of those processes to normal state.
Like 2 days after that Avast reported GCM was online again. I thought everything was Ok now, but no! Still the problem persists.
What I don't know if it's a problem caused by me or it's a default state is: When I check out Google Play Services in the running
processes view of ROM Toolbox app, then enter the Advanced Freeze view, the receivers "icing.impl.PowerConnectedReceiver"
and "mdm.ConnectivityReceiver" are disabled. I check their boxes to enable them, but after rebooting they are disabled again.
I'd like you guys check what is the state of these receivers in your Razr i, please. So I can know
To finish up, I, also, recommend Avast antivirus, if wanted it can be uninstalled after its Anti Theft feature is installed. I don't know how
hack proof it can be, but it can be very, very useful, specially because of the several remote commands it has. Try it n.n
I'm going to purchase the premium service after I get this problem solved. I have already sent my help
request to Avast on saturday. I'm waiting working days to get a reply.
Thanks for your kind help!
- L.
Solved!
Problem solved!
The problem was my router's firewall, it was miss-behaving. Ha
I disabled the Firewall and the device started to receive the web commans again n.n
I'm glad to know those System apps I deleted are not needed at all in the end. (But GCM (a.k.a. C2DM) do is needed for several tasks, of course)
Thanks for reading!
- L.
So I just got a Moto X. Out of the box, Google Now hotword detection ("Ok Google") worked perfectly both in Google Now and in the Google Now launcher that I sideloaded. Then, hotword detection randomly turned off. If I uninstall and reinstall updates to the Google Search app, hotword is temporarily fixed, but it won't last more than a day until it turns off again. This happens whether or not Motorola's own Touchless Controls are enabled or disabled.
It seems like some other app is causing it to turn off since a third-party hotword detection app wouldn't work, either, but I've hardly installed any apps since I just got it.
Also, I've already tried the most common suggestions such as ensuring that my voice input language is English (US) and making sure than no Accessibility options are enabled.
Any help to get back hotword detection would be greatly appreciated!
The newest Google search update broke hotword. The only way to keep it working for now is to uninstall the update and not install it again until possibly the next update.
Do you know what the latest version of Google Search is that still supports hotwords so I can grab an apk? When I revert back to the factory version of Google Search, it breaks the Google Now Launcher.
Also, any idea why hotwords would work for a while and then randomly stop. This has happened several times, all while I've had the same version of Search.
Uninstall back to 3.1. Make your changes then install 3.2, this is where Hotword Detection is still there but not selectable and Ok Google works. Now install 3.3, Hotword is no longer there but Ok Google still works. Don't install 3.4, you loose both.
Worked for me twice, I accidentally hit Update All and got 3.4 back, had to start over. I've been back on 3.3 for a week or so and Ok Google still works.
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
micahmo said:
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
Click to expand...
Click to collapse
In previous versions of Google search, you could say "Okay Google" instead of "Okay Google Now" to activate the hotword when you had the Google app open? I just recently bought the phone and it came already with the newest version of Google Now installed.
I don't think you've ever been able to say "Ok Google Now" as a hotword to activate voice search in the Google app. "Ok Google Now" is Motorola's keyword for its Touchless Controls. Touchless Controls have always worked for me, but when I'm in the Google app (or in the Google Now launcher that I sideloaded), I prefer to use Google's own hotword, "Ok Google" to activate voice search.
Out of the box, my phone also came with the latest version of Google Now installed, and hotword worked out of the box, but for some reason it became disabled. Any time I uninstall and reinstall Google Search (or even clear data), hotword is restored temporarily, but then becomes disabled again after a while.
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it. I haven't
had any trouble with the hotword detection reverting to off as long as I say on 3.3.
Various threads in different forums say different things about this to being a Chrome problem to a Google Search problem to Motorola disabling it
on purpose so the it doesn't interfere with Touchless Control. I guess I'll have to see what happens when Search 3.5 comes out.
At the moment, I don't have a car so the parking feature doesn't have a relevance for me but setting a timer would be kind of useful.
If is is an accident, it would be nice it it were fixed quickly. If it is on purpose, I really wish someone would re evaluate the policy of not allowing a
function on a device that I purchased and would like to make the decision for my self. Just my opinion.
I do hope you find your solution. I came from a Galaxy Nexus and I have been really liking this phone so far as it is as close to the stock that the
GNex was.
SoloDB said:
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
Click to expand...
Click to collapse
No, I did train Touchless Control. I could try disabling it and then re-enabling it without training it, but I don't see how that would fix anything. I actually like using Touchless Control for when the phone is out of my reach (which is exactly what it's for), but it's kinda slow and doesn't always respond. Ideally, I'd like to use both Touchless Controls and Google's hotword.
My phone is the unlocked T-Mobile version and unrooted. I don't know if that makes a difference.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it.
Click to expand...
Click to collapse
My launcher version is 1.0.9.1039417, but I grabbed an APK of the same version you have and it still didn't work with Google Search 3.2.
Anyway, maybe an update to Google Search or Touchless Controls will fix it eventually.
According to Moto, the disabled this as it conflicts with Touchless Controls. I think that's BS, but whatever.
I was having a conversation with my fiancé earlier and Google Now popped up when I said "Ok, you" in conversation. I appreciated Google's sentiment.
Sent from my Moto X
natezire71 said:
According to Moto, the disabled this as it conflicts with Touchless Controls.
Click to expand...
Click to collapse
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
micahmo said:
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
Click to expand...
Click to collapse
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
natezire71 said:
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
Click to expand...
Click to collapse
It sounded like he was going to bring it up and submit a report on the issue, using the conversation in the Motorola forums as a basis. It'd be nice if that led to hotword being re-enabled but who knows. Sounds like some software update is on the way, at least for t-mobile; maybe that will help. Wishful thinking...
Maybe 4.4.3 but who knows.
Google Now Hotword
If your phone is rooted, I think I have a solution for you. It's been working on my phone for about a day now. I don't think I have enough posts in to do any links, but if you go to Droid Life and read the article under "Google Makes “Ok Google” System-wide Hotword Detection Official" the is a link in the comments to a utility called UnLeashTheGoogle. Follow the instructions to get the Google Now stuff working. There is an added step however, look for hotword_blacklisted_devices and change the XT1060 to anything else, I used XT1000. I also went as far as disabling the Touchless Control app so that it wouldn't interfere with the Google Now functions.
All of you that use Touchless Control, great, it is a neat feature, but I prefer to use a more Nexus like feel. To each his own.
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
micahmo said:
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
Click to expand...
Click to collapse
You can root using pie via the moto x toolkit without wiping anything. I just did this the other day, but I deleted everything from the blacklist section.
The only issue I'm having now is always listening via Bluetooth in my car (2013 Honda crz hands free link non-nav). It worked flawlessly with my galaxy nexus.
Yes, unfortunately you have to have root. The utility needs root and before I found UnleashTheGoogle I edited the Google Search app pref file to
alter the blacklist which got Ok Google working in the first place, I needed root for that as well being the folder is in the System area. The utility
got everything enabled as well.
I know there are security issues having a rooted phone, but I learned in the Galaxy Nexus days how valuable it is to have a bit more control of
the phone to do the kind of stuff you'd like to do other than what Verizon and, in the case of the Moto X, the manufacturer would "prefer" you to do. The Developers Edition of
Moto X really has made the transition away from the old Galaxy Nexus really easy.
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
txaggies07 said:
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Would this help? http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher