Develop Bugs

[Q] Keyboard Keeps Resetting To Samsung 3

Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.

dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I think if you go to the buglist at swiftkey.net you'll find you aren't alone. I'm using the Swiftkey Flow beta and this problem hasn't occurred...yet. You can turn of the Flow feature and it becomes a regular Swiftkey keyboard.

I use Smart Keyboard Pro off of the market and the same thing keeps happening to me. By that I mean I don't use swype and my settings keeps rolling back to the regular keyboard.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I've found that these problems can sometimes can be fixed by uninstalling and reinstalling the keyboard.

I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

jeffdaman said:
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Could you describe how this is happening? Does it switch keyboards after you use a certain app, or does it just switch at random times? One thing you could try is to disable all other keyboards under applications. This way, the phone has to keep using your keyboard.

Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)

It happens every time I restart and then it would happen randomly while using the phone. I thing Task Manager by Rythm Soft was killing Smart Keyboard but I got it on the ignore list now; and so far it seems limited to the restart. It's not possible to disable Swype or the Samsung Keyboard. They are greyed out on the list.
To the O.P. you should check any task managers to be sure Swype isn't being killed.

MobileNick said:
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
Click to expand...
Click to collapse
Same thing is happening to me. Always after a restart it falls back to the Samsung Keyboard.

If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium

brorex said:
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Anyone try this, and what does it default to if you do remove the Samsung Keyboard? I have several inputs, WiiMote, PS3, etc. If I have to keep changing the default back to Swiftkey, then this option would get annoying.

Known Bug with Work-Around
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!

Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
Might wait for Google or Swiftkey to fix the bug. If I restore without the data, then I lose all the words Swiftkey has learned.

This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??

MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Same. Reboot causes the problem. Not a huge issue, but odd.

cfn87 said:
Same. Reboot causes the problem. Not a huge issue, but odd.
Click to expand...
Click to collapse
It's a change in the way Jellybean handles how Google Play apps are loaded during boot process, since they happen after the keyboard gets loaded, it reverts to default.

Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers

xBeerdroiDx said:
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers
Click to expand...
Click to collapse
Where would this location be?

dratsablive said:
Where would this location be?
Click to expand...
Click to collapse
via a google search

MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Sorry if this was already covered...but I read a post at the Swiftkey site that the issue is with Paid apps on JB. Not all paid apps of course...but some paid apps like Swiftkey install to this special storage location that is not available soon enough during the boot process.
The 4.x Swiftkey beta was not a paid app so it worked...now that the beta is released it is a paid app and the Swiftkey 4.x release in Google Play has the issue again on JB just like 3.x did.

Unfortunately S Health has stopped working

Anyone else having this issue? Every time I open it, I get a blank screen and then the error message. Any solutions?
Sent from my SGH-M919 using xda app-developers app

go into app manager and clear data and wipe cache?? try that

Tried it, to no avail. After performing around factory reset & reinstalling everything, I finally found the culprit. It was the multi window mod which lets you use all the apps in multi window.
All problems started after its install. Even the phone started to lag and give random force closes. Got rid of the mod and all is back to normal again.
Sent from my SGH-M919 using xda app-developers app

Questions go in Q&A
Thread moved

umair239 said:
Tried it, to no avail. After performing around factory reset & reinstalling everything, I finally found the culprit. It was the multi window mod which lets you use all the apps in multi window.
All problems started after its install. Even the phone started to lag and give random force closes. Got rid of the mod and all is back to normal again.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
how did you got rid of the mod? because i uninstalled the multiwindow manager app, but i don't know how to remove the mod and my S health isn't working.. i have the gs4 octa core

ezezl75 said:
how did you got rid of the mod? because i uninstalled the multiwindow manager app, but i don't know how to remove the mod and my S health isn't working.. i have the gs4 octa core
Click to expand...
Click to collapse
I removed shealth from the enabled packages in multi window manager, saved, rebooted and it started working for me.

ramhen said:
I removed shealth from the enabled packages in multi window manager, saved, rebooted and it started working for me.
Click to expand...
Click to collapse
Thank you. But I contacted to the developer of app and he solved the problem to me. Thanks anyway

ezezl75 said:
Thank you. But I contacted to the developer of app and he solved the problem to me. Thanks anyway
Click to expand...
Click to collapse
What did the developer tell you the fix was?

