Related
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Thanks for your answer. I will just unfreeze freezed apps once 5.0 is available.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Click to expand...
Click to collapse
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
aviwdoowks said:
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Click to expand...
Click to collapse
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
KidJoe said:
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Click to expand...
Click to collapse
+1
kenosis said:
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't used that app. Best thing to say is take an app that you know what the apk name is, use Android Tuner to freeze it, then use a root capable file explorer to look for the apk. If it's still named correctly and located in the original place on the phone, then you should be ok.
Like many others I don't always like the updates to some of my installed apps. Yet it is a hassle to avoid accidentally installing an unwanted update. It is so much easier to click on "update all" in Google Play instead of going through each app's update individually.
Yet I have not found a way to make an installed and purchased app safe from updating. Titanium backup's "detach from market" does not work.
May I suggest a module that would prevent an app from updating? Maybe by making its app files write only?
I think a package like that would be useful. But an easy workaround in the mean time would be to go to Google play store settings and change the automatic update to never.
I already don't allow automatic updates but it is still a nuisance to have to pick through and avoid the persistent update notifications.
I currently use Changelog Droid to accomplish this, although I'd certainly welcome a module to replace it.
Yes, that will tell me what the update changes. I'm looking for something that would "prevent" the update.
this would help me a lot as well. im sure there is a module somewhere that will detach an app from the market and it would just stop showing in the pay store updates.
I think it would help a lot of users. Titanium backup has had that feature for years but it hasn't worked for years. Every time the play store refreshes it reattaches the app.
I am not a programmer but it seems to me that if a tool made an installed app's main files "read only" any attempted update would simply fail, which would solve the problem. Wouldn't that work?
Right now, I try to avoid certain updates but if I accidentally update I use titanium backup to restore the previous backed up version. But it would be nice if it could be simpler. I don't understand why the play store insists on forcing updates.
maybeme2 said:
I think it would help a lot of users. Titanium backup has had that feature for years but it hasn't worked for years. Every time the play store refreshes it reattaches the app.
I am not a programmer but it seems to me that if a tool made an installed app's main files "read only" any attempted update would simply fail, which would solve the problem. Wouldn't that work?
Right now, I try to avoid certain updates but if I accidentally update I use titanium backup to restore the previous backed up version. But it would be nice if it could be simpler. I don't understand why the play store insists on forcing updates.
Click to expand...
Click to collapse
There is some kind of workaround for this issue.
You can use Raccoon to download .apk files from the Play Store to your computer (you can also download previous app versions, search the thread for it). Afterwards, use the app ZipSigner to sign the downloaded .apk with your own key. If required, uninstall the official app version, reboot, install the newly signed .apk and reboot again. Now the update notification from Google Play Store should be gone as the app isn't signed with the same key as the official one from Play Store.
Thank you. I'll try that. Thanks for taking the time to help.
orville87 said:
There is some kind of workaround for this issue.
You can use Raccoon to download .apk files from the Play Store to your computer (you can also download previous app versions, search the thread for it). Afterwards, use the app ZipSigner to sign the downloaded .apk with your own key. If required, uninstall the official app version, reboot, install the newly signed .apk and reboot again. Now the update notification from Google Play Store should be gone as the app isn't signed with the same key as the official one from Play Store.
Click to expand...
Click to collapse
thanks for the workaround. can i use titanium backup to restore the data of the app after download and signing it?
+1
resitm said:
thanks for the workaround. can i use titanium backup to restore the data of the app after download and signing it?
Click to expand...
Click to collapse
maybeme2 said:
+1
Click to expand...
Click to collapse
Yes, you can That's one huge advantage of the described method :good:
Google Play Store checks for the sign code, whereas Titanium Backup depends on the package name (which isn't changed during signing process).
orville87 said:
Yes, you can That's one huge advantage of the described method :good:
Google Play Store checks for the sign code, whereas Titanium Backup depends on the package name (which isn't changed during signing process).
Click to expand...
Click to collapse
I signed the apk and ended up with a zip file, so i flashed that and got the attached error. What am i doing wrong? Got the apk from the developer website which might be causing the issue.
resitm said:
I signed the apk and ended up with a zip file, so i flashed that and got the attached error. What am i doing wrong? Got the apk from the developer website which might be causing the issue.
Click to expand...
Click to collapse
You can select if you want to sign the .apk as .zip or as .apk file (.apk files are .zip files, just with another file type). Don't flash them via recovery. If you can't find the option to sign the .apk as .apk, just sign it as .zip and rename it to .apk afterwards.
orville87 said:
You can select if you want to sign the .apk as .zip or as .apk file (.apk files are .zip files, just with another file type). Don't flash them via recovery. If you can't find the option to sign the .apk as .apk, just sign it as .zip and rename it to .apk afterwards.
Click to expand...
Click to collapse
Thank you very much, i didnt know i could change the output to apk. The app no longer appears in the play store.
I am wondering if someone can make a flashable zip to remove all AOSP apps like phone, contacts, calendar, calculator, mail etc. All this apps are old dinosaurs apps and I am replacing them every time when I flash ROM. Also same thing with Music FX or DSP Manager. Because I am using Viper4Android I have to remove them before I flash Viper.
I have no skill come to that but will be nice if someone can create flashable zip or aroma installer which will remove all of that. Anyone?
"...old dinosaur apps..."
That still work. But I understand where you're coming from. With Google now updating most apps included in AOSP through the Play Store now the versions still in AOSP no longer get updated. What are you replacing these apps with, and is it a flashable zip you're using or a manual install?
simunovic said:
I am wondering if someone can make a flashable zip to remove all AOSP apps like phone, contacts, calendar, calculator, mail etc. All this apps are old dinosaurs apps and I am replacing them every time when I flash ROM. Also same thing with Music FX or DSP Manager. Because I am using Viper4Android I have to remove them before I flash Viper.
I have no skill come to that but will be nice if someone can create flashable zip or aroma installer which will remove all of that. Anyone?
Click to expand...
Click to collapse
If you install "Stock" or "Super" OpenGapps, it automatically replaces them I believe.
MrBrady said:
If you install "Stock" or "Super" OpenGapps, it automatically replaces them I believe.
Click to expand...
Click to collapse
Yes, also with aroma open gapps I can simply replace anything I need. But, there is a catch. All this apps when they get updated in Google Play they stay where they are and new copy is installed like a duplicate. So you can uninstall update and get back to old version. That part I don't like. Why on Earth I need old app?
While apps installed from Google Play when they get updated they will be simply replaced. That is the reason why I would like to create aroma installer to remove all this apps from the system. Then I choose pico apps and everything else grab from Play Store.
I believe that make sense, right?
simunovic said:
Yes, also with aroma open gapps I can simply replace anything I need. But, there is a catch. All this apps when they get updated in Google Play they stay where they are and new copy is installed like a duplicate. So you can uninstall update and get back to old version. That part I don't like. Why on Earth I need old app?
While apps installed from Google Play when they get updated they will be simply replaced. That is the reason why I would like to create aroma installer to remove all this apps from the system. Then I choose pico apps and everything else grab from Play Store.
I believe that make sense, right?
Click to expand...
Click to collapse
There appear to be duplicates because the original GAPPS package installed the AOSP version as a System App. When the app gets updated from the Play Store, the update is installed as a User App. So when you re-install/dirty install with the Stock or AROMA package, it does remove the System version, but not the Updated/User Version.
The only way around this that I know of is to not let apps update or install the desired GAPPS package from the very beginning.
There are also flashable mods that remove GAPPS, like this one: http://forum.xda-developers.com/nexus-6p/themes-apps/script-google-apps-debloater-t3446118. It works on the Nexus 6 as well, although it doesn't remove 100% of what it says it does. It's been hit-and-miss for me, but does work for the major debloat (international keyboards).
MrBrady said:
There appear to be duplicates because the original GAPPS package installed the AOSP version as a System App. When the app gets updated from the Play Store, the update is installed as a User App. So when you re-install/dirty install with the Stock or AROMA package, it does remove the System version, but not the Updated/User Version.
The only way around this that I know of is to not let apps update or install the desired GAPPS package from the very beginning.
There are also flashable mods that remove GAPPS, like this one: http://forum.xda-developers.com/nexus-6p/themes-apps/script-google-apps-debloater-t3446118. It works on the Nexus 6 as well, although it doesn't remove 100% of what it says it does. It's been hit-and-miss for me, but does work for the major debloat (international keyboards).
Click to expand...
Click to collapse
Dirty flashing instead of updating core apps is just to much to play for me. I don't have that time anymore ;(
I like to keep it simple is possible.
That script is very similar to what I am trying to do. I need same thing but with AOSP core apps plus music fx and dsp manager to be included also. That way my way of flashing will look like: flash ROM, remove AOSP core apps, flash pico open apps, flash viper, supersu... done
Now all I need to do download the rest from G play. Updating will not make any duplicates. All is clean, lean and fast
Strephon Alkhalikoi said:
"...old dinosaur apps..."
That still work. But I understand where you're coming from. With Google now updating most apps included in AOSP through the Play Store now the versions still in AOSP no longer get updated. What are you replacing these apps with, and is it a flashable zip you're using or a manual install?
Click to expand...
Click to collapse
I am updating them with original Google versions from G Play.
If you really want to do this, the best way is by doing, because it's unlikely anyone is going to do it for you. Download a flashable zip from the forums, unzip it, extract the updater-script from the META-INF folder and open it. See what the script does, and then try making your changes to that script. Each app you want to delete will be on its own line in the script, and each will use either of the following commands.
Code:
delete("system/app/folder/apk");
delete_recursive("system/app/folder");
In the above, folder is the app's folder, and apk refers to the app itself. The first removes individual files. The second removes entire folders.
Strephon Alkhalikoi said:
If you really want to do this, the best way is by doing, because it's unlikely anyone is going to do it for you. Download a flashable zip from the forums, unzip it, extract the updater-script from the META-INF folder and open it. See what the script does, and then try making your changes to that script. Each app you want to delete will be on its own line in the script, and each will use either of the following commands.
Code:
delete("system/app/folder/apk");
delete_recursive("system/app/folder");
In the above, folder is the app's folder, and apk refers to the app itself. The first removes individual files. The second removes entire folders.
Click to expand...
Click to collapse
Thanks a lot. I will give it a try. Not my thing but seems simple enough
Emilius said:
I am wondering if someone can make a flashable zip to remove all AOSP apps like phone, contacts, calendar, calculator, mail etc. All this apps are old dinosaurs apps and I am replacing them every time when I flash ROM. Also same thing with Music FX or DSP Manager. Because I am using Viper4Android I have to remove them before I flash Viper.
I have no skill come to that but will be nice if someone can create flashable zip or aroma installer which will remove all of that. Anyone?
Click to expand...
Click to collapse
If you can boot into OS before removing them, then you can just root your device then get a file manager that you can give root access before going into the filesystem and just deleting the apps from there.
Hello Magisk community,
i put together a module which installs system-less the Google Dialer v2.3.12 with Magisk.
Tested and working on my Moto X Pure - XT1572 with Marshmallow 6.0.1, Magisk 10.2 and Magisk-Manager 3.0,
Should work on other stock Roms, etc. as framework and permission files a standard files.
Included files:
- com.google.android.dialer.support.jar (framework)
- com.google.android.dialer.support.xml (permission)
- GoogleDialer.apk (Google Dialer)
Do not forget to set the Google Dialer as default app in Configuration - Applications
Notes:
I used version 2.3.1.2 as it is to my knowledge the latest version which works flawless with
- Caller ID
- Places Nearby
- Call blocking
- TeslaUnread from Nova Launcher
- No FC when entering configuration
All later versions, specifically those with the new design v5.+ have problems with Nearby and Tesla Unread on Marshmallow (Google-Dialer will not be recognized by TeslaUnread as default dialer).
Anyway you can update the dialer by downloading the apk from "http://www.apkmirror.com/".
Latest limited working version is 5.1.13122 (Nearby and Tesla not working)
If somebody finds a later version working with all above features, let me know and i will update the Module.
Also i did not include "Google Contacts" as it can be installed as a user app with no problems.
Wishes and suggestions welcome.
Have fun.
I installed this on a stock Xperia Z5 (E6653) and it installs properly and I can open the Google Dialer. The issue I'm having is that I can't enable permissions for the Google Dialer because it tells me I need to disable overlays for the app. When I go into settings to try to disable it, the Google Dialer does not show up, so I can't enable/disable overlays. Calling doesn't seem to work either, I think again because I can't change permissions.
I was able to update the app through the Play Store though, so at least I know that works. Maybe it's an issue with Sony firmware. Maybe you could post a zip that doesn't include the apk and I can try installing it as a user app and see if it works that way?
The apk you can extract from the zip file. If you want only to install the framework and permission file with Magisk delete the priv-app folder under /system in the zip file. That's it.
Thomas_BA said:
The apk you can extract from the zip file. If you want only to install the framework and permission file with Magisk delete the priv-app folder under /system in the zip file. That's it.
Click to expand...
Click to collapse
It works.
I deleted the folder from /Magisk/GoogleDialer/system/priv-app, enabled the module, rebooted, and installed that the same version of the Google Dialer from apkmirror.com. The dialer works, enabling permissions works, and updating through the Play Store works.
I'm not sure if it's the intent of this module, but it might make more sense to have the Google Dialer installed as a user app rather than a system app, because it seems that it might work universally. It would be interesting to get some feedback from other users to see if they have the same issues I did or if I'm the only one. Either way, this is working great, thanks for your help.
You can do so as you have done. But your way does not work on several other Roms. In my case i couldn't even install the apk as user file. Any way glad it works.
I also updated via Playstore, but the updated version was not recognized by Tesla - Unread, neither Nearby works.
Found a newer version, all features working.
"com.google.android.dialer_2.5.11_rc8-20511_minAPI23(nodpi).apk"
It can be downloaded on ApkMirror.
Dialer v5.1.1 is the latest version that works in devices not running 7.1+. (Therefore 7.0 Nougat and below work with Dialer v5.1.x).
23Six said:
Dialer v5.1.1 is the latest version that works in devices not running 7.1+. (Therefore 7.0 Nougat and below work with Dialer v5.1.x).
Click to expand...
Click to collapse
That is correct, but Nearby, Caller ID and TeslaUnread does not recognize this version as default dialer as far as i know.
Thomas_BA said:
That is correct, but Nearby, Caller ID and TeslaUnread does not recognize this version as default dialer as far as i know.
Click to expand...
Click to collapse
No issues for me, it's all working fine.
What Rom are you running, installed as user app, with or without the framework. And Tesla unread works?
Hm, what Rom are you running. Installed as user app, with or without framework and permission file? Tesla unread recognizes the dialer as default dialer?
I have 5.1.13122 and the above three features don't work.
Thomas_BA said:
Hm, what Rom are you running. Installed as user app, with or without framework and permission file? Tesla unread recognizes the dialer as default dialer?
I have 5.1.13122 and the above three features don't work.
Click to expand...
Click to collapse
I had 2.5 rc8 already installed as a user app. But I have Magisk module 'App Systemizer' which converted to a system app.
I used your zip file (removed the apk so just the framework). After flashing I still had 2.5 rc8 as system app. Then I sideloaded 5.1 apk and it works the same (system app).
Nearby places work, all permissions granted, set as my default dialer successfully. Tesla seems not to be working -- just tested.
OnePlus 3T stock ROM (Android 7.0) with stock dialer disabled.
@Thomas_BA work like charm on Honur 5x stock. But another thing. I have a dual sim device. Though from menu I have selected that smart dialling is activated that means stock dialer is asking me for which sim I need to choose for calling but google dialer is not working as it intended to work like it work in lineage OS
methuselah said:
@Thomas_BA my twrp is giving me error 1 while I am trying to flash this on HONOR 5x stock ROM. I tried to delete apk from the zip but nose.
edit: i am with supersu. Can you tell me any way to install this with supersu ?
Click to expand...
Click to collapse
For troubleshooting it's a lot more useful providing the recovery log from the failed flash.
worked.
methuselah said:
worked.
Click to expand...
Click to collapse
What was the issue (for future reference)?
I managed to get that log before you removed it... Looked like the problem was a corrupted zip, but my curiosity is crying out for a resolution.
Didgeridoohan said:
What was the issue (for future reference)?
I managed to get that log before you removed it... Looked like the problem was a corrupted zip, but my curiosity is crying out for a resolution.
Click to expand...
Click to collapse
i was flashing the zip right from twrp . I didn't see the available option from magisk to load module
methuselah said:
i was flashing the zip right from twrp . I didn't see the available option from magisk to load module
Click to expand...
Click to collapse
One last OT post, then I'll drop this. My curiosity is still unsatisfied...
That points the finger at your TWRP. If you can flash the zip through the manager it should be able to flash in TWRP. There was a lot of other errors in the recovery log as well, not only for the zip flash. You might have issues with your recovery...
Over and out.
Didgeridoohan said:
One last OT post, then I'll drop this. My curiosity is still unsatisfied...
That points the finger at your TWRP. If you can flash the zip through the manager it should be able to flash in TWRP. There was a lot of other errors in the recovery log as well, not only for the zip flash. You might have issues with your recovery...
Over and out.
Click to expand...
Click to collapse
well maybe yeah. the recovery I was using was meant as a test recovery. But I am right now won't be able to check whether the stable recovery was working properly with the zip. But this is the first zip I saw that gave me some sort of error. So there might be something inside the zip that makes it only work from the magisk itself. Huawei stock is crap. Maybe it works this way in magic. A guess with my limited knowldge. : confused:
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
@Thomas_BA @Didgeridoohan is there is any other way that can be used to make this flashable zip for google contacts app for the marshmallow ? like phone app ?
Is there a way to get the built in voice mail function to work? It works on lineage os roms but cant seem to get it to work through the module. Thanks.
samsung note 8 system applications can not be updated to the new version from the apk file (the original manufacturer file from apkmirror) the system shows the application not installed without any information about the error. It does not install any updates from Samsung Apps. My applications - empty, does not detect anything. Same Google Play. For example, the camera version 7.62.2 in the phone, and the new one is 8.50, you can not update it, so do the other system.
How to add News Republic to Bixby screen.
Note8 SM-N950FXXU5CRHA Android 8.0 Samsung Exp. 9.0. No root. Fully Stock from fabric.
No idea what you are trying to say honestly. Are you unable to update phone ?
when i run apk file and want update installed application form apk file, android show me shows the application not installed without any information about the error. When i check updates in Samsung Apps /My Apps/Update- it does not install any apps- white screen.
Cannot update any system app from file allways see :this apk not installed. I change any settings and any privilege to app and nothing.
Odin modd and reinstalled system not helped me.
Sorry for previous message is haotic.
2.how add News Republic to bixby screen to reading news.
sandeepkumar0153 said:
No idea what you are trying to say honestly. Are you unable to update phone ?
Click to expand...
Click to collapse
He meant, some of the Samsung system apps doesn't show updates available in the Galaxy Apps store or Play Store. There are updates to certain apps, like the camera and dialer on APK Mirror, but when you download them and try to install them, it gives an error and says the app wasn't installed. That is his issue, that he can't update some of his apps.
HTCCM11/2 said:
when i run apk file and want update installed application form apk file, android show me shows the application not installed without any information about the error. When i check updates in Samsung Apps /My Apps/Update- it does not install any apps- white screen.
Cannot update any system app from file allways see :this apk not installed. I change any settings and any privilege to app and nothing.
Odin modd and reinstalled system not helped me.
Sorry for previous message is haotic.
2.how add News Republic to bixby screen to reading news.
Click to expand...
Click to collapse
Some of the apps you're trying to update, like the camera, can't be updated by side-loading or downloading an APK, because it's a system app. You can't update system apps. In the case of the camera, I wouldn't want to update that anyway, because even though it's a higher version, it's not necessarily meant for the Galaxy Note 8, because the "newer" versions remove the ability to use the optical 2x zoom, which I'm sure isn't supposed to happen. I think those are updated camera APKs for different models, maybe like the A- or J-series.
What you could do, if you are rooted, is to just replace the system APKs with the updated ones you downloaded, but I wouldn't recommend that, because sometimes the updates to system apps might also depend on updates to other library files which you don't get with the APK or can't download and then might cause some problems and issues.
As far as your question about Bixy and News Republic: I have no idea. I don't use Bixby, so I don't even know how it works.
HTCCM11/2 said:
when i run apk file and want update installed application form apk file, android show me shows the application not installed without any information about the error. When i check updates in Samsung Apps /My Apps/Update- it does not install any apps- white screen.
Cannot update any system app from file allways see :this apk not installed. I change any settings and any privilege to app and nothing.
Odin modd and reinstalled system not helped me.
Sorry for previous message is haotic.
2.how add News Republic to bixby screen to reading news.
Click to expand...
Click to collapse
For the 2nd question, have you tried opening Bixby, go to Settings, then go to Cards, then ensure news republic is toggled on (assuming it's installed on your phone in the first place)?
no is not working that, i not see this app in screen.
HTCCM11/2 said:
no is not working that, i not see this app in screen.
Click to expand...
Click to collapse
Hmm if you have the app installed and it doesnt show up there in Bixby, then maybe that app is not compatible with Bixby yet?