Related
Serious effort to reverse engineer and change the "OK Google Now" activation phrase
I just got my Moto X dev edition today, and I plan to try and reverse engineer the activation phrase code in order to change it. I'm going to start by decompiling the touchless application, but I think it will be far more difficult and deeper in the system than that.
Does anyone know where the activation phrase is actually stored? Does anyone know anything about the internal structure of the touchless stuff? And finally, is anyone aware of any other attempts to do this so I can collaborate with them?
Thanks!
glitch003 said:
I just got my Moto X dev edition today, and I plan to try and reverse engineer the activation phrase code in order to change it. I'm going to start by decompiling the touchless application, but I think it will be far more difficult and deeper in the system than that.
Does anyone know where the activation phrase is actually stored? Does anyone know anything about the internal structure of the touchless stuff? And finally, is anyone aware of any other attempts to do this so I can collaborate with them?
Thanks!
Click to expand...
Click to collapse
I got no idea about any of your questions. I wanted to say that doing what your doing would be a very cool feature so thanks for the effort if you get anything going.
I also wanted to mention that I know the OK Google Now phrase is processed on the phone. The voice commands first get processed through Motorola's touchless control app or processes then if it is not recognized as a command it can deal with it then uploads it to google owned google now app. This is why you sometimes get different looking dialers or screens when sending texts depending on if Moto touchless controls handled the action or if google now handled the action.
Just thought of this but I bet it is extremely hard to do what you are doing because no one has created apps to use the low power processor so i presume its locked up somewhere in the phone.
a small start
So, I decompiled the Touchless APK and opened it in Eclipse. I found some interesting stuff in strings.xml, but I think it's just the strings that are displayed to prompt the user This one stood out to me though:
Code:
<string name="hello_moto">OK Google Now</string>
Could it be that the phrase was originally going to be "hello moto" but when Google bought Motorola they changed it for branding purposes?
I think these other string names indicate that could be the case:
Code:
<string name="training_say_hello_moto">Say OK Google Now…</string>
<string name="training_second_hello_moto">Say OK Google Now a second time…</string>
<string name="training_third_hello_moto">Say OK Google Now a third time…</string>
<string name="training_final_hello_moto">Say OK Google Now a final time…</string>
Anyway, if someone wants to change that hello_moto string in the strings.xml file to something else, it might be worth a shot. I can't test any of this yet, because I can't root my phone because it has a spec of dirt under the lens and I'm mailing it back to Motorola to get fixed. But if somebody out there with the knowledge to change this setting in the strings.xml file of the apk wants to try it, I think it's a promising lead.
Hello moto would be cool.. Much better than the OK Moto Magic that was also on the cards... That would just be embarrassing! Good luck man
Sent from my XT1058 using Tapatalk 4
That application is an almighty mess. It has a tremendous amount of classes named things like "a", "aa", "ab", and so forth. Right now, I'm trying to make an Xposed module to send an intent to Tasker rather then start Motorola's interface when the key phase is said. This has been a nightmare of its own. I'm going to start digging for the start phase in earnest once I get this part done.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
hawkjm73 said:
That application is an almighty mess. It has a tremendous amount of classes named things like "a", "aa", "ab", and so forth. Right now, I'm trying to make an Xposed module to send an intent to Tasker rather then start Motorola's interface when the key phase is said. This has been a nightmare of its own. I'm going to start digging for the start phase in earnest once I get this part done.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Names like that usually indicate that the code was obfuscated . I would be stunned if they coded it that way!
@glitch003 any luck with this?
Sent from non rooted motoX :'(
I'd totally change "Ok Google Now" to "Jarvis" if I ever had the chance.
hawkjm73 said:
That application is an almighty mess. It has a tremendous amount of classes named things like "a", "aa", "ab", and so forth. Right now, I'm trying to make an Xposed module to send an intent to Tasker rather then start Motorola's interface when the key phase is said. This has been a nightmare of its own. I'm going to start digging for the start phase in earnest once I get this part done.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's meant to be an almighty mess, so people like us struggle for months to figure out what the code actually does and to prevent copying of their code
While I haven't been able to change the wakeup phrase, I have changed what happens when you say it. With Tasker, I am able to launch AutoVoice and/or !utter instead of Google Now.
This essentially allows you to control your entire phone with voice, while it's still in your pocket.
Kev1000000 said:
While I haven't been able to change the wakeup phrase, I have changed what happens when you say it. With Tasker, I am able to launch AutoVoice and/or !utter instead of Google Now.
This essentially allows you to control your entire phone with voice, while it's still in your pocket.
Click to expand...
Click to collapse
what exactly are you not launching? From my understanding Moto's runs their own voice recognition stuff, then when it can't recognize the command it then sends it to google now. (even though it looks like it is just running googlw now the entire time it is not. So at what point in the process are you hijacking the code? Also, how easily can you use it? Does it take a long time or does it start just as quick as touchless controls/google now was.
jayboyyyy said:
what exactly are you not launching? From my understanding Moto's runs their own voice recognition stuff, then when it can't recognize the command it then sends it to google now. (even though it looks like it is just running googlw now the entire time it is not. So at what point in the process are you hijacking the code? Also, how easily can you use it? Does it take a long time or does it start just as quick as touchless controls/google now was.
Click to expand...
Click to collapse
It's pretty easy. I simply use Tasker to detect when the Touchless Controls app becomes the foreground app, then immediately kill its process. After that, I launch AutoVoice. With AutoVoice, I can then say "Search" to bring me to Google Now, or "utter" to launch !utter. I can also say any of my home automation commands like, "Turn off the lights" or "Watch TV."
I essentially use the Touchless Controls app as simply a detection of when the phrase was said, and then launch my own processes that I want to launch once it's detected, and kill the app immediately before it sends any data to Google Now.
It's seamless, and extremely quick.
Kev1000000 said:
It's pretty easy. I simply use Tasker to detect when the Touchless Controls app becomes the foreground app, then immediately kill its process. After that, I launch AutoVoice. With AutoVoice, I can then say "Search" to bring me to Google Now, or "utter" to launch !utter. I can also say any of my home automation commands like, "Turn off the lights" or "Watch TV."
I essentially use the Touchless Controls app as simply a detection of when the phrase was said, and then launch my own processes that I want to launch once it's detected, and kill the app immediately before it sends any data to Google Now.
It's seamless, and extremely quick.
Click to expand...
Click to collapse
you want to run a test with a lock on your phone? I'm interested to know if touchless control bypasses the lock or not. I know it can do certain things with the phone in lock. I would assume the few options we have has to do with the fact that once touchless controls pushes the command to google now because it doesn't recognize it they can no longer keep the phone in a locked state. Anyway, if you could run some tests on that and report back I'm interested. Thanks in advance.
I'd like to help
Hey could you upload the apk?
Although I haven't done any reverse engineering before but I have a lot of spare time right now and I'd like to try and help. I just got a developer edition of the Moto X and annoyingly it doesn't seem like there's any easy way to root it right now, since it came with the newest update(at least as far as I can tell).
The only reason that matters to this is that I can't get the apk off of the device, as I don't have the sufficient permissions for data/app. If there's another way to do this then please let me know too!
Thanks
EDIT: nevermind, I realized there's a way to root it if I just unlock the device.
Recompiling with signature
I'm not sure if there is still any interest in this, but I've been trying to work on it nonetheless as a personal project.
This is my first time doing any sort of reverse engineering, and my worry is that we won't be able to sign the app after modifying it.
From what I've read of using apktool, it seems that if you want to keep the signatures you have to move the modified files you have back into the original apk.
Problem is, on OS X there doesn't seem to be a good way to open apks and modify them. Can someone else try and see if it can be recompiled and reinstalled?
Thanks
I messed with this for a short while. I found you can do it just by training. I was able to say "OK f$%& Wad", "OK Moto" and "OK Siri" (joke for my wife). I thought it was due to hex editing some files but that was only a coincidence. Train a phrase using "OK [your word] Now". Sometimes it is tough. Now most of the time you can start it with only "OK [your word]". They use some of the Nuance sdk. Nuance app looks for syllables if I read correctly. I will dig into the files again to see if it can be done more easily. All we need is one guy shouting the phrase and 10 phones want to react. ?
Good luck.
DroidJunk said:
I messed with this for a short while. I found you can do it just by training. I was able to say "OK f$%& Wad", "OK Moto" and "OK Siri" (joke for my wife). I thought it was due to hex editing some files but that was only a coincidence. Train a phrase using "OK [your word] Now". Sometimes it is tough. Now most of the time you can start it with only "OK [your word]". They use some of the Nuance sdk. Nuance app looks for syllables if I read correctly. I will dig into the files again to see if it can be done more easily. All we need is one guy shouting the phrase and 10 phones want to react. ?
Good luck.
Click to expand...
Click to collapse
Well the idea is that we want this to work even if you don't say OK, and you should be able to just say anything you want. Also, it should work without having to try many times.
On a side note, I've run into the issue where basically I can not install on top of the app because it's installed as a system app. I'm not too sure if there's any way to get around this besides removing the permissions check from the device which would be a huge security hole. I also don't even know if that itself will work..
It is probably a signature issue. I have a complete deodex of the original KK dump. If you sign with the same key that might help. You can verify by looking at your logcat when trying to install. Check out data/data/blabla audiomonitor. In the files Dir there is a file svsid_trigger. This is recreated each time you train. I would believe it to be a voice sample if you want to call it that. There are other files in there that when opened show the phrase OK Google now. This is where I hex edited but it did nothing. It will even run without some of these files. My theory is one of these files contains a sample of what it should look like. Decompiling the apk is about as messy as you described. When you check the prefs you see the phrase is set to custom phrase which appears to be a function/class. This also gets rewritten when the phone is booted. Curious to see what happens. I really expect Google or moto to change this. It just does not make sense to have all the phones responding to the same thing. Even with training others can activate it. I was watching a video on the phone and that activated it. LOL
DroidJunk said:
It is probably a signature issue. I have a complete deodex of the original KK dump. If you sign with the same key that might help. You can verify by looking at your logcat when trying to install. Check out data/data/blabla audiomonitor. In the files Dir there is a file svsid_trigger. This is recreated each time you train. I would believe it to be a voice sample if you want to call it that. There are other files in there that when opened show the phrase OK Google now. This is where I hex edited but it did nothing. It will even run without some of these files. My theory is one of these files contains a sample of what it should look like. Decompiling the apk is about as messy as you described. When you check the prefs you see the phrase is set to custom phrase which appears to be a function/class. This also gets rewritten when the phone is booted. Curious to see what happens. I really expect Google or moto to change this. It just does not make sense to have all the phones responding to the same thing. Even with training others can activate it. I was watching a video on the phone and that activated it. LOL
Click to expand...
Click to collapse
I know it's a signature issue when I am trying to install it, but even when I uninstall and install again, I get a permissions issue because it's not installed as a system app.
Also, changing the value of the audio file is interesting, but the problem is that unless we know the algorithms to generate the audio files, I don't know how we can adjust that. It seems cleaner to just go into the code and remove the checks altogether. On the other hand, it takes more investigating, and right now I am completely blocked on this. I don't have much time to mess with this anymore unfortunately, but I do want to try to remove the permissions altogether and see if it will let me install the app as a user app.
Synderesis said:
I know it's a signature issue when I am trying to install it, but even when I uninstall and install again, I get a permissions issue because it's not installed as a system app.
Also, changing the value of the audio file is interesting, but the problem is that unless we know the algorithms to generate the audio files, I don't know how we can adjust that. It seems cleaner to just go into the code and remove the checks altogether. On the other hand, it takes more investigating, and right now I am completely blocked on this. I don't have much time to mess with this anymore unfortunately, but I do want to try to remove the permissions altogether and see if it will let me install the app as a user app.
Click to expand...
Click to collapse
Check here when you get around to decompiling audiomonitor.apk. \AudioMonitor.apk\smali\com\motorola\audiomonitor\uis\training. It might be a good start. I use to be good at smali, but it has been a couple of years.
Soooo...
I was messing around with getting text secure to get working with Motorola Assist. From what I remember, I froze Messaging at one point while simultaneously making text secure a system app. Long story short, I broke the function where it talks to you when a text comes in. It still works with active screen and the Bluetooth in my car. It also still works with incoming calls for some reason. Wiping, reloading both the messaging apk and Motorola assist and its framework did not work. I'm looking at databases right now and I noticed it has a different status number and such compared to the other functions. I'm going to play with it to see what I can do, but is there anyway I can get a copy of the database from someone in the community? The database I was looking for was in data/data/com.motorola.contextualsmartrules2/databases/assist.db.....I want to compare the two to see what's different. I would also be open to someone else's titanium backup of Assist and its framework. I have a Verizon Dev Edition. I don't think the individual carriers matter since the databases don't reference the carrier. Unless someone else has a better idea? Thank you in advance for your comment/support.
P.S. I could technically just install my ROM fresh and restore everything but I got ALOT of customizations as well as Google Authenticator and I'd like to keep the ROM as is if I can't help it. I should've backed up before messing with it I know....
Sent from my BOOSTO! Moto X
ovismos said:
Soooo...
I was messing around with getting text secure to get working with Motorola Assist. From what I remember, I froze Messaging at one point while simultaneously making text secure a system app. Long story short, I broke the function where it talks to you when a text comes in. It still works with active screen and the Bluetooth in my car. It also still works with incoming calls for some reason. Wiping, reloading both the messaging apk and Motorola assist and its framework did not work. I'm looking at databases right now and I noticed it has a different status number and such compared to the other functions. I'm going to play with it to see what I can do, but is there anyway I can get a copy of the database from someone in the community? The database I was looking for was in data/data/com.motorola.contextualsmartrules2/databases/assist.db.....I want to compare the two to see what's different. I would also be open to someone else's titanium backup of Assist and its framework. I have a Verizon Dev Edition. I don't think the individual carriers matter since the databases don't reference the carrier. Unless someone else has a better idea? Thank you in advance for your comment/support.
P.S. I could technically just install my ROM fresh and restore everything but I got ALOT of customizations as well as Google Authenticator and I'd like to keep the ROM as is if I can't help it. I should've backed up before messing with it I know....
Sent from my BOOSTO! Moto X
Click to expand...
Click to collapse
This is the very thing custom recovery is for!!
Making a backup before you mess around. Not a big deal, no ROM flash nor Rsd firmware
aviwdoowks said:
This is the very thing custom recovery is for!!
Making a backup before you mess around. Not a big deal, no ROM flash nor Rsd firmware
Click to expand...
Click to collapse
I just wish I had the foresight to do that before I started messing with the messaging -_-'
I got a copy of the database I'm messing with in another location as well. So I just overwrite if necessary. What I noticed in some of the tables is that the other actions including hanashi, have status values of 1 or 2. The one that does the one for home has a 5. I've tried changing it to 1 or 2 and haven't gotten anywhere. My understanding of SQL or databases in general is spotty at best. But if I had to describe it, Assist isn't "seeing" the notifications from the stock SMS app anymore since it was frosted/defrosted/moved as user app. I'm not sure what kind of things that would break considering from what I've seen, it doesn't really. Also considering that SMS works in all other applications, I'm thinking it has to be Assist.
But I'm just an idiot with Google at this point, so who knows :laugh:
EDIT: Hanashi not Hamachi.
Update:
5 in the table means it's on.
2 means it's on, but not active
1 means it's disabled.
So according to the database, it should be on. Which technically, I suppose that's right since I see the Home icon up top. What's odd is that it's intent actions are different from the others as well. Referencing something with android.media intent. I'm wondering if I'm looking in the wrong spot...
Update 2:
After figuring out that the table I was looking is just for the intent and the activation of Motorola Assist, I decided that I would try Motorola support.
Telling them what I already did, the only other course they mentioned was wiping the cache partition....or resetting the device.
I'll be kicking myself if that's all it is (wiping cache partition). Won't know till I'm home later today.
Update 3:
No....no it does not work still. Ugh. I don't suppose anyone would wanna Titanium backup their Assist and Assist Framework and send me a link? Possibly their Messaging app too? If not I'll probably just have to bite the bullet and re-do everything.
Sent from my BOOSTO! Moto X
I am close to pulling the trigger on the MotoX2. However, I have one lingering issue that I need help with. Because of a disability, Always On Voice Input (OK Google) is very important to me. However, I am concerned with reviewers who have characterized Moto Voice as a "hack" (sometimes unresponsive, inaccurate, and a delay when needing a "handoff" to Google Voice). One reviewer who tested OK Google with the MotoX2 and N6 described the MotoX2 as being 1.5 times slower than the "pure" Google Voice implementation on the N6.
Having now verified that disabling Moto Voice on the MotoX2 causes instant on (from screen off) to no longer function (even under Lollipop) has left me with a dilemma.
I NEED Always On OK Google, but really don't want the size of the N6. So, I'm looking for input from MotoX2 users who regularly use Always On OK Google.
In general, I want to know, have the reviewers exaggerated the problems with Moto Voice? In day to day use, is Moto Voice accurate/responsive/quick "enough" when "handoff is needed? In addition, do users feel that the other features provided (specifically by Moto Voice; not the other Moto added features) is a fair tradeoff for the inherent delay when Google Voice is needed (i.e. would you trade them for the "pure"/faster Google Voice?
Any and all inputs/impressions are greatly appreciated!
Sounds like what you've read and researched is fairly accurate. Moto Voice responds well when you're clear and direct. Don't mumble and you won't have a problem. The delay is due to the handoff to Google Search. However, you can use either Moto Voice or Google Now. Both work well. The Moto X is a fantastic device. I don't think you'll be disappointed.
As far as I know the delay comes from the hack that Moto had to implement to overcome the android limitations in the area of "always listen". Im not sure about it but my assumption is with lollipop it should be faster due to the fact that it's already built in into OS
Sent from my XT1092 using Tapatalk
I use Moto voice on daily basis. My day starts with "how's the weather today"
It is about 80% accurate, with my Indian accent. Considering that you have a better accent than i do you will be just fine.
That being said, you need to be in a fairly silent environment.
Does the delay bother me? Yes. Will it stop me from using moto voice? Heck no!
I integrated moto voice with commandr and tasker ad use about 20 tasks on regular basis so i am kind of addicted to moto voice. Apart from that i use moto voice for placing a call and texting, as a matter of fact it recognizes my friends' names(also indian) really well.
I would recommend you to go ahead and buy IF you believe you can use it a FAIRLY QUITE environment.
Thanks all for your inputs so far! Any further impressions will also be helpful!
@roaringcrown, I will be using it mostly from screen off, so I am tied to Moto Voice, as there is no support (even in Lollipop) for Always On with stock Google Voice.
@blinkin, it's my understanding that Moro Voice will still be required with Lollipop (for Always On), and hence, still the delay
@Prash8429, glad to hear it has decent accuracy even with your accent!
Thanks again to all. Looking forward to other impressions!
Moto X Voice Commands and Gesture on 3rd Party Home Launchers?
I have a quick question for user here on XDA. Can someone tell me if the 2014 Moto X Voice and Gesture command will continue to work from sleep/idle mode if I install a 3rd party home launcher? Or is this function specific to the stock launcher provided by Motorola on this phone? Thanks
twcamc said:
I have a quick question for user here on XDA. Can someone tell me if the 2014 Moto X Voice and Gesture command will continue to work from sleep/idle mode if I install a 3rd party home launcher? Or is this function specific to the stock launcher provided by Motorola on this phone? Thanks
Click to expand...
Click to collapse
I have had no issues with other launchers whatsoever.
Thanks for the update. I like the launcher I am using now and didnt want to have to stick with stock launcher just to use all the moto features...
imaginaryenemy said:
I have had no issues with other launchers whatsoever.
Click to expand...
Click to collapse
Using Nova Launcher Prime with no issues....
I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.
Bumping - I'd really appreciate any help, gents.
iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.
iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work
I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.
Hello XDA!
I was wondering if its possible to install and run the original Moto Display application on my device. My device is a Moto X 2014 (Pure Edition) running Cyanogenmod 14.1. I have tried alternatives such as DynamicNotifications, ACDisplay, and Cyanogenmod's own Ambient display, but none compared to how Moto Display feels. I've tried installing the application from the Play Store but once I open the "Display" portion of the Moto app, the app crashes and goes to the main screen. Any help at all would be appreciated. Thanks again and I look forward to my first XDA Thread.
Hi man!
I get that this is your first thread, but this has been discussed a million times. You'll never get Moto Display or Voice on any ROM that is not stock. They're closed source apps and there's nothing we can do about it, not even workarounds because the lads at Google are greedy bast*rds which have hijacked most of the features in Android, the most notable one being, guess what, voice control.
Flipz77 said:
Hi man!
I get that this is your first thread, but this has been discussed a million times. You'll never get Moto Display or Voice on any ROM that is not stock. They're closed source apps and there's nothing we can do about it, not even workarounds because the lads at Google are greedy bast*rds which have hijacked most of the features in Android, the most notable one being, guess what, voice control.
Click to expand...
Click to collapse
Thanks for your help. I am sad that its a close sourced app but I guess there's nothing I can do about it. Thanks you for assisting me in this matter.:good:
You're welcome I also used CM14 for some time until I realised that workarounds for Display weren't the same thing, that replicating Voice functionality was a lost cause, and that I needed some Xposed-related features for my job (such as disabling the proximity sensor).
I settled on stock 6.0 with N-ify and N Navbar, which do a pretty good job at making this phone feel up-to-date.
It's a setup I would suggest to anyone looking for a feature-minded compromise, even if multiwindow is absent and quick reply only works to a certain extent.