ezezl75 said:
Thank you. But I contacted to the developer of app and he solved the problem to me. Thanks anyway
Click to expand...
Click to collapse
Hi! I have the same problem on my GS4. Could you plz tell us what is the solution that the developer told you? Thanks~

Fixed S Health; Reset Flash Binary? Maybe????
I seriously don't know how I did this I was just tinkering around trying to get this to work and I got it!!!!!! I actually hope that this can help others I'm gonna try to walk you through what I did. You will need Titanium backup PRO and a be on your original ROM as I have the ME7 build and have not flashed any ROMs yet. Oh speaking of that while doing these steps I think I reset the flash binary because the "custom" unlock screen is gone now to. I still can't get the stock music app working though. This issue actually started when I transferred a full TB file to a brand new phone. When I first changed it I changed the Android ID to a new one, I think this is where the issue starts. I had apps from anothers ROM (Phone) on a new ROM, and my Android ID was changed.
So here's what I did. I'll start where i'm sure I know it started working and that's after I was able to get to the deeper features of TB.
1. Menu>Your Device...(Make sure you have your original bakcup that has the settings you transferred in, if not your probably out of luck)>scroll down the Your device section>Manage Android ID>
I attempted to restore my ID to the backup and it told me that was the ID>
I figured what the heck and changed the ID to a new one and rebooted...after rebooting I went back into TB....it gave me the warning for having a new ID I told it to keep the old one (can't quite remember the wording but it's the one on the right...last time I told it to keep the new one.)
I then cleared dalvik cache, the beauty of TBP without a custom ROM
Menu>>storage>>clean up dalvik cache.
Once again I removed the S Health App, reinstalled and rebooted. When booting I noticed the Samsung "custom" unlock screen was gone as well.
I tapped that little s health button and after an agonizing wait, it has RETURNED!!!!! UPDATING!!! YEAH!!!!
Now I can't guarantee these steps will work for you but if it does that would be awesome. Has anyone figured out an easy way like that to reset the flash binary?
---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------
Samsung custom screen back again. lol

umair239 said:
Anyone else having this issue? Every time I open it, I get a blank screen and then the error message. Any solutions?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
For Everbody Who has this problem
Go To Multi Window Manager (MW Manager)
Go to settings ( Gear Button on the top side op your screen on the right)
go to BlackList
than seek for the S Health App en Tick the box on the right side of the S Healt App
Greeting Steves1990

Steves1990 said:
For Everbody Who has this problem
Go To Multi Window Manager (MW Manager)
Go to settings ( Gear Button on the top side op your screen on the right)
go to BlackList
than seek for the S Health App en Tick the box on the right side of the S Healt App
Greeting Steves1990
Click to expand...
Click to collapse
So glad I tried this first before going down the other complicated routes. This solved my problem immediately...thanks for sharing.
Note 3 -- Tapatalk

Steves1990 said:
For Everbody Who has this problem
Go To Multi Window Manager (MW Manager)
Go to settings ( Gear Button on the top side op your screen on the right)
go to BlackList
than seek for the S Health App en Tick the box on the right side of the S Healt App
Greeting Steves1990
Click to expand...
Click to collapse
Yes!! This worked for me. Galaxy note 3. Thanks!

Steves1990 said:
For Everbody Who has this problem
Go To Multi Window Manager (MW Manager)
Go to settings ( Gear Button on the top side op your screen on the right)
go to BlackList
than seek for the S Health App en Tick the box on the right side of the S Healt App
Greeting Steves1990
Click to expand...
Click to collapse
This also worked for me att note 3 rooted stock.

S health
I had the same issue on my Note 4, i notice that if you uninstall the last update to Shealth, it works under art.

No Google Now after 4.3

