Hello,
I heard that the new update from t mobile would include a new GTalk with videos along with some other new apps.
I installed the one posted in the dev section and the only change I notice is a new music app. Where is GTalk? Is there anything else that was supposed to be added? Is the updated posted here incomplete compared to the one officially from t mobile?
Thanks.
saltmine said:
Hello,
I heard that the new update from t mobile would include a new GTalk with videos along with some other new apps.
I installed the one posted in the dev section and the only change I notice is a new music app. Where is GTalk? Is there anything else that was supposed to be added? Is the updated posted here incomplete compared to the one officially from t mobile?
Thanks.
Click to expand...
Click to collapse
This is the reason I am waiting for the FOTA/OTA and I just want a clean install.......but the longer it takes the more likely I WILL USE ODIN. I hate this rollout....it sucks.
Google talk app is included in the update. The application talk is google talk the video is built in the chat app itself.
aleks_ said:
This is the reason I am waiting for the FOTA/OTA and I just want a clean install.......but the longer it takes the more likely I WILL USE ODIN. I hate this rollout....it sucks.
Click to expand...
Click to collapse
Clean install? Doesnt get any cleaner and safer than odin. OTA's suck.
Killbynature said:
Google talk app is included in the update. The application talk is google talk the video is built in the chat app itself.
Click to expand...
Click to collapse
The google talk seems to be unchanged by the update. How do I check if it was changed?
It says talk version 1.3 ... Do I have the old one or the new one?
Anyone know if any other apps were changed?
How's everyone's take of the battery on this new radiO?
The video is in there. there should be a camcorder symbol next to your name. I'm in the ROM now.
Sent from my SGH-T989 using xda premium
I haven't seen the update in the market nor the firmware method. How do we go about "updating".
I just bought this phone, but I am still thinking about whether to root it at this point. I mean, I would love to because of all this BS bloatware, but I kinda want to get to know the phone first.
just use the available update and use odin. it'll keep your apps that doesnt need root, intact. i havent tried rooting mine to see if the other apps that requires root will pop back on. and yes, i wiped mine clean and started fresh.
so my point is, if you want a clean install, still just use the odin version and factory reset it through the settings. it'll be just as fresh as one straight from FOTA/OTA
hth
EDIT: oh btw, i did root mine, after resetting it back to factory defaults.
King_Paladin said:
so my point is, if you want a clean install, still just use the odin version and factory reset it through the settings. it'll be just as fresh as one straight from FOTA/OTA
Click to expand...
Click to collapse
+1
I strongly recommend updating through Odin, then Factory Reset after.
Works perfectly, this ROM is perfect for this BEAST of a phone
Related
how do I update apps like Amazon, photobucket, etc.? I can't update them from the market since I didn't download the from there in the first place.
download it from the market. Just try it. Download it, dispite it not shown in the market as an update. Once installed the phone and your market will see it as an update.
Sent from my T-Mobile G2 using XDA App
ddgarcia05 said:
download it from the market. Just try it. Download it, dispite it not shown in the market as an update. Once installed the phone and your market will see it as an update.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
yep
First time I logged into the market, it autoupdated all the junk. Goggles and visual voicemail won't update but that's it.
Yeah, I didn't even find "Visual Voicemail" in the marketplace anymore.
I'm pretty sure that T-Mobile might have pulled it from the market entirely.
Anyway, I can't seem to update Google Goggles either. I've tried several times, but it never seems to actually update and install the latest version.
Would it be safe to use Titanium Backup to remove that system application? Or is that not even possible, considering I've read that people have tried to remove the "bloatware" but it just seems to reappear after a reboot.
Any insights?
Reignzone said:
Yeah, I didn't even find "Visual Voicemail" in the marketplace anymore.
I'm pretty sure that T-Mobile might have pulled it from the market entirely.
Anyway, I can't seem to update Google Goggles either. I've tried several times, but it never seems to actually update and install the latest version.
Would it be safe to use Titanium Backup to remove that system application? Or is that not even possible, considering I've read that people have tried to remove the "bloatware" but it just seems to reappear after a reboot.
Any insights?
Click to expand...
Click to collapse
Damn, no more HD2 huh?
Yeah you can remove the bloatware from your device. Well, disable not remove. Read on http://forum.xda-developers.com/showthread.php?t=809231
Ha.
No way, Jose!
I still have my HD2, it's just collecting dust on my computer desk right now.
I thought about using it as a fly swatter, but that seemed too dramatic!
KIDDING!
But yeah, that thing is legendary, so I couldn't just be rid of it.
And thanks for pointing me in the right direction man, good lookin' out!
If you don't want to disable the app which is very easy to do over terminal emulator, try freezing the app with titanium backup. That way you can see how your phone will work with it disabled. For example if you freeze/disable the stock messenger app no messaging app will work after that until you unfreeze/enable the stock one. Same thing with youtube. If you freeze the app and download the newer one off the market it wont work.
Some 3rd party app depend on the stock app to be functional. Let me know if you need help disabling an app. I'll make a video. I <3 my new camera. I traded a gun for it.
I can't seem to update Goggles...
I've disabled the application, then tried to update it from the marketplace, and still nothing manages to install.
I have successfully updated every other system application through the marketplace, with the exception of Goggles.
How can this application be updated properly?
Have you tried to enable it then update?
Sent from my T-Mobile G2 using XDA App
ddgarcia05 said:
Have you tried to enable it then update?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yeah, of course.
But from what I've been told by a few other users... it's a bug in the ROM that doesn't allow certain handsets to update that application.
I mean, unless you have been able it?
Please go to POST 56 for updated information. I will update the OP over the weekend. Thanks!
As many of you already know, with our recent official Jelly Bean release came a new, updated flash counter. With ICS we were able to either just root via the root66 method and not trip the counter, or we could just use Chainfire's Triangle Away app to reset it. This is no longer the case. Now, with JB, unless our firmware meets a very strict set of conditions, it will trip the counter every time you reboot the device. If you simply just flash the root66 firmware, and do nothing else beyond that, you will not raise your count. But then, whats the point of rooting???
DON'T PANIC!
We can still zero it out for Warranty returns! The biggest issues arise when you want to utilize certain apps and/or services such as All Share Cast, Media Hub and other Samsung apps. For example, if you have purchased the $100 equipment, the All Share Cast Hub, it will not work! Additionally, DRM protected content may not play anymore. (Probably just applies to DRM protected media you got from Samsung, but this needs verification). For example, if you got to download the Avengers a couple of months ago, it will not play, even though it is perfectly legal to do so!
So are we able to get around this? Yes and No, for the moment. There are at least 2 separate detections going on. One is done post-boot, using the SysScope app. If you remove this from /system/app/ you will be able to install a custom recovery, and probably also a kernel and another modem without tripping the counter! I have yet to see any negative side effects from removing this app, so until I find more info proving otherwise, I suggest backing it up and deleting it. Hopefully Chainfire will decide to update Triangle Away to counter the updated detection. He may not though. Please read what he has to say about it here.
This does not solve the whole problem though. There is still another method Samsung coded in to detect if your system has been modified. I am not sure yet what is responsible fot this. But if you were to simply deodex your rom, it will begin tripping the counter at boot again! (It may not be the deodexing that is trigging it though, I believe it is also scanning for any processes that are running with root privledges that should not be there, and it may also have to do with busybox). Either way, if you are running pretty much any kind of custom rom, it will retrip the counter at bootup. This method is different in that it happens during boot, not after, and it does not look at recovery, and probably not at kernel or modem either. It appears to look specifically at the system partition for anything not stock. I am trying to narrow this down.
Because the other 2nd part seems to happen during bootup, I think that Chainfire's paid version may be able to help here. If you purchase it on the Play Store, it will have enabled the ability to Auto run at boot. Since SysScope is now removed, I dont think any detections are running post-boot anymore, meaning Auto run from Triangle Away should work. I do not have the paid version to test with right now. But I will try and test this soon.
I am fairly certain that the rest of the detection process is running either from the kernel, or from a completely separate partition. It is going to require quite a few flashes and test to narrow it down for sure. So if you guys will report your experiences with it, particularly on different kernels, I would be greatly appreciative.
As I find and/or remember more about this, I will update it here. If anyone has any other information about this, please do post it here! Any help, tips, info, etc that you can provide can be very helpful!
I hope this all made sense to you guys! I will go back and clarify some stuff a little later, but Ive got a 6 year old kid going stir crazy waiting on me to be done with this! I wanted to go ahead and get something up though to get the conversation started! I will also post some links to some information later on.
In the meantime, you can Odin back to ICS build UVALJ4, and then flash your roms from there...yes even the JB ones! I hate saying that after suggesting to Odin flash the JB update, but if you have anything not working because of this, it may be your best option temporarily.
Otherwise, delete SysScope from /system/app! And keep Triangle Away handy!
I will continue doing a lot of testing and trying to investigate this problem. But I do appreciate any help that you guys can give!
Hopefully, with a little luck we can figure this out! :highfive:
I think that pretty much covers it...
I know that if you triangle away, and reboot to download mode, the counter's zero... if you boot into recovery and then boot into download mode the counter's still zero...
It gets triggered when you boot into the actual rom... I wonder if you odin to JB... then actually flash down to an ICS rom, does the counter get reset on boot?
scifan said:
I think that pretty much covers it...
I know that if you triangle away, and reboot to download mode, the counter's zero... if you boot into recovery and then boot into download mode the counter's still zero...
It gets triggered when you boot into the actual rom... I wonder if you odin to JB... then actually flash down to an ICS rom, does the counter get reset on boot?
Click to expand...
Click to collapse
That's SysScope running after booting up. Flashing an ics rom over a fully updated JB will most likely also trip the counter due to the 2nd part of the device check which runs during boot. Worth trying though.
Sent from my SGH-T999 using xda app-developers app
Also need to find out if its the deodexing that triggers it, or something like busybox.
Sent from my SGH-T999 using xda app-developers app
Good info. And nice write up so your saying if we odin root66 ics we are ok to say flash gs3r7.zip to jb and the new custom rom detection wont be present?
Sent from my SGH-T999 using xda app-developers app
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Okay, here was the progenitor post, that may give clues if the old (ICS) way no longer works:
http://forum.xda-developers.com/showpost.php?p=28953690&postcount=67
and the resultant manual method, which I verified worked on TMO (ICS):
http://forum.xda-developers.com/showthread.php?t=1781471
1Shotwonder said:
Good info. And nice write up so your saying if we odin root66 ics we are ok to say flash gs3r7.zip to jb and the new custom rom detection wont be present?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Yes that is correct. I cannot guarantee you wont have any other bugs. Doing it this way you are essentially running half ics half jb. If you have no need of samsung services like media hub or all share cast, id go full jb. Otherwise id go with the ics UVALJ4 firmware and a jb rom.
wideasleep1 said:
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Click to expand...
Click to collapse
That would be great! Thanks!
Sent from my SGH-T999 using xda app-developers app
Good job Doc... :thumbup::thumbup::thumbup:
Sent from my SGH-T999 using Tapatalk 2
Doc, I'd be more than happy to help out with this. Just shoot me a PM about where you are heading and I can see what I can do. I'm not adverse to getting in deep, so that is a non-issue.
My initial thoughts are to take a pretty simple approach and, for lack of a better few words, do a side-by-side of the new JB and the recent leaks and see what is different. Obviously it is a bit harder than than but we could breakdown the /system/apps, then move on the each partition scheme and see what the differences are and why they are different. Then start crossing off things like apps, 2boot check, something buried in on of the other partitions, ....
Really Samsung? God this crap is really starting to piss me off. Love how manufacturers don't want be enjoying my device.
On a more positive note, can't Samsung deny claims for just the CPU?
Sent from my SGH-T999 using Tapatalk 2
only thing that bothers me is the avengers movie not playing in any of the players on the GS3R7 rom. ( I have tried to reset the counter and still does not play the movie... any ideas? It does work on stock jb root66 though). Other than that I dont use any other samsung apps. The other issue I have come across is with Root Explorer when trying to modify the build.prop for GW I can edit the build.prop but it will not save the changes I believe this to be an issue with the sdcard now being sdcard0 but I am not 100% any one have a way around this or know the fix?
wideasleep1 said:
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Okay, here was the progenitor post, that may give clues if the old (ICS) way no longer works:
http://forum.xda-developers.com/showpost.php?p=28953690&postcount=67
and the resultant manual method, which I verified worked on TMO (ICS):
http://forum.xda-developers.com/showthread.php?t=1781471
Click to expand...
Click to collapse
Thanks for looking those back up. Ill be checking them out later on today.
Woodrube said:
Doc, I'd be more than happy to help out with this. Just shoot me a PM about where you are heading and I can see what I can do. I'm not adverse to getting in deep, so that is a non-issue.
My initial thoughts are to take a pretty simple approach and, for lack of a better few words, do a side-by-side of the new JB and the recent leaks and see what is different. Obviously it is a bit harder than than but we could breakdown the /system/apps, then move on the each partition scheme and see what the differences are and why they are different. Then start crossing off things like apps, 2boot check, something buried in on of the other partitions, ....
Click to expand...
Click to collapse
sounds good man! Kinda have a feeling ill be needing help on this one! Ill shoot you a pm later on. Gotta get going for now, but wanted to respond real quick.
1Shotwonder said:
only thing that bothers me is the avengers movie not playing in any of the players on the GS3R7 rom. ( I have tried to reset the counter and still does not play the movie... any ideas? It does work on stock jb root66 though). Other than that I dont use any other samsung apps. The other issue I have come across is with Root Explorer when trying to modify the build.prop for GW I can edit the build.prop but it will not save the changes I believe this to be an issue with the sdcard now being sdcard0 but I am not 100% any one have a way around this or know the fix?
Click to expand...
Click to collapse
Its another thing I've got to figure out. If its just breaking Samsung related/downloaded stuff, or is it screwing with DRM altogether.
As to your other issue, wallets included with jb now so I assumed it wouldn't require a 'fix'. But it sounds more like a superuser problem with root explorer. Download chainfires cwm supersu from his thread and flash it. See if that helps. Not going to be related to this stuff though.
Sent from my SGH-T999 using xda app-developers app
Does reverting back to ics roll back the flash counter? I am really liking JB TW maybe time for a change lol
Sent from my SGH-T999 using xda premium
Unfortunately I doesn't work that way. Would be sweet if it did, then all we'd have to do is roll back and we'd be good. Plus we could figure out the trigger and remedy it.
md1008 said:
Does reverting back to ics roll back the flash counter? I am really liking JB TW maybe time for a change lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If I'm not mistaken, you should be able to revert to ICS then use triangleaway and your counter will stay at 0.
Sent from my SGH-T999 using Tapatalk 2
Woodrube said:
Unfortunately I doesn't work that way. Would be sweet if it did, then all we'd have to do is roll back and we'd be good. Plus we could figure out the trigger and remedy it.
Click to expand...
Click to collapse
Triangle away, boot to recovery, then flash ICS on your phone...
Well my counter is stuck at 1 lol
What exactly trips the counter? I've seen multiple answers for the question but I figured ide ask here since there are so many knowledgeable people here
Sent from my SGH-T999 using xda premium
So ive been reading this and from what i can gather, it seems that samsung (or T-Mobile) placed a new apk file into the system directory (or maybe a lib file?) and that if you root your device, every time you reboot your phone, it will +1 to the flash counter?
Has anyone asked any ATT, Sprint or Verizon users if their flash counter goes up with root after each reboot as well? If it doesnt, we could probably do a system file comparison between the two to isolate the file(s) which are causing the incremental flash counter at boot.
That's what I was saying earlier about comparing official and leak and seeing the differences. Sprint is the only one that has had official so not sure if that would work for us. Think we need to differentiate between Samsung and TMo and see where the "fault" lies.
Woodrube said:
That's what I was saying earlier about comparing official and leak and seeing the differences. Sprint is the only one that has had official so not sure if that would work for us. Think we need to differentiate between Samsung and TMo and see where the "fault" lies.
Click to expand...
Click to collapse
That sounds like a good idea. I'll download one of the leaks and see if anything is obvious. It may also be a new line of code inside an apk or lib file as well. Making things a bit more difficult. As im comparing them i will check the size of each APK as well as if new code is added to them it should increase the size of the compiled apk. And i have my computer set up to show individual bytes of data.
my Google Wallet worked for weeks after the hack but today I try to open the application and it force closed. I tried doing all those steps again from the hack thread but I still can't get it to work. Just want to know if anyone else is having the same problems I am?
Same here. Was working earlier today. Nothing new installed or done to the device either.
Still working for me maybe it was a temporary server malfunction
Sent from my SPH-L900 using xda app-developers app
Anybody have any ideas on what may have changed/happened?
ETA:
Stock deodex LK8 w/ latest Perseus.
I know it was working in the AM (1/5), but then I saw the OP's post and decided to check again, and... voila... in el crappero with FC's.
So far: uninstalled, wiped, manual add process which worked for me first time. Still FC's.
I say check your build prop and make sure it didn't get changed by flashing a mod etc
Sent from my SPH-L900 using Tapatalk 2
still force closing for me... what could they have changed
stu5797 said:
still force closing for me... what could they have changed
Click to expand...
Click to collapse
If the build prop hasn't changed I'd say try fix permissions and see if that solves it. Also could try wiping the app cache. All else fails redo the hack for it
Sent from my SPH-L900 using Tapatalk 2
I have redone the hack and it still does not work. Somehow this is working on cm10 based roms but as soon as you come back to a touchwiz rom it force closes. It used to work perfectly on Macs rom, project rom and slim rom but now it does not work on any of them.
stu5797 said:
I have redone the hack and it still does not work. Somehow this is working on cm10 based roms but as soon as you come back to a touchwiz rom it force closes. It used to work perfectly on Macs rom, project rom and slim rom but now it does not work on any of them.
Click to expand...
Click to collapse
I'd try removing the phone from your wallet account online back up your storages reformat then try it again. Maybe there's a file somewhere that's causing the conflict
Sent from my SPH-L900 using Tapatalk 2
Looks like there is some kind of upgrade issue we did/ran into.
http://forum.xda-developers.com/showthread.php?t=2054818, post #3, with the link to below...
http://forum.xda-developers.com/showpost.php?p=35627754&postcount=191
This seems plausible to me...
4. If you running an N7100/7105 rom and have already flashed the nfc fix file or used the nfc files from it, then it is too late. If you recall using those files causes android to upgrade some 270+ files on first reboot. Once that occurs I believe that 4.1.1 apks and lib files makes fundamental changes to a bunch of other apps (like camera, gallery, and etc) which is causing the nfc force closes. You must start fresh again.
Click to expand...
Click to collapse
...if anybody can confirm this to be true...?
Bump.
Just did a factory reset. Total wipe and total re-install.
Total bull$#[email protected]
How can an app "all of a sudden" stop working like this?
Thanks to the couple/few people helping.
I think we flashed a room that meessed with nfc settings and once we messed with nfc settings there is no turning back
stu5797 said:
I think we flashed a room that meessed with nfc settings and once we messed with nfc settings there is no turning back
Click to expand...
Click to collapse
or maybe flashed the zip file with the "bad" libs, and thaty's what cannot be updated (total WAG on that).
(ETA: Post # 643 in link below)
http://www.modaco.com/topic/354635-...let-apk-15-r87-v15/page__st__640#entry2060308
the note2 is missing the correct libs for wallet to work.
you need a new (leaked) rom with them enabled
Click to expand...
Click to collapse
Anybody know of a way to reset those files back to stock/original? or should they be reset if odin'd/flashed over?
I have flashed and odin'd so many times today, I don't even remember what my phone looked like before! Maybe I'll just take mine back and exchange it since I'm under the protection plan.
I still say there's got to be answer/fix for this...
lennykravitz2004 said:
or maybe flashed the zip file with the "bad" libs, and thaty's what cannot be updated (total WAG on that).
(ETA: Post # 643 in link below)
http://www.modaco.com/topic/354635-...let-apk-15-r87-v15/page__st__640#entry2060308
Anybody know of a way to reset those files back to stock/original? or should they be reset if odin'd/flashed over?
I have flashed and odin'd so many times today, I don't even remember what my phone looked like before! Maybe I'll just take mine back and exchange it since I'm under the protection plan.
I still say there's got to be answer/fix for this...
Click to expand...
Click to collapse
I am having the same problem I think it would be better if I just exchange my phone but my phone is outside the 14 day period but I do have insurance. I just don't know I can get an exchange with a lot of problems. I think my phone was flagged.
Sent from my SPH-L900 using xda premium
I just realized that when we edit the build. prop to get the wallet to work, we lose s-note functionality. Wouldn't it be easier to edit the file to mimic that of the galaxy s3? The GS3 wallet does work on the Sprint network. I haven't been able to try it because I don't know what to replace the lines with to make it identical to the s3
Flowed from my Galaxy Note 2.
Are yall using Vipers mod?
Sent from my SPH-L900 using Tapatalk 2
So ever since I got the watch, every day (ie resets once a day) it shows me a stock quote from rl (Ralph Lauren Corp), the watch is the one generating the card because it happens before it synchs with the phone.
The thing is I don't have any stocks entered. I have never had one entered. I don't follow any stocks. This quote seems to be baked into the watch. Anyone else seen it and know what gets rid of it?
Try going to Google.com/finance and see if it is in your portfolio for some reason. If it is, delete it. If it isn't, then I have no idea.
Looks clean, no portfolio.
JeffMD said:
Looks clean, no portfolio.
Click to expand...
Click to collapse
I assume you have checked the Google Now > Customize > Stocks menu?
So strange. If you find a fix, be sure to post back and let us know what resolved it.
Maybe it's a sign that it's time to start investibg
AndroidSlave said:
Maybe it's a sign that it's time to start investibg
Click to expand...
Click to collapse
+1
Dude, its a sign from God
Sent from my LG-E400 using XDA Free mobile app
Pfft... I was guessing more along the lines that Ralph Lauren paid google to be the default demo stock for the stock app. Anyways it still pops up despite not being in any of the areas listed above.
Try opening the Google app on your phone, go to customize and see if its listed as a stock there.
If I were you I would at least attempt clearing all data from Android wear app in settings and doing a factory reset on the 360 itself. Is your 360 on latest 5.1.1?
gocats7 said:
Try opening the Google app on your phone, go to customize and see if its listed as a stock there.
Click to expand...
Click to collapse
Edit: I see that was already suggested, not sure how i missed that post
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...