Database Users

Anyone else / Diagnosis Menu Update?

Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?

I've got the icon, but no updates as yet...

mwako said:
Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?
Click to expand...
Click to collapse
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before

skeet94 said:
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before
Click to expand...
Click to collapse
Can't believe i didn't notice that , I remember now thinking it was an odd feel before when it didn't vibrate inputing the codes, after every other touch/input/exit on the device makes it vibrate, Seems they are doing something then. Lets see if anyone finds any new interesting menus inside ?

The "root menu" doesn't work any more it seems. I don't quite recall the command since I always check the Focus threads.

Updated Service Codes
We have extracted about 90% of the Service Codes from the latest Version I have downloaded. So far, not much in additional options. Maybe some changes in the old ones. Needs to be checked. There are again, some dead codes which are not referenced, so this is normal and not a wrong code from me.
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
AUDIOGAINCONTROL <-- What a shame as I still need to tweak the Volume on Level 1/30. Which should play more this Level.
(Yes I know, I have tweaked the Sound Tuning options)
The App runs a functions called "check cable" and this one calls "JIG_UART"
This function checks for two conditions. Unfortunately just some numbers, which cannot be explained because of a number code only..
This seems to be a Service Cable, as I was not able to run those codes, even when changed from USB to UART in the menu. So lets get an UART cable
If the UART Service Cable is not needed, maybe someone else finds out...
There are also two commands which check a registry value from the phone, and start not for me:
FTAMAIN
VIEWHISTORYNW
So far I have seen only the following new ones:
SerialNumber --> Starts but does not show anything
TFlashUnPairing --> Starts but have not tested it. I don't need to know everything
Some Menu Item was deleted, forgot which ones...
I have attached the Commands and the Hash table. It does not make sense to transfer every hash code, because most of them are already resolved.
I explain how to resolve it, in case you want to try one:
As an example I have chosen the SMDINFO (Open the TXT file)command, because it has only 5 digits:
The first Number: (4) Tells you the length of the code. Because we use 0 too, this code has 5 positions:
Next to the number in the brackets, is the number you put into the DiagApp Tool, starting from the last. Because SMDINFO shows, you only two of them in the same line, you just continue downwards. You can also use the search option:
This results in:
*#03#
Again you look for the numbers next to the numbers in the brackets. So you need to find the numbers for:
(4) (3) (2) (1) (0)
(4) (3) are easy, on the same line... the looks for the next (2), which can be found under: DisableSellOutSMS If you are unsure, use search...
Its easier as it sounds...
If I find anything new and useful, I will let you know...
Let me know any interesting file to disassemble. The is always more then the eye can catch.. At least with a debug guru in the team...
MC

mchabr said:
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
Click to expand...
Click to collapse
I guess the well known workaound, will result in the same root access.
*#1111# continue to press any number, until the long number at the top gets a minus symbol. Then just press back, until you jump into the main menu.

Auto-rotate screen (colaberative 6 axis, G-Sensor, Accelerometer, Gyrometer) fix

First off let me say thanks to the many members that posted pieces of this fix for various Samsung phones.
The sole purpose of this post is to condense the info I found spread out across multiple threads when trying to resolve this issue myself. Hopefully making it easier for future users that may have the same problem I did. Which is why I have the various sensor names in the subject.
If your phone is having problems auto-rotating, or does not rotate at all in any app (like mine did). These steps should get you working again. This will be overkill in some cases but I like to cover all my bases when something is not working to begin with.
Note: This assumes you are running Android 2.2 (if you are not, you will not be able to perform the last step, but your phone should still work properly without it). Your phone will need to be rooted with busybox and you will need a terminal emulator app installed. I have attached the "Android Terminal Emulator" apk just in case you don't have or know what that is.
open your terminal type su press enter
type cd /data/system press enter
type rm ms3c_yamaha.cfg press enter
type cd /system/bin press enter
type ./sensorcalibutil_yamaha press enter
secure your phone on a flat level surface and gently press the enter key on your keyboard
type exit press enter
type exit press enter
Close your terminal and go to menu -> Display -> Horizantal calibration
turn your phone upside down with the bottom edge over hanging the table you used as a flat surface so that you can just barely see the calibration button when you are looking under the phone. Gently press the calibration button.
All done, you should be in working order!

Nice post! But the Epic does not require all of these steps that other phones might.(assuming your using Terminal Emulator)
Once within terminal, type
"su"
then you only need to type
"sensorcalibutil_yamaha" and press enter. Then follow the steps on the screen.
As far as hanging the bottom edge over the table goes, it's not necessary. The Epic is level on both ends because the camera protrudes at the other.

