Hey guys first time poster here.
Ive been trying to search around but cant find any real solutions.
I find the stock phone dialer app terrible as you cant have favourites and just the overall appearance of it aswell is a little plain.
I downloaded the app dialer and I like the look and functionality of it but when i press to call someone it goes to the stock dialer but it takes about 15 seconds to get there.
Someone please help!
The standard dialers you find on play store do not implement HFP-CLIENT.
To my knowledge, there are three hfp-client dialers available;
1) The binary only one that the thing ships with,
2) The new one added to AOSP8 here: https://android.googlesource.com/platform/packages/apps/Car/Dialer/
3) The qualcomm test application available on codeaurora.
There are problems with all of them for this application.
Specifically, as you note, option (1) is absolutely terrible.
A common problem with option (2) and (3) is that they don't interface with the chinese audio control hacks, which means that when you switch to a call, the audio won't come through.
An additional problem with option (2) is that it doesn't compile with less than Android 7.0 -- even though it actually specifies a minimum of 6.0, it depends on something with a minimum of 7.0.
An additional problem with option (3) is that it is a test application through and through, it doesn't implement the necessary background service to pop up a notification you can click on to answer a call. The application has to actually be *open* to do anything.
But aside from those problems with (2) and (3), the *good* thing about them, is that they are open source, which means that anybody who wants to adjust them so that they do work, can do so.
If I was going to pick somewhere to start with this, it would be with option (2). It is a dialer meant for end users, and would take a lot less work to adjust it to (a) compile, and (b) implement the needed audio hacks. Although technically, I do have option (3) working, as I mentioned, it has to actually be open in the foreground to do anything, and it doesn't implement the audio hacks.
Hi,
Apologies for the noob question but what do you do with the code in option 2 to install it on the headunit?
Thanks!
luciusfox said:
The standard dialers you find on play store do not implement HFP-CLIENT.
To my knowledge, there are three hfp-client dialers available;
1) The binary only one that the thing ships with,
2) The new one added to AOSP8 here: https://android.googlesource.com/platform/packages/apps/Car/Dialer/
3) The qualcomm test application available on codeaurora.
There are problems with all of them for this application.
Specifically, as you note, option (1) is absolutely terrible.
A common problem with option (2) and (3) is that they don't interface with the chinese audio control hacks, which means that when you switch to a call, the audio won't come through.
An additional problem with option (2) is that it doesn't compile with less than Android 7.0 -- even though it actually specifies a minimum of 6.0, it depends on something with a minimum of 7.0.
An additional problem with option (3) is that it is a test application through and through, it doesn't implement the necessary background service to pop up a notification you can click on to answer a call. The application has to actually be *open* to do anything.
But aside from those problems with (2) and (3), the *good* thing about them, is that they are open source, which means that anybody who wants to adjust them so that they do work, can do so.
If I was going to pick somewhere to start with this, it would be with option (2). It is a dialer meant for end users, and would take a lot less work to adjust it to (a) compile, and (b) implement the needed audio hacks. Although technically, I do have option (3) working, as I mentioned, it has to actually be open in the foreground to do anything, and it doesn't implement the audio hacks.
Click to expand...
Click to collapse
I just bought a Seicane unit. The model is listed as sp9853i in the settings screen. I haven't been able to find a lot of information anywhere about this unit. I have been trying to get a different HFP-enabled phone dialer, but no luck so far.
I did try installing FCC Launcher, which lists dialing through BT as a feature. However, it looks like the Seicane sp9853i provides the actual bluetooth functionality in the actual launcher. When I start FCC launcher, BT disconnects. Also, the BT properties are not available under Android settings, which is not terribly surprising, since it's a head unit, not a phone.
Related
Ok I had gotten board with the lack of wifi and decent web browser on the Treo 650 that I decided to make the move to the 8125. I knew about the speed difference and some of the other issues discussed in these forums because I researched the device for months before making the move. Therefore I wont say much about that. Unfortunately I have a few issues that I can't seem to find answers for in this forum and I was hoping other users out there could help.
1. Is there any way of making the navigation pad useful? I cant access anything on the taskbar and it would be great if I could. I installed magic button so I can close apps and switch back to home when I want. Furthermore there is almost no documentation on how to use the nav pad. All application instructions say tap the icon. It's very convenient to have one handed use. for example i have yet to figure out how to get back to the location bar in Pocket IE so I can enter a url without having to tap the screen.
2. Is it common that some applications just freak out when you switch to landscape mode (scroll bars not working and such)?
3. As mentioned I installed magic button but is there an application that will pop up a list of running tasks so I can switch between them easily with the navigation pad.
4. Backup. I may be very wrong on this but I fear that active sync does not actually backup my entire device like palm does. Could someone clear this up and if I'm correct is there a way for active sync to do this. I have more programs on this device than what is on my add/remove prog screen.
5. Notification reminders. I see a feature to have the led for a period of time but it would be nicer if it could be set to play its sound also. Like the pagers of old.
6. Notification of lost service. This phone never tells me I have no cell service. Last thing I want is battery draining searching or worse assuming I have service and miss all calls.
If anyone could provide some info on the above it would be a great help. i have already found many other programs that make up for the lacking features. Below is a list of what I have installed please make any suggestions you think would be helpful.
1. AnthaVPN - easiest and fastest to install
2. TN520 by mochasoft
3. Pocket Putty SSH client
4. Eyes On Call - Callfilter like program with many features still limited but the developer is very quick in implementing suggestions.
5. Info sharp - same developer as above but this provides sms capabilities that are very impressive. He almost has chat style sms with the way this program works.
6. OMAPclocker - for clocking to 220. I actually see the difference.
7. IM+ - Sametime/AOL instant messenger client.
8. Info apps I have Metro, Ereader, Bdicty, VadeMecum
9. TCPMP
10. Registry Wizard
11. Calc98 - the built in calc app is a joke.
12. Xpressmail - dont care what anyone says this app does what it says it will do. Pushes email to your phone.
Thank You
- Richard
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.
Since i got a new/old car and i am not too happy with its radio right now I would like to exchange it and get an android device.
Actually right now I am a bit torn between an android unit and a pc. I know the pc is more expensive but as I read around the internet, right now it has the following advantages for me:
1. I can choose freely which hardware it has.
2. Bluetooth works fine.
3. It will support Windows 10 so i can use cortana - which will give me the option to use it more or less hands free.
4. I can use Kodi for Radio etc.
5. it might just run android as well
6. pretty much all apps are more or less available
7. with Kodi i can customize the look (in my opinion way beyond of what i could do with different launchers)
8. Kodi supports radio traffic service
Now that I have listed all the + Notes on the PC version here comes Android:
1. A lot cheaper!
2. Works out of the box.
3. I don't have to buy the apps again (as i have bought them already and use them on my phone)
4. Theoretically I can use Kodi (afaik "just" not for radio)
5. Afaik bigger community
BUT(!)
I was digging around and found following problems which i'd like to ask you guys if they are still an issue:
1.) So far no Android 6.... so no Google Voice for hands free
2.) Bluetooth is at best buggy (incomeing calls show no name from the phonebook just the number) other devices such as obd do not work or if they work only the ones from the manufacturer of the headunit will work. Bluetooth connectivity is limited to one device at a time.
3.) I am limited to the Apps from the manufacturer as far as radio goes. (i think most of the apps i have seen are ugly - i don't want to see the frequency of the station I am listening to... especially not as big as i have seen it.) DAB(+) Apps look somewhat ugly as well. There is no real chance to change that.
4.) there is no support for radio traffic service
5.) Customization is limited
My questions are:
1.) Is what I am saying still correct (for example the bluetooth issues).
2.) Does anyone know a work around for the Google Voice? Preferably without the need to press a button. Or has someone an Android 6 device and can confirm that Ok Google works fine there?
3.) Is it at all possible to implement the Radio(FM/DAB+) into Kodi on Android - has someone done this? Maybe even something like a navigation software? (yes - i am a kodi fanboy -actually more or less from day one - i had a old xbox - the first xbox running xbmc in my car with linux and a gps built in)
What I would like to have in the end would be a system where Kodi is loaded up as soon as the car starts.
Via Tasker (if possible) I would grab the infos from torque and implement them in a custom skin in kodi. I would love to listen to the radio via Kodi and if at all possible have navigation in there as well (but if that does not work I will find a workaround - i already have one in my head)
I know this is a lot and many of you might think tl;dr but if anyone could answer my questions anywhere I am convinced that it is here on the mighty xda board.
Thank you guys so much. (If I get this all to work I will of course post all of it here (skins, tasker skripts etc)
About Android vs Windows and head unit vs PC, I think you'll have to decide on that for yourself. Nobody here can tell you what's the right choice for you.
As for Kodi, I haven't dived into it much, but I have a more typical use of the head unit I guess. Google voice works in 5.1.1, but you need another launcher and you need to install the required apps from Google Play and enable everything. I have it working in mine, but decided to have it activate on a button press. I do have to switch between apps and stuff, and the BT caller app is a little quirky to use. I would've wanted something more inline with the default Google dialer, but no go on that one. Even if you install Contacts and the Google Phone app, they don't really do anything. If you want complete control over everything, then PC and Windows (or <insert OS her>) would be the best choice for you. If you want to save time and have something that is fairly easy and quick to set up out of the box, then a head unit with Android would be better.
Thx Hilari0 for your answer.
May I ask what Unit you have. What are the pitfalls? How did you manage to solve or work around the Bluetooth problems (i saw that joying for example released an update - can anyone tell me if that fixes the bluetooth problems?)
Is it more complicated than on other devices to install another launcher?
Thank you!
I have the Joying Intel 2GB/32GB head unit, the 135 variant. The bluetooth on it worked well out of the box with the update installed, but it was vastly improved following the instructions in this thread:
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
So I was wondering how many of you had gone through with implementing the buildprop change that enables Google AI. I decided to do it the other night and have been fiddling around with it since then. If you haven't done it, it basically turns Now-on-Tap into "Voice Search by default," but you can still do screen searches for things like USPS Tracking and Phone/Address Lookup. Voice searches are vastly improved; it will auto-start Navigation, fetch links as a list of cards (for example, miniaturized news feeds), open apps instantly (provided the phone isn't locked), and essentially just be all around snappier than Google Now/Now-on-Tap.
That said, it does bother me that the phone literally had to be rebranded as a Pixel to make this work. A) It's not the most stable change, and 2) that change is now reflected on any device/prompt that interacts with my phone. It managed to be picked up by adware on a sketchy site (don't ask what sketchy sites I go to), and my desktop also mislabels it on USB connection. Does anyone know if Motorola allows you to change the device name for USB connection? I know LG lets you.
But yeah, those are my thoughts on it. I might try it out for a week or two, and if I'm not exactly bowled over by it, I'll probably just go back to Now-on-Tap. But I wanted to hear your guys' thoughts.
I don't even use now-on-tap, and I've done the assistant bulildprop trick before, and it made little to no difference on how often I use both of them. I understand what you mean by having to rebrand it to a pixel though - Google shouldn't make this Pixel exclusive
Couldn't find that one listened anywhere here specifically. I'm pretty sure my phones compromised but I'll probably just get people telling me I'm being paranoid. Just notice a lot of weird stuff going on.
I'll give some examples, but it would be cool if someone else here has an A03s and could give me a full list of the system apps to know for sure if mine has some extra ones that aren't truly factory. Because I've restore it several times and they don't go away.
Like under the apps screen under the basic ones I got apps like Android auto, webview, configapk, customization service, and something called data restore tool, device health services, group sharing, meet, nearby device sharing, quick sharing, quick share, settings..etc. which to my knowledge are pretty normal apps to see on phones right? But I seem unable to control them, if I disable them and go back and check later they mysteriously reenabled again, or after that the permissions lists will be greyed out not being able to do anything. Also there is a app called "permissions controller", as well as ones called "apps", "apps update", "tools", "app recommendations", "settings recommendations"..etc. is that normal? I never noticed that with my old samsung. They are really small file size apps with pretty generic looking icons and they don't let me disable them.
What gets more weird to me though is when I enable the system apps too. I see all kinds of suspicious looking ****.
Like for the android setup, and android system apps there are two of each, and the other two have generic looking icons, also got stuff like configuration restore, audio mirroring, auto hotspot, automation test, bluetooth/bluetooth midi service, call & text on other devices, callbgprovider, camera extensions proxy, carrier login engine, sim tool kit, cell broadcast services, clipboardsaveservice, cmh provider, companion device manager (where I have no idea where my "companion is or how to control it so I must be the one being controlled?", configupdater, csc, dcktimesyncapplication, dynamic system updates, ipservice, enterprise sim pin service, external storage, like 10 different gestural navigation bars, group sharing, iaft, ims service, settings, and logging, input devices, iothiddenmenu, keycustomizationinfobnr, launcher, locale overlay manager, service mode and service mode ril, media and devices, mdmapp, vpndialogs, mmigroup,mmsservice, mobilewips, mtp host, nearby device scanning (2 instances), network diagnostic, nsdswebapp, one handed mode, osulogin, package installer, an app called "people", private share, proxy handler, quick share agent, samsung core services? (is that a real app even? I can disable it but who wants to disable "core" system apps, so touche there if it is a program deployed by a hacker on their app naming skills lol, smart switch agent, 2 instances of software update, system connectivity resources, system uwb/wifi resources, an app called "tasks", tethering, tethering provision and tethering automation, tfstatus/tffunlock always running when I never access them, usbsettings, and theres one called wallpaper services/wallpaper and style that looks really generic which is confusing because I assumed the samsung theme manager just handled all that stuff in one? We also got wearable manager installer running, and sometimes wificalling and wifi direct or work setup will be running when I don't have any of those configured.
Sorry for the huge block of text, I'm sure I missed a bunch i missed because there's some that don't show even when you tap "show system apps", like the skms agent as one example, so got a few general questions for you, so for the file/download system I got a bunch of default apps. There's two different files apps, there's a download manager and download app, and also a storage manager, and ALSO a app called the external storage that always wants to be running but can you explain that if I have no external storage? Is the built in storage space on the a03 called external storage? I even have my drive apps and stuff disabled.
Another things that's suspicious to me is secmediastorage, secvideoengineservice, secsoundpicker, secureelementapplication, media and devices + ext storage. Like why should there be a SECOND video or audio engine running when I'm old school and don't even use cast programs/features or anything like that? In fact it's usually one of the first things I just go ahead and try disable.
I noticed a lot of weird things going on with the display though too, looking really sharp then suddenly almost looking like there's two layers of gui not exactly lined up, like off by a pixels making things look blurrier. Like the one ui home is the default factory launcher right? So why does my phone also have a app called "launcher", plus another hidden launcher or something running in the background? I can't remember the name of it offhand, something GUI..
And I understand the concept of android have a permission controller, and "core apps" but are there actually apps under the system apps named that lol? "permission controller", "samsung core apps" one called "device services"...
also is service mode suppose to be running in the background? I googled into it and know it's a genuine service, but I really don't understand why a lot of these apps are stopping and running or renabling themselves.. It's like I have zero control over my own phone and if I'm just paranoid and they are meant to be just seems like a waste of complete waste of ram/data to me.
****, I was just sitting here thinking for like a few minutes about to post and almost forgot the most suspicious ones I've noticed in last few days. all the "com." overlay apps. I guess I really saw the word "overlay" as something you should be suspicious about until the vpn I recently bought had a feature that is suppose to block web browser based overlays. Then I noticed that MOST of my com. apps are all overlay apps! Lol, ranging from google/samsung to mediatek.
I won't post all of them because there's probably 20 at least but here's a few.
com.mediatek.frameworkresoverlay
com.mediatek.settingsproviderresoverlay
com.mediatek.systemuiresoverlay
com.samsung.android.networkstaack.tethering.overlay
com.samsung.android.smartswitchassistant
com.samsung.android.wifi.p2paware.resources
com.sec.android.app.camerasaver and a camera.app.cameraapp one (camera always running in background even if background and battery saver with restricted settings enabled)
com.google.android.ondevicepersonalization.services (I never used any personalization service or see a personalization app for that matter)
com.google.android.networkstack.tethering.overlay
and there's a bunch of com.google.android.overlay.gmsconfig ones /common geotz/ gsa/ photos/
com.google.android.overlay.modules.captiveportallogin.forframework
plus a overlay broadcastreceiver, ext.services, documentsui, permissioncontroller, and sdksandbox one.. tetheringresoverlay, wcmurlsnetworkstackoverlay, locale overlay manager..etc.
Also I get my service through straight talk which I think uses verizon and I noticed when I go to connections/mobile networks and network operators and uncheck the box "select automatically" that for some reason it only wants to connect to a network operator called "Home". I just thought that was kind of a weird and generic name for a network operator. I tried to use a android hidden settings app to change that because it was blocked out and thought I messed up my phone because I no longer had data and couldn't access the menu through the app anymore, but luckily a reformat fixed it but I'm still dealing with all this crap haha.
Can someone tell me I'm not crazy and there's definitely someone that is accessing and controlling my phone without my permission and what would be the best way to go about dealing with this?
Thanks.
First things fist: Here on XDA we expect you to follow the Forum Rules:
2.5 All members are expected to read and adhere to the XDA rules.
Click to expand...
Click to collapse
If you haven't done that yet, click the link in my signature and do it now.
One of the rules you'll notice is this one:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Click to expand...
Click to collapse
You've copied this post at least once. We'll be removing the duplicate.
Now on to your question...
It is my opinion that the problem may not be with what you are observing, but with your assumptions. In the duplicate thread, you assume two possibilities:
You're being hacked
Your paranoia is justified
Have you thought there may be a third or even fourth option? Such as, maybe you don't understand that much about Android, you don't recognize what you see, you're assuming it's malicious, which combined with your own confirmation bias, has led you to the conclusion that foul play is afoot?
Nothing you have described sounds in any way abnormal. You have a Samsung device running OneUI (Samsung's framework overlaid on top of Android) that is powered by a Mediatek chipset. Everything you describe sounds completely normal to me, with over 10 years of experience in Android, most of that with Samsung devices.
My conclusion, to be frank: You are not being hacked, and your paranoia is unfounded.
OP your post gave me a headache trying to read it.
So...
Have it reflash to the stock firmware if you really think it's behaving erratically and a factory reset doesn't work. Change Google password and all others.
Then be careful what you install.
Don't put in foreign thumb drives or let others use it.