I have been running 4.1.2 for a long time and google now always worked fine. When the 4.4 home screen apks came out I installed them and was really enjoying having google now as a homescreen page. Last week I installed the ditto note rom and ever since then I can not get google now to work, I have tried everything that I have found when searching (Why doesn't xda search support speech marks though?) Last night I did a super wipe and installed pheonix rom but still the problem persists. What am I doing wrong?
Since installing DN3 I have tried:
changing language to english us - still no google now
changing to english uk and downloading offline data - still no google now
clearing google search app data - still no google now
upgrading google search to lastest version - still no google now
downgrading to dn3 default version - - still no google now
installing 4.4 apks - still no google now
super wipe and install phoenix rom - still no google now (shouldn't superwipe kill any possibility of it being something on phone that did it?)
languages again - still no google now
installing launcher enabler - still no google now
So is it one of the following?
Google decided that an English speaker in China doesn't get google now anymore? On the exact day I upgraded my rom?
I'm being punished for installing the 4.4 apks early?
These two roms don't support google now?
superwipe isn't super?
Google now was bad for me and the universe is staging an intervention?
Please help

Im living in China too and have this problem on my nexus 4

AntiNSA said:
Im living in China too and have this problem on my nexus 4
Click to expand...
Click to collapse
Hmmm.. looks like it must be something similar to how location reporting got disabled for many countries.. For a company that talks so much about transparency I sure wish they would explain why they are disabling these features that used to work fine simply because I happen to be in another country. Is it an international law thing?

joshofbass said:
Hmmm.. looks like it must be something similar to how location reporting got disabled for many countries.. For a company that talks so much about transparency I sure wish they would explain why they are disabling these features that used to work fine simply because I happen to be in another country. Is it an international law thing?
Click to expand...
Click to collapse
It makes me really uupset to. I know that google now/voice search requires active location settings... I think the Chinese government demanded that googole disable location tracking for internal security (closed market/monopoly),,,,
I dont want to see maps blocked here s I guess it is a balancing act. I hate to see the other features of googe blocked....

From what I can tell it works perfectly fine if you set it up from an earlier version of google search.. For me that means probably a reflash without install search then finding an earlier apk version to initialize it.. Will report back on progress..

joshofbass said:
From what I can tell it works perfectly fine if you set it up from an earlier version of google search.. For me that means probably a reflash without install search then finding an earlier apk version to initialize it.. Will report back on progress..
Click to expand...
Click to collapse
Success!
What worked for me was:
I reflashed the rom I was using but chose not to install google search as a system app. You could just try to remove the app with Titanium, it should have the same effect.
On first boot I didn't sign in to google at all. Instead I first installed the search2.6 apk from the below link.
Then I opened google play and signed in and quickly went to turn off auto update.
Then I opened google search and it asked me to opt-in to google now.
Once it was all running I went back to google play and let it update and also installed the launcher enabler app.
Hope this helps someone.
http://forum.xda-developers.com/showpost.php?p=47492354&postcount=106

Great! Let me know if you can make it work also let me know if the Google now, voice search works with the new KitKat and old search apk
Sent from my Nexus 4 using xda app-developers app

working just fine for me
I am using pohnix rom v15 with 4.3 and google now is workin!!

AntiNSA said:
Great! Let me know if you can make it work also let me know if the Google now, voice search works with the new KitKat and old search apk
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Working 100% now. I'm pretty sure it's a location at time of setup issue. Good luck trying it on your nexus4.

Can't touch/access Google Now Settings?

Hey,
I can't access Google Now settings. I can go into the settings menu, but whenever I tap on any of the settings it doesn't respond.

captainreynolds said:
Hey,
I can't access Google Now settings. I can go into the settings menu, but whenever I tap on any of the settings it doesn't respond.
Click to expand...
Click to collapse
try swiping up on the home button, scroll to the bottom and press the 3 dots. hope this helps because I dont know from where are you teying to access the setting.

mr.dj26 said:
try swiping up on the home button, scroll to the bottom and press the 3 dots. hope this helps because I dont know from where are you teying to access the setting.
Click to expand...
Click to collapse
Yeah, I am accessing the settings that way. Any ideas? I've tried wiping data in Titanium Backup to no avail.

captainreynolds said:
Yeah, I am accessing the settings that way. Any ideas? I've tried wiping data in Titanium Backup to no avail.
Click to expand...
Click to collapse
go to play store, type google search, uninstall, intall again.
---------- Post added at 01:23 AM ---------- Previous post was at 01:19 AM ----------
try this.
go to settings (normal setting)
choose accounts and sync
google
search
this should show up the Google now setting.

mr.dj26 said:
go to play store, type google search, uninstall, intall again.
---------- Post added at 01:23 AM ---------- Previous post was at 01:19 AM ----------
try this.
go to settings (normal setting)
choose accounts and sync
google
search
this should show up the Google now setting.
Click to expand...
Click to collapse
Unfortunately neither of those things work. going to settings then accounts and sync and Google just opens up the normal Google now settings.
Also uninstalling Google now has royally screwed up my phone so I would not recommend anyone else do this.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

mr.dj26 said:
try swiping up on the home button, scroll to the bottom and press the 3 dots. hope this helps because I dont know from where are you teying to access the setting.
Click to expand...
Click to collapse
I can't quite figure it out either. Stock rom, when I swipe up from the soft home key, I go to google now. How do I change or disable this?

Xdpker06 said:
I can't quite figure it out either. Stock rom, when I swipe up from the soft home key, I go to google now. How do I change or disable this?
Click to expand...
Click to collapse
both of you, install a custom rom

I need to, just lazy because I have everything set up on stock.
Sent from my HTC One_M8 using xda app-developers app

Xdpker06 said:
I need to, just lazy because I have everything set up on stock.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
thats why I installed a custom rom as soon as I got the phone out of the box
backup with htc cloud, shouldn't take long to recover everything back to normal

I really don't want to install a custom rom. They are too unstable for me and the stock rom has great battery life and is well designed. Xposed modules can allow me to make any changes necessary without the bugs you get with custom roms.
Bumping this again. I have uninstalled, wiped data of the app, and done everything I can think of. Also updated to the latest one and no success. I have no apps modifying google now or any touch interfaces of any kind. Any idea for a fix?

So what are you actually wanting to change? What Google Now cards are shown? If so, you open Google Now and then click the magic wand you can then add/remove which cards are shown

EddyOS said:
So what are you actually wanting to change? What Google Now cards are shown? If so, you open Google Now and then click the magic wand you can then add/remove which cards are shown
Click to expand...
Click to collapse
Imho he means the settings screen where you can access e.g. the Offline Voice Packs...

A couple of us have been trying to figure this out forever. Custom ROM won't help. Something else is breaking it. In my case, I think it was when I installed a clear themed gnow from tbo. The only way I ever got it back was when I accidentally wiped my internal storage. I broke it again with clear gnow. Restoring a nand doesn't help. Clean flash doesn't help. This leads me to believe something is being left in internal SD that's messing with it. Another of us has not installed anything themed and still it's happening to him. Very elusive.

Here's a workaround that was just found. I'm pasting it from the tho thread I just posted it in. Op, maybe add to your op for people who stumble upon this thread with the same problem.
Pasted: Just want to keep you abreast of my discoveries. My problem, and a friends, of settings not working clearly start when I install clear gnow however I have found a couple people who have this problem and did not theme anything. Someone found a work around. This may or may not shed some more light. If you install gnow launcher you can access the settings from there. If you switch back to sense it stays until reboot but then if you need to adjust you can switch back to g launcher to do it. I'm just keeping gnow launcher installed for that purpose.
Sent from my 831C using XDA Free mobile app
Sent from my 831C using XDA Free mobile app

Phone app won't wake screen!!!!

This is driving me crazy!!!
When my phone is off sitting on a table and it rings, the screen does not come on. Just sound. I thought it was the theme, so I removed it from the dialer app and that didnt help. I removed the update in the Playstore and the screen comes on again when it rings. I removed auto update for the app, but what could be the reason the updated app isn't working for me?

Stock dialer or a custom app from app store?
Sent from my SM-N950U using Tapatalk

EVOme said:
This is driving me crazy!!!
When my phone is off sitting on a table and it rings, the screen does not come on. Just sound. I thought it was the theme, so I removed it from the dialer app and that didnt help. I removed the update in the Playstore and the screen comes on again when it rings. I removed auto update for the app, but what could be the reason the updated app isn't working for me?
Click to expand...
Click to collapse
Your issue has been reported by several others as well. They are doing the same thing you are to make it work. Would recommend you log complaint on play store under the phone app and see what happens. I truly think Google does this to jack with the themeers!

amyf27 said:
Stock dialer or a custom app from app store?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Stock, but I can't take it anymore, so I removed the update and installed Simpler dialer. I can't even disable the stock dialer or the screen won't come on. It's just been removed as default at this point.

I just read reviews for the app and tons of people are reporting it. What a joke!!!

EVOme said:
I just read reviews for the app and tons of people are reporting it. What a joke!!!
Click to expand...
Click to collapse
I don't know if this will help or not, but a couple weeks or so ago, the Google phone app was giving me trouble with themeing. It was due to the fact that the theme was actually ahead of the Google update(go figure). So another user figured it out and linked me to the phone app on apk mirror. So I uninstalled the phone app, downloaded the apk mirror version from December 14th, installed it, and it worked great with my theme. What's more is that even after the update from Google, I'm not having the issue that you are, or many others for that matter. Here's the link if you want to give it a go. Can't promise anything, but what the heck :good:
https://www.apkmirror.com/apk/googl...-phone-15-0-178841333-3-android-apk-download/

Badger50 said:
I don't know if this will help or not, but a couple weeks or so ago, the Google phone app was giving me trouble with themeing. It was due to the fact that the theme was actually ahead of the Google update(go figure). So another user figured it out and linked me to the phone app on apk mirror. So I uninstalled the phone app, downloaded the apk mirror version from December 14th, installed it, and it worked great with my theme. What's more is that even after the update from Google, I'm not having the issue that you are, or many others for that matter. Here's the link if you want to give it a go. Can't promise anything, but what the heck :good:
https://www.apkmirror.com/apk/googl...-phone-15-0-178841333-3-android-apk-download/
Click to expand...
Click to collapse
Thanks for that. The dev of the theme I am using replied to me because his theme was not working on the phone app. He told me I needed to install this version
https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-15-0-179075669-release/
I installed it and applied the theme and it worked. Since the latest update, it doesn't. The version you posted is different than the one he did. I'm half tempted to try it, but at this point I have all the updates off the phone app and using a different dialer and it's working.
Also, how are you uninstalling the stock phone app...all I can do is uninstall the updates and disable.?

EVOme said:
Thanks for that. The dev of the theme I am using replied to me because his theme was not working on the phone app. He told me I needed to install this version
https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-15-0-179075669-release/
I installed it and applied the theme and it worked. Since the latest update, it doesn't. The version you posted is different than the one he did. I'm half tempted to try it, but at this point I have all the updates off the phone app and using a different dialer and it's working.
Also, how are you uninstalling the stock phone app...all I can do is uninstall the updates and disable.?
Click to expand...
Click to collapse
I uninstalled it using my root explorer. I just delete the apk, reboot, and gone. Have to be rooted though. If nothing else, just install the apk, then if you wind up with 2 phone apps, just disable or freeze the bad one. Or, just do what your currently doing. The updates aren't that big a deal anyways :good:

Badger50 said:
I uninstalled it using my root explorer. I just delete the apk, reboot, and gone. Have to be rooted though. If nothing else, just install the apk, then if you wind up with 2 phone apps, just disable or freeze the bad one. Or, just do what your currently doing. The updates aren't that big a deal anyways :good:
Click to expand...
Click to collapse
Figured it was a root thing. I can't root my phone due to work email MDM detecting it and harassing me. Going to try your suggestion. Much appreciated

EVOme said:
Figured it was a root thing. I can't root my phone due to work email MDM detecting it and harassing me. Going to try your suggestion. Much appreciated
Click to expand...
Click to collapse
Bummer man. Best of luck to ya :good:

Badger50 said:
Bummer man. Best of luck to ya :good:
Click to expand...
Click to collapse
Just tried it. Once I apply theme, phone won't light up. Deleted 3rd party dialer, removed theme from dialer you provided. Now I'm using the Google dialer you gave me in stock white blinding form. A bit pissed...

I have the same issue. In my case I have a gear s3, and if I disconnect the bluetooth, when the call is coming the screen turn up normally, but if the gear is connected, the screen stays black..Additional, when you take a call or do a call, the sound automatically is route to the bluetooth device, I have to habilitate the sound in the phone manually. I think it was with the January update or the phone app last update, because other people have the same issue in their android devices. The solution for now is go to Play Store, search Phone app for Google, uninstall the updates, then go to settings in the phone - Apps - Phone, and clear the cache and data, force stop of the app. The phone app come back to another version (12.1...) which doesn't have this issue, after that the calls working normally. I hope for a fix from Google...