A couple of weeks ago, i had the problem where sensorcalibutil... in terminal emulator (and adb etc) was failing when trying to execute. Deleting the file above did fix this. So, maybe update the op to only try that if it fails. Thx for putting this together juise
Sent from my SPH-D700 using Tapatalk

decalex said:
A couple of weeks ago, i had the problem where sensorcalibutil... in terminal emulator (and adb etc) was failing when trying to execute. Deleting the file above did fix this. So, maybe update the op to only try that if it fails. Thx for putting this together juise
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Good point. I've never run into that issue myself, and I'm not sure what would cause it, but deleting that file would fix it.

Auto rotation.
Thanks for posting this. I was having this problem on my phone and now it's fixed!

Ahhh! This has finally fixed my auto-rotation issues! My phone has been unable to auto-rotate for months and now it works again. Thanks much!

mattallica76 said:
Nice post! But the Epic does not require all of these steps that other phones might.(assuming your using Terminal Emulator)
Once within terminal, type
"su"
then you only need to type
"sensorcalibutil_yamaha" and press enter. Then follow the steps on the screen.
As far as hanging the bottom edge over the table goes, it's not necessary. The Epic is level on both ends because the camera protrudes at the other.
Click to expand...
Click to collapse
Actually I needed to delete the cfg file with my Epic, so the need is there depending on the problem. This why I say in some cases this may be overkill, but it if you follow the instructions as posted no harm can come of completing all the steps I chose to list. As long as you don't have faulty hardware you should be back in business after completing them.
If my years with BSD/Linux have taught me anything, it's assume nothing! If you know *nix you'll notice that my commands assume nothing about the user environment. To me that is the safest way to provide instructions like these to users that may not be familiar with the OS.

Thank you for this consolidation... for noobies like me, searching all the forums can be a lil intimidating... this may be "overkill" like you said, but it sped up my auto-rotate like nobody's business. You get TWO thumbs up...

juise said:
Actually I needed to delete the cfg file with my Epic, so the need is there depending on the problem. This why I say in some cases this may be overkill, but it if you follow the instructions as posted no harm can come of completing all the steps I chose to list. As long as you don't have faulty hardware you should be back in business after completing them.
If my years with BSD/Linux have taught me anything, it's assume nothing! If you know *nix you'll notice that my commands assume nothing about the user environment. To me that is the safest way to provide instructions like these to users that may not be familiar with the OS.
Click to expand...
Click to collapse
Good philosophy. I'm just currious as to why that file would get corrupted in the first place. Unless folks are trying to restore data from a froyo Rom onto an eclair rom, this should not be happening. The file resides on the data partition which would have been wiped durring the install process, assuming it was done correctly. Ha, there I go assuming again.
Sent from my SPH-D700 using Tapatalk

meh i guess it works. didnt really do anything though.

[Q] Initial issues from a WP7 newbie...

Hi everyone... I'm having some initial problems with my new Optimus 7 device and maybe someone more experienced can help me...
1) After 1min of inactivity, my screen goes totally black... and I cannot seem to unlock it! The only way I found is by holding the camera button, which opens the camera app and then the phone is unlocked... but for sure there is a simpler method! When I try to unlock right after it has locked I can do it by "scrolling up", but after it has gone totally black, it does not work anymore... Is this a bug or am I just stupid?
2) I would like to know the MAC address of my phone... I saw a tutorial for the Samsung Omnia 7 using the MFG app, but the MFG app in LG is different, and I cannot find the MAC there... is there a way to discover the MAC of this device?
I'm sure many more questions will come, but that's it for now...
Many thanks!
Leo.

Alright, it is totally understandable that you may have these issues. First of all, in order to take the phone out of standby, you need to press the 'Power' button at the top right of the phone. It may seem too small at first, but you'll get used to it. When you press the button, the screen lights up and you can scroll up to unlock. As you may have discovered, the 'Camera' button also unlocks the device, but that is a feature to quickly take a photo, not to unlock it.
Secondly, have you installed the MFG app on the LG Optimus 7 yet? If not, bring up the dialer, and dial ##634#, wait for the app to install, and then it will be available like any other app in your 'right flick' list. You can even pin it up to the Home screen if you choose to. Then, enter 277634#*# for the password to enter the app. The following is the path you must take:
7. Engineer Menu > 2. Device Test > 8. WIFI Test > 1. Net.Info.
At which point you should be greeted by the Net.Info. screen showing you the MAC address and the IP address of your device.
Hope this helps. Ask any other questions you have here as well. Welcome to the WP7 Club.

