I've heard that somewhere, the app ShootMe works on unrooted Evos.
Just wondering if this is true, because I have a screenshot of my phone overheating to 130 degrees, on stock rooted, and I need to take my phone to the Sprint store and show them. It would be hard to explain if ShootMe requires root on the Evo...
Check superuser app. If shootme requires root, it will be there.
ywjkid said:
Check superuser app. If shootme requires root, it will be there.
Click to expand...
Click to collapse
I understand that, but I am going to unroot my Evo before I go into the store. I can't have Superuser then, and I have to explain the use of ShootMe to capture my phone overheating.
tropicalbrit said:
I understand that, but I am going to unroot my Evo before I go into the store. I can't have Superuser then, and I have to explain the use of ShootMe to capture my phone overheating.
Click to expand...
Click to collapse
Take a regular photo just in case if you can. When you unroot, download ShootMe again and try to take a screenshot. It should work.
Keep in mind the framework, etc in the screenshot you already have. If it's obviously a custom rom, or if it just looks different than stock, they may question you. They could claim it's a different phone in the shot or that your phone was rooted when you took the photo.
I used ShootMe on my Evo before I rooted it, so unless something changed then it should still work. This was before the latest OTA, though.
(from... Evo/MIUI/Tapatalk)
plainjane said:
Take a regular photo just in case if you can. When you unroot, download ShootMe again and try to take a screenshot. It should work.
Keep in mind the framework, etc in the screenshot you already have. If it's obviously a custom rom, or if it just looks different than stock, they may question you. They could claim it's a different phone in the shot or that your phone was rooted when you took the photo.
I used ShootMe on my Evo before I rooted it, so unless something changed then it should still work. This was before the latest OTA, though.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
That's going to be an issue possibly... I cannot replicate the problem, it just occasionally happens. I was on Deck's ROM when it happened, so it has a different notification bar. I can possibly blame that on Launcher 7, with a custom notification bar.
This will be my second time in the store this week, first time they gave me a new battery and told me to come back if I still had overheating/random rebooting issues. I'm crossing my fingers for a new phone... power button/sound buttons are worn out from flashing so much
Just crop the image so the notification bar doesn't show... unless that's where it is showing the temp. It could be the rom or kernel that's causing the problem. If it doesn't happen on stock then that's most likely the problem. If it does happen on stock, just take a new screenshot then.
But if it's obvious that the screenshot is of a custom rom, I'd just tell them about the problem first and see if they will do something about it. If they won't, then show it to them.
(from... Evo/MIUI/Tapatalk)
The overheating issue happened on every ROM and kernel I tried. Oh well. They ran tests and couldn't duplicate the problem, but they knew me well and took me on my word. Ordered a new phone.
On the way out, showed them the screenshot (in Spare Parts, showing battery information)... they freaked and knew I wasn't joking.
Thanks for your help!
I used Shoot Me on my evo before it was rooted without an issue, as well as a friend of mine.
Sent from my PC36100 using XDA App
Yes it will work on an unrooted evo.
Related
So does anyone else with an epic get a fc on the new google music app. Tried market and standalone and both fc every time.
Sent from my SPH-D700 using XDA Premium App
Hmm it works for me
Sent from my Samsung Epic
It won't work at all, i've tried removing my music.apk from system and it just stays stuck on installing.
Weird. By your sig, I can tell you're running SRF so the ROM isn't causing it. Maybe it's just a glitch or something. Try rebooting the phone?
acer1096xxx said:
Weird. By your sig, I can tell you're running SRF so the ROM isn't causing it. Maybe it's just a glitch or something. Try rebooting the phone?
Click to expand...
Click to collapse
Ya something is bugged, it now says the app is installed after changing permissions but now the apk is nolonger in my /system/app folder lol Titanium backup shows it as active but can't uninstall because it can't find the apk. dang i think something is way messed up. I might just reflash or nandbackup.
juanaraya92679 said:
Ya something is bugged, it now says the app is installed after changing permissions but now the apk is nolonger in my /system/app folder lol Titanium backup shows it as active but can't uninstall because it can't find the apk. dang i think something is way messed up. I might just reflash or nandbackup.
Click to expand...
Click to collapse
I wouldn't do that just yet unless you're THAT willing. I mean, the OP didn't get it to work either. Maybe I got lucky and the market is having issues in your area. Idk, just I wouldn't jump to reflashing so quickly
acer1096xxx said:
I wouldn't do that just yet unless you're THAT willing. I mean, the OP didn't get it to work either. Maybe I got lucky and the market is having issues in your area. Idk, just I wouldn't jump to reflashing so quickly
Click to expand...
Click to collapse
Ya didn't flash just yet, going to mess with it on the weekend. I will let ya'll know if I figure this out, perhaps if I do it would help others who have the same weird issue.
I am stock rom, rooted, running mrket stand alone and have had no issues, no fc's and have been messing with it for the better part of the morning (few hours)
Epic is as Epic does.
it worked for me but i'm not in the beta and the samsung player was better for me so i deleted it. for some reason the last fm scobbling would not stop when it was enabled for the google music player also.
Worked for me on both the stock rom, and on Frankenstein Froyo. Only issue I have is not yet having an invite to the actual service.
This sounds like you may have remnants of it in your dalvik-cache. Have you tried wiping it and re-checking afterwards?
juanaraya92679 said:
Ya something is bugged, it now says the app is installed after changing permissions but now the apk is nolonger in my /system/app folder lol Titanium backup shows it as active but can't uninstall because it can't find the apk. dang i think something is way messed up. I might just reflash or nandbackup.
Click to expand...
Click to collapse
so when i take pics on the phone, they dont show up in the gallery.... i usually have to reset the phone, or take the battery out to make them show up... then after a while i have to do it again etc....
any ideas how to fix this?
kneedraggin101 said:
so when i take pics on the phone, they dont show up in the gallery.... i usually have to reset the phone, or take the battery out to make them show up... then after a while i have to do it again etc....
any ideas how to fix this?
Click to expand...
Click to collapse
Are you rooted with a custom rom, or stock?
Sent from my shiny metal G2 w/ meXdroid V3
Search market for an app called 'Rescan Media'. Run this to update the gallery with all photos you have taken. It's a fairly common problem (at least on stock, don't know about with other ROMs). Hopefully the 2.3 update will sort this out.
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.
Hey all,
I have had some minor experience in unlocking and rooting my older android devices, but I was wondering if someone could shed some light on the current state of affairs. I just received a brand new nexus 7 and am trying to decide whether or not to unlock/root it.
I remember back with my Xoom as soon as I unlocked the boot-loader, Hulu stopped working. Is this still true? Are there any other side effects like that?
Thanks for all the help everyone
Nexus is basically made for rooting so no worries.
Sent from my Nexus 7 (2013) using Tapatalk 4
Some apps don't run if you're rooted. However, that's usually not for any technical reason; it's just because some app makers write a check for root into their apps and refuse to run if they find root. I don't know if Hulu is like that, but you might want to check if you have any apps that are like that. Alternatively, you can always unroot or use a hide root app to get around the app check.
bananagranola said:
Some apps don't run if you're rooted. However, that's usually not for any technical reason; it's just because some app makers write a check for root into their apps and refuse to run if they find root. I don't know if Hulu is like that, but you might want to check if you have any apps that are like that. Alternatively, you can always unroot or use a hide root app to get around the app check.
Click to expand...
Click to collapse
Which Hide root app do you suggest ?
I was going to recommend OTA Rootkeeper, but apparently 4.3's security changes prevent it from working. As far as I can tell, it looks like you can't hide root on 4.3.
Can anyone confirm whether or not Hulu works with Root?
monkeyman08854 said:
Can anyone confirm whether or not Hulu works with Root?
Click to expand...
Click to collapse
I use it a few times a week to watch stuff. Works fine on my rooted N7 with CleanROM and ElementalX kernel.
I don't see how I get all kind of errors when I try rooting this is it cuz I'm using winxp?
Sent from my Nexus 7 using xda app-developers app
the one and only downside of rooting is you start suffering from ORD (Obsessive ROM-updating Disorder). I've been suffering it for past few months, and it seriously gets to my head sometimes.
Symptoms:
1) You feel like updating your ROM every day a nightly comes out, even if it is without any change. Just because it has a different incremental number.
2) You can't concentrate on studies, tv, movies, GFs, or even on your potty.
3) You dream about a new nightly every night after flashing current nightly.
4) You have titanium backup on your device.
Cure:
1) no cure.
I can't think of a single app that doesn't work with while rooted. It used to be Google Movies didn't work, but that's no longer the case.
Rooting isn't a big deal. The worst part is that it resets your devices to stock, so backup first.
MikeMurphy said:
I can't think of a single app that doesn't work with while rooted. It used to be Google Movies didn't work, but that's no longer the case.
Rooting isn't a big deal. The worst part is that it resets your devices to stock, so backup first.
Click to expand...
Click to collapse
Sky Go! doesn't and so far there appears no work around. Unless someone has heard something!
I had some gps lock on issues after rooting, but now that its rooted I can edit the gps.conf and fix issues.
Found a good repository for gps.conf files will help in specific areas https://m.app.box.com/view_shared/w57s1v1n3hie7l5lk28i/d_1033932257
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...