{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just updated my T-Mobile Tab s4 to Pie. I was hoping the Tab S5e message and calling feature would come to this tablet. Well, it did, but is blocked. It is baked into the Pie update and alive on the tablet (see screenshot), i just cannot access it. Any savvy geniuses out there want to get this figured out?
Any luck?
Could you flash an international ROM possibly? I'm not sure exactly what would be compatible or not.
I have a SMT835N and recently tried a Sprint ROM and Phone ability was removed. I am wondering if the same limitation is applied across US carriers and if that limitation is not present in international versions.
Hi. Your post doesn't show any screenshot. How do I get there? I have the Wi-Fi version.
jeremythielman said:
I just updated my T-Mobile Tab s4 to Pie. I was hoping the Tab S5e message and calling feature would come to this tablet. Well, it did, but is blocked. It is baked into the Pie update and alive on the tablet (see screenshot), i just cannot access it. Any savvy geniuses out there want to get this figured out?
Click to expand...
Click to collapse
Call and message continuity (as far as I know) didn't get added to the S4. Maybe for the LTE versions, but my US wifi model doesn't even have the option. Can you post a screenshot of what you're seeing?
I'm not seeing it on my T-Mobile S4 at all...
My UK Wifi Tab S4 got Continuity with the Pie update, but I was only able to use it when my S10+ received an update this week.
Screenshots?
My tab s4 does not have call option with any update
I found something potentially interesting. I'm not sure about the inner workings of Call and Message Continuity, but it seems like it might be an apk? There is an app with that name on apkmirror. I downloaded and tried to install it but it just says install failed..... If that's all that's needed maybe it needs to be a system app?
Related
I've encountered something on my VZW Galaxy Nexus that appears completely new to me. I did some online research but found no one with similar problems.
To give a little background, I encountered this problem after I hit the "traffic to home" Google Now tile which took me to Google Maps. After hitting this tile, though, the graphics for traffic on my Google Maps has become very low resolution. Normally, you see two lines on each freeway, one in each direction. Right now, those lines are all blurry and overlap to the point where I can't see both lanes. It looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I zoom in enough, I can get it to look like it normally does, but zooming out slightly makes it go right back to fuzzy-garbage-traffic:
Anybody know what happened? I uninstalled and reinstalled Maps, but it didn't help.
I'm experiencing a similar issue on my Galaxy Note II on AT&T. I just noticed it yesterday. And it was after I flashed my phone to Cleanrom 4.7. If I zoom in closer, the lines become sharp and are no longer blurry. Not sure how to fix it.
Getting the same thing on my EVO on Sprint. It appears that people have started taking to posting comments in the Play store as well:
https://play.google.com/store/apps/...DEsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I went a step further and reported it using the "Feedback" option in the map.
subhumanderelict said:
Getting the same thing on my EVO on Sprint. It appears that people have started taking to posting comments in the Play store as well:
https://play.google.com/store/apps/...DEsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I went a step further and reported it using the "Feedback" option in the map.
Click to expand...
Click to collapse
I'm getting this too on my Galaxy Note on CM10.1. I think this happened after the last update. Hope they fix it soon. Very annoying?
christran12 said:
I'm getting this too on my Galaxy Note on CM10.1. I think this happened after the last update. Hope they fix it soon. Very annoying?
Click to expand...
Click to collapse
Wiped and updated to the latest nightly of CM10.1 and the problem is gone.
A couple of days ago, a notification to update SPDClient appeared in Galaxy App Store (Samsung Apps). But what is this app for, and what does the update do? The descriptions does not show any relevant information and there are many comments asking what does this app do.
Does anyone know about this app?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It tells you in the app description what it is.
Sent from my leanKernel 3.7 powered stock 4.4.2 (NF4) SM-N900T
I also got that and was little afraid of updating, worrying if Samsung trying to sneak some security update for Knox, or root discovery etc.(I'm stock rooted). But it seems to be internal driver related to data exchange over networks, possibly updated due to new hardware like VR or S-watch. I updated it now, so in case I buy Samsung watch or some other new hardware in near future, I won't go crazy wondering why it doesn't work, since once you decline the update, usually doesn't come back anymore.
pete4k said:
I also got that and was little afraid of updating, worrying if Samsung trying to sneak some security update for Knox, or root discovery etc.(I'm stock rooted). But it seems to be internal driver related to data exchange over networks, possibly updated due to new hardware like VR or S-watch. I updated it now, so in case I buy Samsung watch or some other new hardware in near future, I won't go crazy wondering why it doesn't work, since once you decline the update, usually doesn't come back anymore.
Click to expand...
Click to collapse
Any idea if updating this app affects root?
tony yayo said:
Any idea if updating this app affects root?
Click to expand...
Click to collapse
It does not.
Sent from my leanKernel 3.7 powered stock 4.4.2 (NF4) SM-N900T
Hi, I recently bought a Tab S 8.4 online (ebay). 'Refurbishment check' Using phone info app says that the device is not genuine and it couldnt find IMEI or baseband. Can anyone please testt their wifi only tab with Phoneinfo app and let me know the result. I attached the screenshot for your reference.It does have a serial number though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cough cough. That's because I am on a custom rom. I dont think wifi devices need Imei. Someone correct me if I am wrong. But you ahould be fine if you have the same chip stuff. Download CPUZ and check your chipset. It should say exynos something and a bunch more.
DUHAsianSKILLZ said:
Cough cough. That's because I am on a custom rom. I dont think wifi devices need Imei. Someone correct me if I am wrong. But you ahould be fine if you have the same chip stuff. Download CPUZ and check your chipset. It should say exynos something and a bunch more.
Click to expand...
Click to collapse
Thanks for the quick reply bro..lets see what it will show on others.
I used Antutu benchmarks and after running the test, it showed the chipset, resolution, ram, camera and other info..everything seems to match with the specifications of SM-T700.
vishnu8058 said:
Hi, I recently bought a Tab S 8.4 online (ebay). 'Refurbishment check' Using phone info app says that the device is not genuine and it couldnt find IMEI or baseband. Can anyone please testt their wifi only tab with Phoneinfo app and let me know the result. I attached the screenshot for your reference.It does have a serial number though.
View attachment 3163073
Click to expand...
Click to collapse
You shouldn't worry. You have all OK! The Phone Info Samsung program so defines WiFi the SM-T700 version. Really this Tab version has no IMEI and Baseband.
IMEI is a mobile security number for identiy/theft.
It wont have one unless it is 4G.
FoxFi has survived the latest update to marshmallow 6.0
Can confirm it works on Verizon LG G4 6.0 VS98624C
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, I was holding my update because of this.
I'm on the v10 with Verizon and it just randomly stops. Anyone else having problems
I can confirm it works fine on 25a also.
Has anyone tried to wifi hotspot with foxfi with a different sim card in a Verizon g4? Thank you
Kevinrdz91 said:
Has anyone tried to wifi hotspot with foxfi with a different sim card in a Verizon g4? Thank you
Click to expand...
Click to collapse
I assume by "g4" you mean a Galaxy Note 4? If so, I have tried it, and initially it was not working for me. I have a 3 mobile SIM card (I'm in the UK now) in my Verizon Note 4 with the latest Marshmallow update (build number MMB29M.N910VVRU2CPF3) and when I tried to turn on WiFi tethering via FoxFi, it went through Starting Hotspot...1, 2, 3 messages and then I just get a message saying that it couldn't start the hotspot (I forgot to write down the exact message).
It also didn't seem to be able to control the hotspot at all, since when I start the WiFi hotspot on its own (without FoxFi), it started up, then I went into FoxFi to stop it, it gave me a message about not having started it, closing anyway, yet the hotspot kept running...
HOWEVER, as I was typing this up, I was going through the process to be able to write down some of the details - and like magic, it started working! ;] I have absolutely no idea why it started working now, I don't recall changing anything at all. The only thing is that the hotspot was active all night (forgot to turn it off - heh). Well, I'll take it! :laugh:
HerbCSO said:
I assume by "g4" you mean a Galaxy Note 4?
Click to expand...
Click to collapse
Dude, you are in the "Verizon LG G4" forum... so g4 doesn't mean Galaxy Note 4!
Whoops, sorry! Dropped into this from a search and didn't pay attention to which forum it was. Mah bad! ;]
No worries, I appreciate you trying to help, just thought it was funny.
Hope this is the correct spot for this... I loaded a new rom on my old Sprint Samsung Galaxy SIII a couple years back (not sure which rom now) but I kept getting the popup shown in the image, finally got frustrated and pretty forgot about the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Found the device again this week and I'm now wanting to use it in my office mainly for streaming music to a bt speaker. However I'm wondering 2 things - first is there a way to get rid of this pop up on this particular rom?
And #2 any suggestions on what rom I should be using on this device to use it as a media streamer? Will need bt access and wifi, camera would be nice as well as use of the microSD slot... suggestions welcome!
TheDrake2k said:
Hope this is the correct spot for this... I loaded a new rom on my old Sprint Samsung Galaxy SIII a couple years back (not sure which rom now) but I kept getting the popup shown in the image, finally got frustrated and pretty forgot about the device.
Found the device again this week and I'm now wanting to use it in my office mainly for streaming music to a bt speaker. However I'm wondering 2 things - first is there a way to get rid of this pop up on this particular rom?
And #2 any suggestions on what rom I should be using on this device to use it as a media streamer? Will need bt access and wifi, camera would be nice as well as use of the microSD slot... suggestions welcome!
Click to expand...
Click to collapse
Looks like the stock ROM, definitely a TouchWiz based ROM. That message on screen could be one of the settings in developer options. USB notification in status bar too. Look for settings about showing stats, turn them off.
ROMs, for media streaming, stock is fine. Just a little outdated. Lineage is on nougat 7.1.2 now. Everything works fine on it. Octos is on nougat as well. Both have currently maintained ROMs for Sprint S3.
This is because your efs got wiped or modified
I think that this is because your efs partition got modified or wiped during installation or something, you can fix that using EFS Professional.
You can go here and find out how :
https://forum.xda-developers.com/ga...ol-updated-09-06-14-efs-professional-t1308546