kapanak said:
Alright, it is totally understandable that you may have these issues. First of all, in order to take the phone out of standby, you need to press the 'Power' button at the top right of the phone. It may seem too small at first, but you'll get used to it. When you press the button, the screen lights up and you can scroll up to unlock. As you may have discovered, the 'Camera' button also unlocks the device, but that is a feature to quickly take a photo, not to unlock it.
Secondly, have you installed the MFG app on the LG Optimus 7 yet? If not, bring up the dialer, and dial ##634#, wait for the app to install, and then it will be available like any other app in your 'right flick' list. You can even pin it up to the Home screen if you choose to. Then, enter 277634#*# for the password to enter the app. The following is the path you must take:
7. Engineer Menu > 2. Device Test > 8. WIFI Test > 1. Net.Info.
At which point you should be greeted by the Net.Info. screen showing you the MAC address and the IP address of your device.
Hope this helps. Ask any other questions you have here as well. Welcome to the WP7 Club.
Click to expand...
Click to collapse
Thanks very much! I was going crazy with this lock screen problem... I think they should state this flow more clearly somewhere... anyway, thanks also for the MAC info, I got it also!
For now that's everything! But I'm sure there will be more in the future...

OK, one more small thing that is bothering me...
Does IE (on WP7 of course) has any means to store passwords and auto-complete them? I even looked for some apps, but they didn't seem to integrate with IE...

banvetor said:
OK, one more small thing that is bothering me...
Does IE (on WP7 of course) has any means to store passwords and auto-complete them? I even looked for some apps, but they didn't seem to integrate with IE...
Click to expand...
Click to collapse
As of now, IE does not support any plug-ins, ActiveX (thank God), or any of the regular functions you are used to on a desktop browser. However, I believe autocomplete will come soon. For now though, you should upgrade to NoDo, and use a password manager (I use 7Pass, and Passkeeper), and copy username/passwords from there to your browser...

kapanak said:
As of now, IE does not support any plug-ins, ActiveX (thank God), or any of the regular functions you are used to on a desktop browser. However, I believe autocomplete will come soon. For now though, you should upgrade to NoDo, and use a password manager (I use 7Pass, and Passkeeper), and copy username/passwords from there to your browser...
Click to expand...
Click to collapse
OK, I was afraid of that... unfortunately this didn't come with NoDo (I already have it
It will be a long wait until the next update (Mango, if I remember the name correctly)... it would be very nice if MS would release smaller updates like this more often... this way maybe they could even deploy it faster, since the changes would be small and so would the probability of a grand failure (I guess)
Anyway, one more question came up yesterday: is there any way to show my contacts birthdays on the calendar? I had this same problem on my Nokia... I never understood the reason to have a birthday field on the contacts if they didn't show up on the calendar!
Thanks!
Leo.

[Q] Choose an action missing gallery is making me crazy

Got the new phone other day, really nice so far.
BUT when i choose an uploader button on forums, craigslist or google image search etc… the choose an action menu pops up like normal, but NO gallery icon.
SO how can i upload? Taking a new pic each time is pretty annoying. BTW this worked fine on all my previous droid devices WITHOUT a special craigslist app or google app etc…..

