The Xperia Arc has built-in SIP VOIP support and apparently so does the Nexus S with Gingerbread. So I'm wondering if that's standard in Gingerbread and/or if it will be a feature that the sgs2 will have as well?
Anyone know?
It's a standard feature in Gingerbread because the Nexus S is completely stock Gingerbread and it still has the feature. Manufacturers may choose to disable that function however, so watch out for that.
Certainly Carriers will add their bloatware and remove this feature.
Fortunately, I'll be getting mine unlocked and without bloatware so hopefully it will be a feature that's still intact.
Just got our answer on this one from the ever-so-helpful Dom.
http://forum.xda-developers.com/showpost.php?p=13174479&postcount=173
The only thing I can imagine is that Samsung wants to make the SGSII as operator-friendly as possible, but honestly, with this feature in the likes of the Nexus S and the Xperia Arc, it doesn't appear to be hurting their operator sales.
With that in mind, it's just kind of rediculous that Samsung wouldn't provide native Internet calling support in the SGSII, but apparently that's what they've done.
Guess it's back to the Sipdroid battery hog while we wait for cooked roms to put Internet calling back into the regular phone app.
Related
ASUS has touted Wi-Fi Direct http://www.asus.com/News/k4PosV90YN1qdjZ3/ as one of the features present on the Transformer Prime. For those of you who are not familiar, Wi-Fi Direct is basically a means of establishing an ad-hoc Wi-Fi connection without the need for a router or one device acting as a hotspot and was just introduced into Android 4.0.
I've had the chance to use it on multiple occasions, transferring huge files between two Galaxy S II devices and all I can say is the speed is much, MUCH faster than Bluetooth, such that transferring 2GB can be done within a reasonable time frame like that of a meal. Also, it doesn't consume anywhere near as much battery as using one device as a hotspot and then transferring files between them.
So my question is, has anyone found a way to access the WiFi Direct functionality we all supposedly have on our Transformer Primes? Given the spottiness of MTP/PTP, having another reasonably fast way to get files on/off the device can only make things better!
Source: android.com
Support for Wi-Fi Direct lets you connect directly to nearby peer devices over Wi-Fi, for more reliable, higher-speed communication. No internet connection or tethering is needed. Through third-party apps, you can connect to compatible devices to take advantage of new features such as instant sharing of files, photos, or other media; streaming video or audio from another device; or connecting to compatible printers or other devices.
Click to expand...
Click to collapse
application is needed
Thanks! Did a search of the market, seems no apps implement that functionality yet...
ong.andrew said:
Thanks! Did a search of the market, seems no apps implement that functionality yet...
Click to expand...
Click to collapse
yea, i've been really excited about this, but google doesn't seem to have it finalized yet from what i understand. It will make printing about 50x easier in the workplace since chrome is not commonplace and chrome is required for cloudprint
So is this why we don't have an option in our settings as opposed to the Galaxy SII?
You don't need any App.
WiFi-Direct technology is implemented in ICS 4.0 and aboce.
whne the Prime will get ICS update it will support it. in any context menu.
it would be like sending via bluetooth.
I guess ASUS ment that te Prime's wifi chip DOES suppot that. but the software need too. and Gingerbread dosen't.
On the Galaxy S2 it's the same thing. only Samsunge made special apps for themselfs and that was build in the system (in the TouchWiz). No other 3-rd party project can access that thing and build other Apps. Only when the Galaxy wil have ICS update. exaclly like here....
Good luck...
Here are some resources regarding "wifi direct":
http://developer.android.com/resources/samples/WiFiDirectDemo/index.html
zaxy78 said:
You don't need any App.
WiFi-Direct technology is implemented in ICS 4.0 and aboce.
whne the Prime will get ICS update it will support it. in any context menu.
it would be like sending via bluetooth.
Click to expand...
Click to collapse
This is actually not true. I own the Galaxy Nexus and currently there is no way to actually use WiFi Direct without an app. Even the core Android apps don't make use of it. Pretty useless feature up until Google or the developers start releasing apps that make use of it.
So just hoping you guys could clear this up for me.
As far as I know, S-beam replaced android beam as the NFC app on the gs3. Form everything I've heard, s-beam can only communicate with another s-beam enabled device, which right now means only the gs3. However I have no proof of this, either way.
So, that said, here are my questions.
1) if you 'bump' a gnex and a gs3, will android beam and s-beam communicate?
2) if not, is there any way to get a-beam working on the gs3, for better compatibility?
3) would it be worth the effort (or even possible) to try to get s-beam onto other nfc enabled devices? It seems to have more features than A-beam, so if A-beam and s-beam are compatible, it would be seen as an upgrade, and if they're not compatible, it would still be useful, as a way to communicate with s-beam enabled devices.
Thanks in advance for your answers!
S Beam supplements Android Beam, it doesn't replace it. There are two separate options in the menu (see attachment).
As for porting, S Beam obviously implements certain authentication and security features. But it might still be possible to port. It might not even be worth it: the only other person I know with an S3 is my dad and he's thousands of kilometres away so I can't say how well S Beam works.
Your first two questions are obviously moot.
But I also got the impression before that S Beam replaced Android Beam, so don't feel bad anyway.
Thank you for clearing that up!
The reason I asked if it would be possible/worth it to port is twofold. One, because the US is soon going to get a huge amount of GS3s, and the other, because nfc-based wifi direct is a feature that I would use daily if I had it on both my phone and tablet.
i tried android beam 2.0 (jelly bean on my nexus) with the galaxy s3 s beam. I tried to sent a image and only get text on my display like ".../galleryshare" with an OK button but no file.
not very sucessfull
I have a generic tablet which has Android 4.0.3 stock-installed. I can use the 3G feature without a problem; but when it comes to make voice calls; here's what happens:
1- eXdialer: When the calling button is pressed, nothing happens but the screen refreshes only.
2- DialOne: Prints out the warning on the thread subject: "Telephony feature is unavailable on this device"
The producer company claims that Xphone dialer works on this device; but it looks like some hardware-lock or similar?
Since the mentioned software is not free, I could not test if it works.
Hint: The devices are imported to our country as "it has no telephony feature" on the formal papers, just because of the higher taxes on telephony enabled devices. Previous products of the same company were similarly software-locked and they soon released a new rom that enabled the telephony feature. Now there is no any modified rom for this device.
Any ideas are welcome.
Waiting for somebody to say "xda-dev forum is not a right place for you, ugly duckling"; after all.
To put it in another way, Samsung Galaxy Camera also don't have the Telephony feature even if it does have 3G. So its pretty much they've removed the standard dialer app and the resources/lib associated with it. But by installing the missing things, it could be do-able though, I guess.
That is what I also think; but the damn thing I don't know is: HOW?
I thought I'd start a thread to post the top (best) things to do with your AT&T HOX+ on a stock ROM.
Unlock Bootloader, Install CWM Recovery & Root
In order to be able to do many of things listed here, you will need to have root access to your phone. Follow the following thread to unlock and root your phone. By unlocking your bootloader, you'll be able to install custom ROMS down the road if/and when you want.
How-To Thread - Credit goes to hasoon2000
Disable AT&T Crap-ware
The one and only time I'll give kudos to Apple is that they don't let the carriers load up their phones with preinstalled crap-ware. Sadly, not the case with Android. So, you're left with manually having to disable them. Luckily you only need to it once.
Below is the list of Apps to disable (unless you actually want to use any). Simply go the Settings > Apps > All and select Disable for each app.
AT&T Code Scanner
AT&T Family Map
AT&T Hot Spots
AT&T Locker
AT&T Messages
AT&T Navigator
AT&T Ready2Go
Device Help
Facebook (sorry, Google+ user)
Internet (if you use Chrome only)
Live TV
ME Infiltrator
NOOK
YPmobile
Enable Tether (on AT&T)
Obviously you should have a legit tethering plan with AT&T [chuckle], but you can easily bypass their check and enable it on your HOX+ utilizing the stock wifi tethering app (no need for 3rd party apps).
How-To Thread - Credit goes to 911jason
Disable AT&T ANNOYING Boot Animation
The AT&T boot animation is just annoying, loud and obnoxious. With this little tweak, you can disable it and just have the HTC stock boot animation enabled.
How-To Thread - Credit goes to sixcarnage
Disable Automatic AT&T WiFi Hotspot
Nothing annoys me more than being close to a Starbucks (or any AT&T Hotspot locations) and being forced to connect to their WiFi, only to get crap to zero connection and then having to disable WiFi on your phone and forgetting to turn it back on later. URGH. Not to mention LTE is blazing fast in comparison.
How-To Thread - Credit goes to spyz88
Use Google Voice for Voicemail
Whether you use Google Voice all the time or not, you can have your phone use its VM option instead of AT&T's. I prefer it because I have an easy archive of all my VMs, easier access from anywhere, and obviously having them transcribed for me.
Normally you can select your VM carrier through the Google Voice app on your phone, but obviously AT&T blocks this. Instead, all you have to do is dial the following:
Activate:**004*1XXXXXXXXXX#, where is Xs represent your 10-digit Google Voice number
Deactivate: ##004#
Replace Default Keypress Sounds
The stock HTC keyboard is decent, but fails horribly at swipe predictions and is very limiting. You have many options out there for 3rd party keyboards, and of course the stock Android JB 4.2 keyboard with swipe. For me, I found Swype Beta to be the best in terms of layout, swipe predictions and other cool little features.
The problem with Swype (or stock Android 4.2 keyboard) is that it uses the keypress sounds found under /media/ui which HTC never bothered to update from the days of Android 2.0. Needless to say they're horrid.
If you find yourself wanting to use either of these keyboards, you can easily extract the keypress sounds from the HTC keyboard APK and use them instead by copying them over to /media/ui.
What you'll notice is that Swype doesn't have a volume control for the keypress sounds, and they're set to UBER high. What I did is take the sounds from the HTC keyboard APK and then used Audacity to reduce the gain by -13 and that gives you a perfect level.
For Swiftkey fans, unfortunately the keypress sounds are stored inside of their APK, it doesn't use the system default.
I didn't post the sounds because I presume they're copyrighted by HTC, so you'll need to get them yourself...very easy.
-----------------------------------------
Got More?
Please add any other useful tweaks that I might have missed (or that I...or others...don't know about). Just keep in mind two things:
Tweaks must work on HOX+ STOCK AT&T ROM
and…tweaks only, no apps
.
I see the issue come up frequently on various forums on the 'net, people with Atrix 4G's that have a lot of trouble getting their sms/txt messaging to work with car on-board systems, like Ford Sync, BMW's System, and Mazda's Bose/Navigation system, etc etc.
The systems in question support SMS/txt messaging via Bluetooth (PBAP and MAP) from various smartphones. Hardware-wise, the Atrix 4G is compatible. BT specs say it should work as well. The systems should download any texts that show up, display or read them back to you, and show you the sender/#.
I've been experimenting on both my Atrix 4G's, and it seems any blur-based ROM has a poorly/improperly implemented bluetooth stack, or possibly an incorrectly configured messaging db. I have tried regular unmodified fruitcakes for .91, .141, and 145. on both phones in several different cars.
* .91 completely fails, will not upload messages/sender at all.
* .141 and 145. will allow message uploads, but cannot upload sender properly (always comes back as 'null' on cars display ). It should be noted, that both can be temperamental downloading messaging on rare occasion.
I have also tried the .141 based Nottachtrix ROM, and the .145 based Laytveyit ELITE ROM. Both has same issues and the OEM style fruitcakes.
To further test the theory, I installed CM7. It works perfectly will all the mentioned car systems, no issues, never misses sender or message info.
At this point, I dont even know if the blur-based ROM's are fixable, but for sure in their current state the BT messaging is kind of useless. Doesnt do much good if everything that comes in is from 'null', i.e. cant tell who its really from while your driving. I have heard of some people getting these to work sometimes, but I sure couldnt.
Despite going over log-cat info during BT events, I wasnt able to pinpoint anything obvious. But that may just be me not recognizing something.
Hopefully that may give some relief to anyone whos' been frustrated by the poor (or lack of) functionality with BT messaging.
For myself, I'm using CM7 as my daily ROM now. Unfortunately it doesnt support webtop, so I keep a backup of CM7, and a Nottachtrix 2.1 build I setup, on my external SD so I can switch between them if I need to use my lapdock.
Kinda sucks, but thats pretty much what I expect from Motorola these days.... Crappy software... broken promises.
If any development/programmer type guys have any idea on the 'null' sender upload, I'm all ears.
K