Related
Does anyone know if a lockscreen widget that would put the small icon with a number for notification of incomimg messages (and emails too).
Im looking for something similar to the 4.1 style o lockscreen notifications.
Anyone have any suggestions?
Try dash clock.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Big-A-Rob said:
Try dash clock.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
+1 dash clock FTW
polish_pat said:
+1 dash clock FTW
Click to expand...
Click to collapse
how can i get this on my lock screen? i have it working on my home screen but my lock screen only has one screen so I can't add it as a widget.
onlynismo said:
how can i get this on my lock screen? i have it working on my home screen but my lock screen only has one screen so I can't add it as a widget.
Click to expand...
Click to collapse
Settings. My device. Lockscreen. Allow multiple widgets.
_Dennis_ said:
Settings. My device. Lockscreen. Allow multiple widgets.
Click to expand...
Click to collapse
my options under lock screen are:
screen lock
lock screen widgets
secured lock time
when i clock on lock screen widgets, i just get the clock settings.
onlynismo said:
my options under lock screen are:
screen lock
lock screen widgets
secured lock time
when i clock on lock screen widgets, i just get the clock settings.
Click to expand...
Click to collapse
Have to be in 'swipe' lockscreen (ie no password/dots/face unlock)
_Dennis_ said:
Have to be in 'swipe' lockscreen (ie no password/dots/face unlock)
Click to expand...
Click to collapse
ahhh...damn. i need the password cause of exchange e-mail.
thanks!
I'm in the same boat. Is there a workaround for this? Maybe for rooted devices?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
rohitvis said:
I'm in the same boat. Is there a workaround for this? Maybe for rooted devices?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=41021447
He says it works.
onlynismo said:
ahhh...damn. i need the password cause of exchange e-mail.
thanks!
Click to expand...
Click to collapse
_Dennis_ said:
http://forum.xda-developers.com/showthread.php?p=41021447
He says it works.
Click to expand...
Click to collapse
If that's the only reason you need the lock screen password then yes I can confirm once again that it works. Just follow the thread.
Another option is to use WidgetLocker. Then you would have the lockscreen Dashclock and a customizable unlock slider, and then a password/pattern lock screen afterwards. This is what my wife uses, and it works well.
Isn't the smartest option to just use the Quick Glance Air Gesture? It does show unread messages and emails after all......
KryptosXLayer2 said:
Isn't the smartest option to just use the Quick Glance Air Gesture? It does show unread messages and emails after all......
Click to expand...
Click to collapse
Not the same. The lockscreen is a bit more convenient IMO. Quick glance would require an extra step to unlock the phone.
_Dennis_ said:
Not the same. The lockscreen is a bit more convenient IMO. Quick glance would require an extra step to unlock the phone.
Click to expand...
Click to collapse
#firstworldproblems
Come on, read what you just wrote, seriously? Haha....
Sent from my Samsung Galaxy S 4 using the XDA app
KryptosXLayer2 said:
#firstworldproblems
Come on, read what you just wrote, seriously? Haha....
Sent from my Samsung Galaxy S 4 using the XDA app
Click to expand...
Click to collapse
Yea really and I did read what I wrote. We're talking about how to fix a $600 phone to make it work BETTER. Of course its notbon the same level as curing cancer or world hunger. From what I've read in your post your always right. Bud just because someone else wants to mess with their phone when they have to Odin to fix it, or they are looking for a solution to a problem you feel is unimportant does not mean they are less then you. Some of us want to make our phones as good as they can be FOR US. This is what this whole site is about. DEVELOPING ways to IMPROVE our phones. Improvement for ke may mean nothing for you but still it deserves a place here. This site is not KryptosXLayer2-development.com.
_Dennis_ said:
Yea really.................. .
Click to expand...
Click to collapse
WHOA, settle down, good God! Apparently this issue IS as important as world hunger or curing cancer to you!
You don't have to attempt to educate me on why we screw around with these phones, I'm not new to this, chief..... I just recommended something that works for JUST as well, but you've obviously got some issues to resolve in your own life, so have fun dealing with all that, geez!
Sent from my Samsung Galaxy S 4 using the XDA app
KryptosXLayer2 said:
WHOA, settle down, good God! Apparently this issue IS as important as world hunger or curing cancer to you!
You don't have to attempt to educate me on why we screw around with these phones, I'm not new to this, chief..... I just recommended something that works for JUST as well, but you've obviously got some issues to resolve in your own life, so have fun dealing with all that, geez!
Sent from my Samsung Galaxy S 4 using the XDA app
Click to expand...
Click to collapse
Everyone has their issues in life. Mine are fairly minor. I'm just not big on stopping progress just because I feel the immediate effects are useless. To me the end result could be something amazing. This might end up inspiring someone to get AOSP lockscreen working, or even someone to learn to code etc. Basically I see it as an opportunity. I took your comment the same way I take people who dont want to research basic science or ways to save certain animals from extinction etc because they dont see the immediate point. Of course this is much less important but the thought process seemed the same "I wont benifit in the next few days, who cares". I try to allow my mind to stay open, and to see opportunities were ever they appear. I dont honestly think 5 threads about bootloaders aee needed or the AdamOutler's thread is needed yet (I personally would have waited until Dan released his hack to expect the theead to stay on topic since so many people laced so much hope on Dan that theybare foing to talk about it every were they can.) But I dont go around telling these people they are wrong and their issues unimportant. I let the threads be and check in from time to time to see if anything meaningful has occured. Maybe it's just the American in me be I perfer to let people have their important issues and help those I can and those I agree with while not bothering those whom I can't help or those whom I don't agree with.
---------- Post added at 06:08 AM ---------- Previous post was at 06:03 AM ----------
mattdm said:
Another option is to use WidgetLocker. Then you would have the lockscreen Dashclock and a customizable unlock slider, and then a password/pattern lock screen afterwards. This is what my wife uses, and it works well.
Click to expand...
Click to collapse
I like widgetlocker. Only issue I have is sometimes it does not load, or is slow to load. These are nit to bad though and this is what is holding me over until I can mess around and try to enable AOSP lockscreen.
So now KitKat is out with a new full screen mode that apparently breaks whatever mechanism was previously used to go full screen. So is it technically possible to somehow force an app to use immersive mode?
Sent from my Nexus 4 using xda app-developers app
drinkypoo said:
So now KitKat is out with a new full screen mode that apparently breaks whatever mechanism was previously used to go full screen. So is it technically possible to somehow force an app to use immersive mode?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
"To provide your app with a layout that fills the entire screen, the new SYSTEM_UI_FLAG_IMMERSIVE flag for setSystemUiVisibility() (when combined with SYSTEM_UI_FLAG_HIDE_NAVIGATION) enables a new immersive full-screen mode. While immersive full-screen mode is enabled, your activity continues to receive all touch events. The user can reveal the system bars with an inward swipe along the region where the system bars normally appear. This clears the SYSTEM_UI_FLAG_HIDE_NAVIGATION flag (and the SYSTEM_UI_FLAG_FULLSCREEN flag, if applied) so the system bars remain visible. However, if you'd like the system bars to hide again after a few moments, you can instead use the SYSTEM_UI_FLAG_IMMERSIVE_STICKY flag."
Found at developer.android[dot]com/about/versions/android-4.4.html
It would be cool if there was a method to force this mode selectively of globally for all apps with some sort of control with root.
bunklung said:
It would be cool if there was a method to force this mode selectively of globally for all apps with some sort of control with root.
Click to expand...
Click to collapse
no, no it would not, and no, no it would not work for many!
Wtf are you talking about? Of course it would be desirable and work for many. You just add ONE FLAG to the properties (IMMERSIVE_STICKY) and the application does not even need to be aware!
Sent from my Nexus 4 using xda app-developers app
Already asked developer of full!screen to address this but no response.
Would edit comment but xda app won't let me touch latest post on kitkat, usual high quality of tapatalk
Sent from my Nexus 4 using xda app-developers app
drinkypoo said:
Wtf are you talking about? Of course it would be desirable and work for many. You just add ONE FLAG to the properties (IMMERSIVE_STICKY) and the application does not even need to be aware!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
nope... depends on the design of the app as to if it would work with the UI, it should stay a design decision not a system/platform one!
Look, apps not going full screen has already been a big problem for android for YEARS. That's why there are so many apps that make apps full screen, like full!screen+. But now Google has made it impossible to hide the navigation bar any way OTHER than immersive mode. Consequently I will be sticking with jelly bean for the foreseeable future because there is no other way to use certain apps full screen. Once again Google breaks something I am using for no reason.
Unfortunately you will get your way even though you are wrong. Apparently you can only initiate immersive mode initially, and not from outside the program. According to the developer of full!screen+ anyway.
There is literally NO valid argument against an app being to force immersive_sticky mode. NONE. The app is not aware of it at all, and it's MY phone, not the app developer's. Don't tell me how I want to use my phone, and I won't tell you where to go and what to do when you get there.
Sent from my Nexus 4 using xda app-developers app
Not about right or wrong, and it should not get you wound up. My app would be worse off if you could do it... So no... Bad idea cause I designed my app to use the back button for navigation. If the app design allows... Sure would be good.. If not... No lol
Sent from my Nexus 5 using XDA Premium 4 mobile app
deanwray said:
Not about right or wrong, and it should not get you wound up. My app would be worse off if you could do it... So no... Bad idea cause I designed my app to use the back button for navigation. If the app design allows... Sure would be good.. If not... No lol
Click to expand...
Click to collapse
Sigh. Please read up on Immersive mode: https://developer.android.com/training/system-ui/immersive.html
The user swipes from the edge of the screen to show the UI, and then they can press the back button.
Please educate yourself.
drinkypoo said:
Sigh. Please read up on Immersive mode: https://developer.android.com/training/system-ui/immersive.html
The user swipes from the edge of the screen to show the UI, and then they can press the back button.
Please educate yourself.
Click to expand...
Click to collapse
BTW I mean and intend no malice or to be condescending..
As condescending as you are attempting to be... I personally think you should come back after having designed a few apps.. Obviously I know what it is and know what kiosk mode was very early in Android... Anyway.. Look... I don't like arguing... But I like it less when someone attempts to dictate terms of Ui design.. While also assuming I need to educate myself... I think that's about the dumbest thing you could have said.. Please note that I have not intended to argue and only offer what I thought would be a valid opinion given my experience... I'm not going to explain / educate you on user flow/ Ui design.. But if you do read there are some good books that should demonstrate a few things that would say it's not the best idea. It obviously depends on design principals and methods in use in the app. Anyway I didn't comment on this thread to argue, only offer an opinion... I think you should be a little more open minded as to opinions, who people are, their experience and have a little more respect.. I apologise if anything I have said offends, as always I'm just attempting to be helpful, will leave this thread and unsub. Good luck in your search
Edit: sigh...ugh, ok my helpful nature came back to me, there are many reasons why this would/could and maybe a bad idea for some but not all apps. Here are a few reasons that initially came to mind.
Dev:
Popup view placements with custom menus in apps (rather than using absolute screen coords (as you cant and it's dependant on android version what is reported) devs sometimes have to hack a solution based on system bar and status bar metrics and calculations, this would screw them and they would now have to check the state, hence why it's an app controlled thing!)
Fixed optimized surfaceView or custom renderer handling, user controlled views that change size with no callbacks or state changes and with no android configuration calls can be very bad. Won't explain this one too much. But at the least it would require devs to implement listeners or callbacks, not something that they would do accidentally allowing it to work.
Design:
if using on screen system bar UI controls (back key, onscreen) that is offscreen, then simply going back becomes a gesture and a click, which is fine unless your design dictates this happen lots.
neways thats a few "opinions" and reasons.
drinkypoo said:
Please educate yourself.
Click to expand...
Click to collapse
I always am and do.... how about you?
Sent from my Nexus 5 using XDA Premium 4 mobile app
I hope you do unsub, and leave me alone in the future. Telling me, the user, that I shouldn't have what I want is beyond ridiculous. And since there's no reason whatsoever (and you have utterly failed to present one, in spite of your attempts to be condescending) why I shouldn't be able to decide if an app is full screen, I wish you'd delete your comments too so that this thread could be used for some useful purpose.
drinkypoo said:
I hope you do unsub, and leave me alone in the future. Telling me, the user, that I shouldn't have what I want is beyond ridiculous. And since there's no reason whatsoever (and you have utterly failed to present one, in spite of your attempts to be condescending) why I shouldn't be able to decide if an app is full screen, I wish you'd delete your comments too so that this thread could be used for some useful purpose.
Click to expand...
Click to collapse
hang on I came back to help...and no I apologize yet again if you think that I was attempting to be condescending, that is not the case, I'm attempting to say why it would be a bad idea "to let the user control the system" in such a way. Personally I think immersive mode in apps should be put in by the dev, but be accounted for and designed around. That was my point. I think you have missed what I was attempting to say... and no, despite 17 years of design/vfx/software etc, I have no more right to tell you to educate yourself than you do me, that was another point... anyways sorry you don't get what I was saying (how it would crash/fc some apps, cause that is a fair reason) or how I explained it... good luck again
deanwray said:
anyways sorry you don't get what I was saying (how it would crash/fc some apps, cause that is a fair reason) or how I explained it... good luck again
Click to expand...
Click to collapse
Apps are not aware of immersive mode, how would it crash/fc some apps, and even if it did, why is that an argument against letting the user attempt it? There's tons of apps promoted here on XDA which will cause apps or even devices to crash if misused, hell, even to be bricked. Are you against all of those apps, too? That is what you didn't explain. You're also engaging in the logical fallacy of appeal to experience when you don't have experience actually trying to do this, and you're only engaging in FUD. You didn't come back to help, you came back to continue your argument against what I want and why? Because you're insulted that someone might believe that the developer in fact does not know best?
This is not my first time around the track with a developer who thinks they're wonderful and that users are ignorant and that nobody but them could possibly know what someone might want to do with their device, or with an app. But users are extremely well-versed in one thing: what they want. And what I want is to be able to force immersive mode for apps which don't employ it, mostly because they were written and then abandoned before KitKat was released and before there was such a thing. In such a case, or in any other case, what the developer wants is irrelevant. That is to say, you are irrelevant. Someone who actually wants to help achieve the goal of being able to force immersive mode would be relevant.
For what it's worth, I'm an IT professional with a good twenty years of experience. Developers are worthless without IT, and vice versa. And neither one has a purpose without the user. Hop off your high horse, and either help or don't.
lol, omg! I don't know how you are taking me the way you are... ok this is the last time I'm going to apologize now cause I intend neither malice or to be condescending or anything of that nature, and I as a "new" dev value not only opinions of strangers but highly value opinions of users beyond what I have seen in other devs! I apologize if you think I'm questioning you in some way... again I am not at all, I'm simply pointing out what "I think would happen and why", although I'm somehow failing to explain/communicate properly.
drinkypoo said:
Apps are not aware of immersive mode, how would it crash/fc some apps, and even if it did, why is that an argument against letting the user attempt it?
Click to expand...
Click to collapse
It's the fact that they are not aware of it, android is a fair platform, but not the best when handling any change in the view tree. So here is an example of performance hit... a listView is a type of view user in almost all apps. Here is what would happen from a framework standpoint if lets say, an animation was triggered to get rid of the system bars that the app didn't know about and the dev hadn't planned for...
the listView starts to expand, the 1st indication of this is it gets incremented in height by (some pixel value/cycle animation)
the listView now triggers invalidate(), this causes all backing data to be read again and all views in the list to refresh and is "blocking" (i think) (as in hangs on the main thread and can stop/slow the UI)
it then redraws all the child views when this is done
repeat for every frame of animation..
thats just 1 little example btw, I can think of lots here and some cause FC's
There's tons of apps promoted here on XDA which will cause apps or even devices to crash if misused, hell, even to be bricked. Are you against all of those apps, too? That is what you didn't explain. You're also engaging in the logical fallacy of appeal to experience when you don't have experience actually trying to do this, and you're only engaging in FUD. You didn't come back to help, you came back to continue your argument against what I want and why? Because you're insulted that someone might believe that the developer in fact does not know best?
Click to expand...
Click to collapse
Not against any apps or mods of any kind (although I must admit that some mod influenced crashes have caused me to have to spend time accounting for them) thats not all that nice
I 100% assure you I did not come back to argue, maybe to present a point better yes, but not for any other reason than I think you took/are taking me the wrong way entirely
Also I would never say I know best, ever, there is no guarantee that it would be "ever" true!
This is not my first time around the track with a developer who thinks they're wonderful and that users are ignorant and that nobody but them could possibly know what someone might want to do with their device, or with an app.
Click to expand...
Click to collapse
Ok that is entirely wrong, and I apologize (really last time) if you got that impression!!! You are sounding more like you have had very bad experiences with android developers!
But users are extremely well-versed in one thing: what they want. And what I want is to be able to force immersive mode for apps which don't employ it, mostly because they were written and then abandoned before KitKat was released and before there was such a thing. In such a case, or in any other case, what the developer wants is irrelevant. That is to say, you are irrelevant. Someone who actually wants to help achieve the goal of being able to force immersive mode would be relevant.
Click to expand...
Click to collapse
we are all irrelevant But again I think your taking me/this the wrong way, I keep saying I would "LOVE/LIKE" apps to be designed and updated for this... I actually was very angry at android for 3.0 and forced systembar (end of kiosk mode)
I was simply pointing out why/how such a thing may cause problems if not designed for and accounted for both visually and technically!
Hop off your high horse, and either help or don't.
Click to expand...
Click to collapse
ok last time really really, there is no high horse here, so nothing to hop down off, out of most I know I am probably one of the humblest you could ever meet and actually most critical of myself too! So sorry if you took me the wrong way!
Again, yes it would be a good "design" idea, no it probably would not be good technically given how "lots" of apps are written.
I think it maybe possible with root, but I also think it may crash a large amount of apps...
Well, sorry, maybe I would have taken you differently if you hadn't attacked my idea right away. If you wanted to be helpful why didn't you try that first?
Anyway, it is supposedly impossible to activate later but I would love that to be false
Sent from my Nexus 4 using xda app-developers app
drinkypoo said:
Well, sorry, maybe I would have taken you differently if you hadn't attacked my idea right away. If you wanted to be helpful why didn't you try that first?
Anyway, it is supposedly impossible to activate later but I would love that to be false
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well I wouldn't call what I said an "attack on the idea" but maybe I should have explained more about why it is not a good idea given on how the android framework expects things.... dont be so quick yourself to attack, defend or assume, as I think I have said all along, it would be a good idea if it wasn't for "android constraints" ... or rather maybe I should have started out that way... tbh I can see a way that it could be done with some "google" love to the api, but not without...
if you could convince google to alter viewGroups or multi view holders to have adaptive offsets for the top and bottom containers, and that there was also an interface listening by default to what window mode it was in, then lots of the problems both design and technical could be overcome. But in all honestly it took them 3 updates to fix a quite simple but annoying keyboard bug, so would not hold my breath on a request such as this
EDIT : thinking about it, would be easier to just convince developers to include support for it. There is not much to it tbh, I may try with smart messenger when I get all core features finished!
deanwray said:
if you could convince google to alter viewGroups or multi view holders to have adaptive offsets for the top and bottom containers, and that there was also an interface listening by default to what window mode it was in, then lots of the problems both design and technical could be overcome.
Click to expand...
Click to collapse
The whole point of the immersive sticky mode is that the App doesn't know it's happening! The very point is that it can be added to an app without any other changes. The app is totally unaware that the UI is being presented, and it is not intended to know because it is not intended to rescale itself! Your objections all apply to IMMERSIVE mode, I don't see how they apply to IMMERSIVE_STICKY at all. You want the app to know what is happening, but it is critical that it not know if it is going to work correctly without any changes to the app itself!
That is why you are boggling my mind so hard. The app isn't supposed to know that the UI is being presented or hidden, and I don't want it to because I don't want it trying to resize itself or do anything else "tricky", for which you should read stupid. It's stupid because if the app tries to do that stuff it will probably fail, and further there is no need for it to happen.
drinkypoo said:
The whole point of the immersive sticky mode is that the App doesn't know it's happening! The very point is that it can be added to an app without any other changes. The app is totally unaware that the UI is being presented, and it is not intended to know because it is not intended to rescale itself! Your objections all apply to IMMERSIVE mode, I don't see how they apply to IMMERSIVE_STICKY at all. You want the app to know what is happening, but it is critical that it not know if it is going to work correctly without any changes to the app itself!
That is why you are boggling my mind so hard. The app isn't supposed to know that the UI is being presented or hidden, and I don't want it to because I don't want it trying to resize itself or do anything else "tricky", for which you should read stupid. It's stupid because if the app tries to do that stuff it will probably fail, and further there is no need for it to happen.
Click to expand...
Click to collapse
not quite sure if you just called me stupid there Hopefully I read it wrong... the problem is that the available app space would change though right ? Meaning that views would change size. To prevent this the app would need a few things designed into it, so yes you are correct in that there would be no need for a listener with STICKY, but the developer would have had to set flags on both windowManager layout and the base View (SystemUi) (this is what i mentioned with offsets based on UI space, all it does is expand the app to fullscreen "underneath" the System bars) ... so yeah, in the end it is the app that needs to do this, because without that space will change and then the problems start...
Hope I explained that enough ?
deanwray said:
the problem is that the available app space would change though right ? Meaning that views would change size.
Click to expand...
Click to collapse
WRONG. This is why I told you to go read up, do your research, et cetera. It wasn't arrogance, it was because you clearly had not done these things, and needed to before you could make an intelligent, insightful contribution.
This is what differentiates IMMERSIVE_STICKY mode from IMMERSIVE mode. The UI elements appear on top of your application. The available app space does not change. When the user is done using the UI elements, or when they time out, they fade away and your app is left sitting there full screen just like it was throughout the presentation of the UI. Your app is utterly and completely unaware of and unaffected by the presentation of the UI elements.
I treated you the way I did because it was clear that you were coming from a position of ignorance, and meanwhile accusing me of the same. Now that is arrogance.
http://phandroid.com/2016/03/02/samsung-galaxy-s7-tips-tricks/
This page discusses some features in the GS7/GS7 Edge. T-Mobile removed "Galaxy Labs," meaning there is no ability to remove the app drawer, have the Whitepages features, or have voice activated dialing w/ searching for contacts. We cannot have the "experimental" features Samsung wants to make on its devices. Just a PSA. Idk what to do tbh? T-Mobile might be trying to push its own Caller ID app, which not many people will be interested in if there are free alternatives baked into the phone.
Shenanigans like that should be illegal.
Sent from my SM-G935T using Tapatalk
I think they also messed with the Do Not Disturb function... It's missing the rules feature that seems to exist in Marshmallow natively. I don't know what their motivation would be to mess with that.
So far, the ones I noticed that was gone:
- Whitepages ID
- Wireless fast charge
- Labs
vnguyen972 said:
So far, the ones I noticed that was gone:
- Whitepages ID
- Wireless fast charge
- Labs
Click to expand...
Click to collapse
I have the T-mobile phone and have Wireless Fast Charge.
kxhaz said:
I have the T-mobile phone and have Wireless Fast Charge.
Click to expand...
Click to collapse
Wow... that's weird... I live in TX and my TMobile doesn't have that option. TMobile, what the hell?
vnguyen972 said:
Wow... that's weird... I live in TX and my TMobile doesn't have that option. TMobile, what the hell?
Click to expand...
Click to collapse
Have you tried using your phone with a fast wireless charger?
blah_blah_blah_blah said:
Have you tried using your phone with a fast wireless charger?
Click to expand...
Click to collapse
No I haven't. I don't have one yet... will order one if I could confirm it works
PS: I did take on a promotion to get the Samsung wireless charger.. hopefully it will work.
vnguyen972 said:
Wow... that's weird... I live in TX and my TMobile doesn't have that option. TMobile, what the hell?
Click to expand...
Click to collapse
I also have a T-Mobile S7E and don't have that option... Very odd.
I have silver T-Mobile S7E, and I can see the fast charge toggle on the battery page. I'm a little disappointed the whitepage function has been removed. T-Mobile doesn't want to include a free service to compete with their paid caller ID feature.
dodgeboy said:
I also have a T-Mobile S7E and don't have that option... Very odd.
Click to expand...
Click to collapse
I have the fast wireless option and I don't own a fast wireless charging pad...
Hopefully a software update when the phone is officially released will solve these issues
vnguyen972 said:
No I haven't. I don't have one yet... will order one if I could confirm it works
PS: I did take on a promotion to get the Samsung wireless charger.. hopefully it will work.
Click to expand...
Click to collapse
It's happened in the past where people start freaking out because they don't see the fast wirless charging option
Once the phone uses fast wirless charging the option will appear in the settings
For some odd reason samsung made it so it only appears if you use that accessorie
vnguyen972 said:
PS: I did take on a promotion to get the Samsung wireless charger.. hopefully it will work.
Click to expand...
Click to collapse
The Samsung one they're giving out is standard charging. You can get one from Choetech off Amazon for like $20 though.
entropism said:
The Samsung one they're giving out is standard charging. You can get one from Choetech off Amazon for like $20 though.
Click to expand...
Click to collapse
I think it was closer to $30, but I got one the same day as I received the phone and can confirm, fast wireless charging works just fine.
Edit: $30 for a fancier one with a light. There is also one for about $20.
I have no wireless fast charging option or the experimental labs but I am able to search businesses in the contacts/dialer apps.
Josh H. said:
Edit: $30 for a fancier one with a light. There is also one for about $20.
Click to expand...
Click to collapse
Yep, the $20 one is pretty awesome. Big enough to hold the phone without any wobble, doesn't light up the room while you're sleeping.
I have the wireless charger from Samsung, but still no option. I got the white pages to work by just using the search in contact. When I began to search pizza a pop-up came letting me know I can search for businesses. Enabled it and it works now.
LpSk8r said:
I have the wireless charger from Samsung, but still no option. I got the white pages to work by just using the search in contact. When I began to search pizza a pop-up came letting me know I can search for businesses. Enabled it and it works now.
Click to expand...
Click to collapse
I can confirm this worked for me as well. Thanks for pointing that out.
In past version of Touchwiz Samsung has a xml file called Floatingfeatures.xml in the root of the system directory. It basically makes it easy for carriers or manufacturers to turn off certain devices as it provides simple switches to features in the smali. Im sure that this is exactly the same way and Tmobile just "turned off" the features for some reason or another. It should be really easy to turn them back on but we need root on the S7 first. My guess is that they think it makes it easier to use or something for there customers.
On a side note, i can guarantee that the reason that they turned off the white pages lookup feature is because they are trying to push there own name caller id service (or whatever its called) and they want to charge 3.99 for it. That doesnt really seem right to me but there are apps on the play store that can do things similar.
---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------
LpSk8r said:
I have the wireless charger from Samsung, but still no option. I got the white pages to work by just using the search in contact. When I began to search pizza a pop-up came letting me know I can search for businesses. Enabled it and it works now.
Click to expand...
Click to collapse
Probably should have right this first, Your right! It does work with that trick. Thanks and nice find!
Hi there. Anyone noticed that Ad Blocking for Samsung Internet 4.0 browser isn't working? The option to use an ad blocker under Setting > Advanced > Block Content is missing.
Recently bought the S7 for Verizon while my friend bought it for AT&T. I was looking for a setting to turn off the touch key backlights and could not find one. Ended up asking my friend who is on AT&T and sure enough he had a setting under display that allowed him to turn the backlight off on the touch keys. Is this a normal thing for carriers to pick and choose specific features? I know I can download and app but really??
Verizon crippled this phone. We are missing a few things, Whitepages, samsung browser, smart manager and other little settings here and there.
If you like power saver it disables the touch keys. There was an app floating around the Verizon s7 or s7 edge forums that does this.
dsmendiola said:
Verizon crippled this phone. We are missing a few things, Whitepages, samsung browser, smart manager and other little settings here and there.
Click to expand...
Click to collapse
That's amazing. I had no idea that carriers could even do that. Doesn't really make any sense because what benefit did they get out of it....oh well. Good ole Verizon
JediDru said:
If you like power saver it disables the touch keys. There was an app floating around the Verizon s7 or s7 edge forums that does this.
Click to expand...
Click to collapse
Yeah I could just turn on power saver but the phone already has an option to disable the touch key lights! Can't fathom how it would help Verizon to disable that option. Doesn't make any sense. Probably will just end up downloading an app.
neilwashere said:
That's amazing. I had no idea that carriers could even do that. Doesn't really make any sense because what benefit did they get out of it....oh well. Good ole Verizon
Click to expand...
Click to collapse
Personally I'd rather they disable a few features (though I'm not happy they did, in fact I complained to Verizon and Samsung via Twitter) then add in push advertisements for DirecTv, as AT&T did.
When they are willing to have push n first boot, what are they going to do in 3 months when you can't return the phone?
Sent from my E6683 using Tapatalk
_Dennis_ said:
Personally I'd rather they disable a few features (though I'm not happy they did, in fact I complained to Verizon and Samsung via Twitter) then add in push advertisements for DirecTv, as AT&T did.
When they are willing to have push n first boot, what are they going to do in 3 months when you can't return the phone?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Very true, those push ads were a bit outrageous. Honestly might just return this phone if the bootloader's really are locked down. At least Verizon gives you a 14 day trial period!
I have been scrolling through looking for answers, I have a s7 on att fully stocked. When I send a pic through the default app or a 3nd party ( exp: chomp, hangouts) about 2 out of 10 pics come out looking chopped in half and messed up on the receivers end. I have noticed this with people on multiple carriers and a range of different model phones receiving the pics.
Any answers? I have already hard reset it and problem continues...
Idk but this is happening to my wife's phone and it's pretty annoying.
Sent from my Nexus 6P using Tapatalk
16vMK1 said:
Idk but this is happening to my wife's phone and it's pretty annoying.
Click to expand...
Click to collapse
I know, I have done resets, different messenger apps and other things testing. I'm pretty advanced with android but even this I come up short with. I wish someone had a answer. Is your wife on att also? Does she have the new wifi calling enabled? If so sms goes out over wifi not just calls. I have noticed it with and with out wifi calling enabled. I just want to find a common variable between them. :silly:
crapymonkey2012 said:
I know, I have done resets, different messenger apps and other things testing. I'm pretty advanced with android but even this I come up short with. I wish someone had a answer. Is your wife on att also? Does she have the new wifi calling enabled? If so sms goes out over wifi not just calls. I have noticed it with and with out wifi calling enabled. I just want to find a common variable between them. :silly:
Click to expand...
Click to collapse
Yeah we are on att. I don't know if she does I'll have to check.
Sent from my Nexus 6P using Tapatalk
It's noticeably better using Allo. The pictures are so good MMS compression ruins them!
joe3681 said:
It's noticeably better using Allo. The pictures are so good MMS compression ruins them!
Click to expand...
Click to collapse
I've heard so much about the security issues in apllo, I wonder about it. Have you had any issues or concerns.
crapymonkey2012 said:
I have been scrolling through looking for answers, I have a s7 on att fully stocked. When I send a pic through the default app or a 3nd party ( exp: chomp, hangouts) about 2 out of 10 pics come out looking chopped in half and messed up on the receivers end. I have noticed this with people on multiple carriers and a range of different model phones receiving the pics.
Any answers? I have already hard reset it and problem continues...
Click to expand...
Click to collapse
When att released the advanced messaging feature. I've had this issue, I would get chopped pictures or none at all (failed to download). After disabling the advanced messaging feature. I haven't had this issue.
Sent from my SAMSUNG-SM-G930A using XDA-Developers mobile app
crapymonkey2012 said:
I've heard so much about the security issues in apllo, I wonder about it. Have you had any issues or concerns.
Click to expand...
Click to collapse
Not really but we don't use it for anything serious. There's always incognito mode that offers encryption.
nahrah said:
When att released the advanced messaging feature. I've had this issue, I would get chopped pictures or none at all (failed to download). After disabling the advanced messaging feature. I haven't had this issue.
Click to expand...
Click to collapse
I did for a few days use the advanced messengers that att released. But I've been using chomp and other also.
joe3681 said:
Not really but we don't use it for anything serious. There's always incognito mode that offers encryption.
Click to expand...
Click to collapse
I remember reading a article that was released soon after allo was, that the fbi warned about the security of allo.
crapymonkey2012 said:
I remember reading a article that was released soon after allo was, that the fbi warned about the security of allo.
Click to expand...
Click to collapse
Actually Snowden did. Because there's no real ecryption. Again, unless you use Incognito mode.
joe3681 said:
Actually Snowden did. Because there's no real ecryption. Again, unless you use Incognito mode.
Click to expand...
Click to collapse
It may have been, I didn't think it was him. Wish I would have saved that article.