vdubjim said:
Got the new phone other day, really nice so far.
BUT when i choose an uploader button on forums, craigslist or google image search etc… the choose an action menu pops up like normal, but NO gallery icon.
SO how can i upload? Taking a new pic each time is pretty annoying. BTW this worked fine on all my previous droid devices WITHOUT a special craigslist app or google app etc…..
Click to expand...
Click to collapse
It's not clear what you are objecting to. What your droid did is irrelevant. It's not reasonable to expect every phone to be identical for your favourite features. And if that is somehow critical to you.. why did you buy a non-droid phone?
As far as I can tell, you are accustomed to having the gallery icon show up on the action menu and don't like that it's (apparently) not there on your S5. Did you try clicking, "documents" on the action menu? I bet that takes you right into the gallery or a file browser.
Or there are a million other ways to do the same thing too - my files (the stock file browser, various apps, upload from your browser, long press on the recents (left soft) key to access a conventional context menu, the command line.. etc, etc.
If you want, go grab the Google gallery apk and install it and I bet it shows up on the action menu..
.

Umm thanks I guess??
Yes document worked.
The other 12 paragraphs you typed why?
Wtf are you talking about ? I guess htc, Sony and Samsung don't count. Lol
fffft said:
It's not clear what you are objecting to. What your droid did is irrelevant. It's not reasonable to expect every phone to be identical for your favourite features. And if that is somehow critical to you.. why did you buy a non-droid phone?
As far as I can tell, you are accustomed to having the gallery icon show up on the action menu and don't like that it's (apparently) not there on your S5. Did you try clicking, "documents" on the action menu? I bet that takes you right into the gallery or a file browser.
Or there are a million other ways to do the same thing too - my files (the stock file browser, various apps, upload from your browser, long press on the recents (left soft) key to access a conventional context menu, the command line.. etc, etc.
If you want, go grab the Google gallery apk and install it and I bet it shows up on the action menu..
.
Click to expand...
Click to collapse

* plonk *

Dear Vdubjim,
To be completely honest with you the answer you received was quite sensible - outlining many options you do have and hope they can be resolved.
Do note - "droid" - means a Motorola phone with that word in the name (a/p gsmarena.com 4 pieces produced). Therefore - the whole rant about other options in other device maker's skins for Android.
The thing is - there are a lot of people in those forums who do not bother to google for answers and who simply want everything put before them on a plate. This always results in a somewhat sarcastic reply - and personally I'm not surprised. The answer you received was mild and non-offensive - please do take note of that.
Cheers!

Thank you for the insight.
Next time I'll post my search logs.
rnrnrn said:
Dear Vdubjim,
To be completely honest with you the answer you received was quite sensible - outlining many options you do have and hope they can be resolved.
Do note - "droid" - means a Motorola phone with that word in the name (a/p gsmarena.com 4 pieces produced). Therefore - the whole rant about other options in other device maker's skins for Android.
The thing is - there are a lot of people in those forums who do not bother to google for answers and who simply want everything put before them on a plate. This always results in a somewhat sarcastic reply - and personally I'm not surprised. The answer you received was mild and non-offensive - please do take note of that.
Cheers!
Click to expand...
Click to collapse

KODI with - amazon voice search :D (proof of concept)

Hi Guys,
I managed to root my FireTV a few days back, and yesterday decided to look at the voice search to see if I could use it for other things.
After reversing some code, I found the actual voice search is handled by com.amazon.vizzini.apk
The SearchOverlay.class has this piece of code, which calls back to the amazon fireTV UI SearchResultsActivity upon completion with the search result returned as a string.
I replaced the fire TV UI with my own code, which receives the search text, and then sends a JSON rpc to KODI's web interface, and brings KODI to the front after the search is completed.
Here is a video of it in action.
http://youtu.be/hpgKci_gJYY
android studio project
http://uptobox.com/ccykod7zua1l
mirror
http://www107.zippyshare.com/v/mAhl3UuM/file.html
***** I have a FireTV v1 updated to fire os 5 ******
I have no idea if this will work on older versions of software.
To make it work you will require ROOT, and you will have to uninstall or move the existing fireTV amazon UI.
Reason for this is that the vizinni.apk calls back to
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
So your activity has to be in that package, and called SearchResultsActivity.
The only other way to possibly get round this would be to modify the vizinni.apk to call a different package instead, but then voice search wouldn't work on the amazon UI anyway. I wasn't really bothered about the amazon UI working myself which is why I did it the way I did.
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system then installed my code via android studio.
mount -o rw,remount /system
mv /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /system/
You will also need to change KODI's settings to enable web interface control on port 8080.
On my setup it was .. system.. services.. webserver.. and tick the box that says "Allow control of kodi via http" and make sure the port is set to 8080.
edit: 07/07/2016
I did start work a few months back on an Xposed module (works but not 100%), I was going to add a settings page but I think there was issues with xposed on android version that the fire tv runs on, due to permissions etc.
You can set a prefix in the code (currently hard coded to KODI) so if you say " kodi star wars" it would pass the param of "star wars" to kodi.
If you just say "star wars" without the prefix it would pass this to the normal amazon UI.
If anyone wants to take it further, it's attached on the link below.
http://uptobox.com/ensqll4a7r65
Mick

Thats actually pretty great.
Conventional wisdom was that both voice recognition and response "results packaging" was done server side - and the only return query you could get were preexisting amazon database references - not the result of the initial voice recognition.
I've actually read that multiple places - but as it turns out, no one had bothered reversing the process I guess.
Major props and thank god for overlays containing strings... Finally - that microphone might not be so useless after all..
Next step - implement it to interface with google search. (Weather in ...)
edit: Actually - there are three interesting usecases I can think of on top of my head...
1. Launch other Apps (maybe even with "fixed Keywords (App 1 f.e. would work edit: "Number 1" delivers better results. )" if App names arent known to Amazon) - so thats text>launcher app - see if sphinx02 has any interest in coding that as part of Firestarter..
2. google search (Whats the weather in.. ) text>google search app (if possible)
3. direct text input as seen in the POC video
edit 4. forward to Amazon - not to "break" their implementation
This could be realized by a quick 4 way select screen (just confirm with the direction button) after you select the string in the overlay.

great find and implementation. would love see more expansion as above post mentions. Are you planning to share fire tv UI code?

I was playing with voice search strings and found that Amazon tends to strip out "Google" in front of search queries -so instead of "Google how is the Weather tomorrow" only "How is the weather tomorrow" will get returned.
But - Alexa as a trigger word will be returned fine, so - I vote for using "Alexa" as a trigger word to forward all search queries to the google search app.
Ok - maybe not - but conceptually, this would be a great "work of art".

An even better idea than Harklekinrains' would be to check the foreground app and do different things based on that. For example, if Kodi is open it could send the intent to Kodi. If the Fire TV launcher is open it could fall back to default functionality, etc. Simulating keystrokes could also cover 99% of the other applications. I'm excited for this. It really makes the Fire TV so much less of a novelty.

I've just updated the original post with a copy of the android studio project, and a few more details.
Mick

Great mate,thanks! gonna check it out soon!
One question (as im not firm with intents and stuff): aint there a possibility to listen for intents sent to the amazon ui and catch them? Personally, i dont care too much about it right now as im using nothing but kodi, but maybe some day when wanting to use prime or similar stuff?

dafunkydan said:
Great mate,thanks! gonna check it out soon!
One question (as im not firm with intents and stuff): aint there a possibility to listen for intents sent to the amazon ui and catch them? Personally, i dont care too much about it right now as im using nothing but kodi, but maybe some day when wanting to use prime or similar stuff?
Click to expand...
Click to collapse
I don't think so as the actual code in the vinizzi apk is as follows:
Intent localIntent = new Intent();
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
localIntent.putExtra("identifier", null);
localIntent.addFlags(402653184);
localIntent.putExtra("term", str);
localIntent.putExtra("text", str);
localIntent.putExtra("source", "VOICE");
localContext.startActivity(localIntent);
So basically when it receives the voice search response from amazon's server, it's starting the activity com.amazon.tv.launcher.ui.SearchResultsActivity from package com.amazon.tv.launcher
Mick

Integrating the search attempt based on the previous foreground app would mean that "voice search" could never "initate a new attempt". This would prevent the "lets just ask google, or lets launch an app - impulse use" of the feature. Still - in the long term it might turn out to be the right approach - f.e. if
"People tend to use the the google search only lets say "half a dozen times", and in the majority of cases just want text input in Kodi" Also - without having a select screen with "four (dont make it too many) predefined "use options"" discoverability is pretty non existent. People would have to read readmes to find out which interactions are supported.
Also Amazon wants you to "be able to always reach the Amazon content search from anywhere" - so, political implications.
Also - each time a new app would want to integrate the voice to text feature - they would have to contact the devs of this project - if you dont use "just text input" as a default in the "use the previously open app as an indicator of intent" approach. So make sure you default to "just text input" in that case. (Amazon launcher > forward query to Amazon (do not break functionality), ....)
Dont implement it as a mixed approach though as "Kodi is open most of the time" probably for most people - and the intent (message) gets "confusing".
--
What you probably shouldnt do - regardless, is to use "trigger words" as an "indicator of intent" - because Amazon can start blocking them. "Number 1" is probably generic enough so they wont try to block that - but in principal, they can. Also Amazons "voice to text" engine is optimized for "short phrases" - the longer your input query gets the more prone to errors their results become. Leave the actual "voice input" as "natural" as possible (dont embed logic there). Imho.

I'm in the USA and uptobox.com is not available in our country.
I want to give the source a look and see what I can do to contribute.
Can you put it on github or somewhere else?
Much appreciated.

kratosjohn said:
I'm in the USA and uptobox.com is not available in our country.
I want to give the source a look and see what I can do to contribute.
Can you put it on github or somewhere else?
Much appreciated.
Click to expand...
Click to collapse
I've just uploaded it to zippyshare too. Link added to original post.
Mick

It would be nice if this could be generic way of entering text in any app, similar to the FTV Remote App that has keyboard support. I am surprised Amazon has not done this already. If you are in a text field voice search would fill in the text, else it can continue with normal Alexa functionality letting you " always reach the Amazon content search from anywhere". Should be an easy solution for Amazon to implement, not sure if it could be added with the progress here, and it would really make the voice control so much more useful.

Hey Mick, as im still very exited about that (so frustating to enter searchphrases with a dpad...), i thought about what your great find could develop to. I hope u dont get me wrong, as i unfortunatly cant contribute any programming (if u need something made with tasker let me know ), its not that i want to demand anything - rather share my thoughts or ideas...
- I think its a good thought not to 'blow it up' by adding many keywords, make it more complicated, and avoid amzn to lock features down. even if it may be an abstract fear. I think with a well-structured menu in kodi, all apps one will need to start are just 2-3 clicks away.
- if i got it right, xposed could hook into every module and alter it, right? so basically it should be possible to avoid to exchange the amazon ui and/or alter the vizinni.apk,but just modify the SearchOverlay.class? wouldnt it be (on top) the most convenient way to decide wether one is on e.g. Amazon Prime, or on kodi, and either hand over the result to the original module, or hand it over to kodi?
So, please understand my post as a mixture between sugestions and questions, not as a demanding 'please make it how i want it asap'. Im really excited about your finding, appreciate your sharing, and want to contribute what i can do - unfortunatly its rather thoughts and suggestions. Cheers mate!

Great Work !!! I totally understand this is for amazon Fire products only. My question is would we be able to port for generic Android TV box like nVidia Shield which also has mic capability and comes with root support.

Good job @is0-mick it's great to see you accomplish something that Netflix doesn't even want to be bother with on their app.

harlekinrains said:
No you dont understand. You havent even read or understood the first posting - but you have bought another device and now want others to move in your direction on your behalf.
Click to expand...
Click to collapse
Seriously mate if XDA bothers you so much, you need to take a break from it for your own sanity!

fach1708 said:
Seriously mate if XDA bothers you so much, you need to take a break from it for your own sanity!
Click to expand...
Click to collapse
No, I really don't think he needs to take break, his argument is completely understandable. This is not a Shield forum (btw before we make judgements, I own both devices). We need to get this fixed for one device, before even mentioning whether other devices are an option.

is0-mick said:
To make it work you will require ROOT, and you will have to uninstall or move the existing fireTV amazon UI.
Reason for this is that the vizinni.apk calls back to
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
So your activity has to be in that package, and called SearchResultsActivity.
The only other way to possibly get round this would be to modify the vizinni.apk to call a different package instead, but then voice search wouldn't work on the amazon UI anyway. I wasn't really bothered about the amazon UI working myself which is why I did it the way I did.
Click to expand...
Click to collapse
Is it not usefull for this to create a xposed mod? I thought xposed was made for this...
Perhaps you should talk with rbox in his thread about a integration into version 1.5 of his mods, look here.
is0-mick said:
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system then installed my code via android studio.
mount -o rw,remount /system
mv /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /system/
Click to expand...
Click to collapse
So does that mean, while you are using your proof-of-concept you can not use the normal Launcher-UI?
Really great your work! I hope we got more
Sadly I am with my FireTV-Stick (hardware-Rooted-superSU) and my FireTV box gen1 (hardware-Rooted-superSU+custom-recovery+unlocked-bl)on the old FW. I wait for custom roms.
Greetings by Idijt
EDIT:
I forgot to ask you something. Did you got the kind of search-request back?
Can you see if amazon-voice-rgn knows if it is a app or a video or a moviestar?

This looks pretty cool since I don't like typing the name of the movie in the search box... now I can just speak it.
As a novice I have one question, You wrote:
is0-mick said:
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system
Mick
Click to expand...
Click to collapse
The code I downloaded was in .RAR format not .apk. Do I need to covert it to .apk or rename it to .apk before replacing the original?
I've not rooted my device yet so I haven't looked at the file structure, but I'd be willing to root to get this feature. OR is the adding of this code better done by someone other than a novice?
Thanks

carpenter940 said:
The code I downloaded was in .RAR format not .apk. Do I need to covert it to .apk or rename it to .apk before replacing the original?
Click to expand...
Click to collapse
It's the source code. You have to compile it and create the apk with AndroidStudio.