Nothing new, just refresh design (even worse and iphonisher) and offical HDMI out support.
Hoppin service is similar to Media Hub + apple's seamless playback between devices. When you sync your phone to PC or HDTV, they continue playing media that phone did.
FYI, M110S was initial Galaxy S, and M130L was CDMA + OneNand (like fascinate)
I've read that this phone will be released running 2.2. Their froyo habits seem a little off to me.
any custom rom or ics update on this phone?
Related
A new skype version is available today on the market. It enables more phones/tablets. Nevertheless the Transformer is not yet supported.
cause it's a tegra2 device
any chance we will get video on skype for android?
salam0506 said:
any chance we will get video on skype for android?
Click to expand...
Click to collapse
yes, it is already the case for "selected" devices. At least thoses
Samsung Google Nexus S
Samsung Galaxy S II
Samsung Galaxy S
Samsung Droid Charge – Verizon
Samsung Galaxy Tab
HTC Desire (2.2)
HTC Thunderbolt – Verizon
HTC Sensation
HTC Evo 4G
HTC Evo 3D
HTC Incredible S
HTC Desire HD
HTC Flyer
HTC Desire S
LG Revolution – Verizon (2.2)
Sony Ericsson Xperia PLAY
Sony Ericsson Xperia ray
Sony Ericsson Xperia mini pro
Sony Ericsson Xperia neo
Sony Ericsson Xperia pro
Acer A5
Tablets that are available are 7" running gingerbread... Samsung Tab and HTC Flyer.
We'll just have to wait...
wow i didnt realise skype was just being biased against the TF - i hope they don't overlook it!
eagerly waiting for skype to work on my transformer....
aarif_ziaee said:
eagerly waiting for skype to work on my transformer....
Click to expand...
Click to collapse
Me too. Also I want the ability to send and recieve files.
According to
http://blogs.skype.com/en/2011/08/skype_21_for_android.html
Is your device not on the list? No need to worry...
For those of you using Android 2.2 (Froyo) and above, you should still be able to enable video calling in your Skype settings. Just go to "Skype settings" after launching the app and select "enable video calling".
Unfortunately, if you cannot see the video calling settings, it means your Android phone does not meet the minimum requirements needed to make Skype video calls. Please be aware that video call quality may not be as good as on a certified Android device and only the back camera of the device will work if your device is running on Android 2.2 (Froyo).
Click to expand...
Click to collapse
Not sure how transformer can not meet the min requirements.
maybe it's so cause our transformers are tegra2 devices
TheSgrash said:
maybe it's so cause our transformers are tegra2 devices
Click to expand...
Click to collapse
Samsung Galaxy S2 IS a tegra2 mobile phone device, just not a tablet device? and sadly drivers are 2.3.4 based, which again means that 2.3 gingerbread drivers are probably not 3.x compatible anyways..
very sad..
edit: i was wrong, it seems!!
It is now working on my MT4G. It has an option in settings to enable video call. That option does not appear on TF. On mobile I got a very good videpo quality. Since Microsoft took over Skype, things are finally moving. Perhaps tablets are next.
Skickat från min ASUS Eee Pad TF101
Sick and tired of Skype's ****ed up bull****, our Eee Pads can MORE then handle video calling and tegra2 phones use it, its just bull**** plain and simple. They play ****ing games (remember Fring). And no one at Skype will give a straight answer and they have no contact line, emails go unanswered, I assume they simply dont give a **** like most other tech companies these days (can you say dell tech support line? I knew you could).
I'm pretty sure Skype has a reason. It's a business. It wants to make money. It is going to do what ever is most profitable. If you don't like it, start your own VoIP company, convince the majority of the world to use it, then develop an app for every device/OS out there. I'm pretty sure you'll find it's hard to make everyone happy.
With that said, I too look forward to having Skype video chat on the Transformer.
salam0506 said:
any chance we will get video on skype for android?
Click to expand...
Click to collapse
Here is the response from Tech support:
"We understand your concern about the availability of video calling on your ASUS Transformer. We will be happy to assist you with this.
Steve, we are working on adding more Android devices all the time, but we are not able to provide you with an exact time frame for when your device may be supported.
To make Skype video calls on Android device, you will need:
An Android phone running Android 2.2 (Froyo) or above. Front facing camera. Chipset with NEON technology support*. The latest version of Skype for Android (Skype 2.1 for Android and above).
* This specifically does not include some tablets that use the Tegra 2 chipset (e.g. Android tablets and Motorola"
There was this topic:
http://forum.xda-developers.com/showthread.php?t=1206326
But this:
https://market.android.com/details?id=com.dancingpixelstudios.sixaxiscompatibilitychecker
Says it's incompatible with the Infuse 4G.
This is just the checker, and I would assume that you could at least download the checker to see if it's compatible... or is the fact you CAN'T download it the check itself? Strange~
Also, this is kind of a +1 for adding PS3 Controller compatibility, or if anyone knows of an alternative for the Infuse 4G.
I hope it works,it would be cool
Not compatible with ANY GalaxyS (or similar) phone. Also not compatible with any HTC Sense phone.
Both Samsung and HTC break the Bluetooth stack in the official firmwares. In fact the general rule (with the Galaxy Tab 10.1 being the only exception) is: If it runs Sense or TouchWiz, it won't work.
Cyanogenmod ports have a fully functional Bluetooth stack (when they have one that works at all - Bluetooth is completely missing from LinuxBozo's CM7 port so far)
I have not yet seen an example of someone "un-breaking" the Bluetooth stack in a stock-based firmware - only in full-blown AOSP/Cyanogenmod ports.
Entropy512 said:
Not compatible with ANY GalaxyS (or similar) phone. Also not compatible with any HTC Sense phone.
Both Samsung and HTC break the Bluetooth stack in the official firmwares. In fact the general rule (with the Galaxy Tab 10.1 being the only exception) is: If it runs Sense or TouchWiz, it won't work.
Cyanogenmod ports have a fully functional Bluetooth stack (when they have one that works at all - Bluetooth is completely missing from LinuxBozo's CM7 port so far)
I have not yet seen an example of someone "un-breaking" the Bluetooth stack in a stock-based firmware - only in full-blown AOSP/Cyanogenmod ports.
Click to expand...
Click to collapse
Wish it was as simple as taking a folder called "Bluetooth" from one phone and just slapping it into the Infuse. Oh well, patience then.
I'm new to Xoom. I use Samsung Galaxy S2, where if you use a non-stock ROM like Cyanogenmod, you lose hardware decoding support for many video codecs. That's the reason I always use stock-based ROMs on my phone.
I flashed Team EOS ICS rom on my Xoom almost as soon as I brought it home, and I love it. However, I wonder if I lost any hardware video decoding support compared to stock. Any help?
After using both stock and TEOS, I haven't noticed any huge difference between the two in video playback, or at least what I use of them.
If you really wanted to try it out, you can always flash your XOOM back to stock using the images that Motorola supplies, then update to ICS if required, then see if anything is missing. I haven't personally done this myself, but in theory it should work.
The xoom uses hardware accelerated decoding supported by nvidia firmware. In that context, decoding is identical.
This might not be specific to this phone, since most Samsung phones don't have the ability to do this by default, but maybe it is.
My first Android phone was a Nexus One. Loved the phone, but after about 2 years, it died on me. I was ok with it too, as I was on AT&T and the data speeds were always SLOOOOOW.
Anyways, I have this phone now, and I do miss using a bluetooth gamepad to play snes roms. I tried using the bluetooth input app from the market (the one made by CCP or whomever) and naturally I get the, "This will not work on most unmodified Samsung phones" error message.
While part of me kinda wanted to buy the Galaxy Nexus, which I knew would work with this without any problem, the phone is just too large for me.
If you've rooted your Blaze and taken out some of the apps, have you ever tried to use a bluetooth gamepad (such as a wiimote, which is esentially what I'm using, since I have a Datel gamepad that is basically a wiimote built in) or the newer method which of course is a Sony PS3 controller, that is paired via a connecting cable?
I'm not sure specifically why most of the branded phones don't work with this, all I know is that supposedly the Sense UI phones don't have the proper bluetooth license in their chip so it never worked, I don't know if that was true though, and if it's also true for Samsung's Touchwiz.
I look forward to the day when there are stock ICS rom's that work with our phone available! Until then, I'll use what I have.
Thanks!
If anyone else is wondering, I rooted the phone a couple days ago, and yes, it does. I have not yet personally used the wiipad setup because I don't have any AA batteries currently, but https://play.google.com/store/search?q=sixaxis+controller&c=apps works very well. It connects with "type 2" which means that it has to disable all other bluetooth devices so you can't use a set of bluetooth headphones to listen to music or talk while you are playing a rom, but oh well.
Hi
I just purchased the Samsung BD-FM59C bluray player from Costco for $120. The player supports AllShare Cast and Miracast.
I tired it out a display version at Costco (they hooked up the display to a tv and let me play with it). I went to the screen mirroring option and it said to connect my "Allshare Cast or Miracast device" and I was able to successfully mirror with my Nexus 4 (CM 10.1 Linaro nightly). Satisfied, I bought it.
I went home and updated the firmware (v1003 to v1007). Now it no longer mentions Miracast on the Screen Mirroring option and my Nexus 4 never connects.
Anyone have experience with mirroring on this model? Any other ROMs work better with Miracast? Also if you are interested in this player for mirroring, maybe hold off on updating the firmware.
Update: Stock rooted T-Mobile Samsung Galaxy S III does not work either with Allshare Cast. It connects then quickly disconnects without mirroring. So it seems to be a bad update. Or I possibly have a lemon.
Does anyone have this model or the new Panasonic models (BDT230 AND BDT330) with Miracast? I'm looking for a decent bluray player with Miracast, DLNA, and Amazon Instant Video. So far, these players seem to be the only ones that do this at least at a reasonable price
ralphwiggum1 said:
Hi
I just purchased the Samsung BD-FM59C bluray player from Costco for $120. The player supports AllShare Cast and Miracast.
I tired it out a display version at Costco (they hooked up the display to a tv and let me play with it). I went to the screen mirroring option and it said to connect my "Allshare Cast or Miracast device" and I was able to successfully mirror with my Nexus 4 (CM 10.1 Linaro nightly). Satisfied, I bought it.
I went home and updated the firmware (v1003 to v1007). Now it no longer mentions Miracast on the Screen Mirroring option and my Nexus 4 never connects.
Anyone have experience with mirroring on this model? Any other ROMs work better with Miracast? Also if you are interested in this player for mirroring, maybe hold off on updating the firmware.
Click to expand...
Click to collapse
We also just got the Samsung BD-F5900 bluray player. Although I did try to do mirroring with my Galaxy s3 before it self-updated (also from v1003 to v1007). Before the update it mentioned Miracast and after it did not. However, I haven't gotten it to work before or after the firmware update. I am speaking with Samsung now to get it resolved and they told me they would call me back in a day or two.
Can you go back to Costco and see what version they are running in the store? If it is working with the older version, you could reset your device back to the stock device and disable software updates form inside settings. Or, perhaps Costco would work with you on setting up your system mirroring with your phone, in their store?
KitzyKitt said:
We also just got the Samsung BD-F5900 bluray player. Although I did try to do mirroring with my Galaxy s3 before it self-updated (also from v1003 to v1007). Before the update it mentioned Miracast and after it did not. However, I haven't gotten it to work before or after the firmware update. I am speaking with Samsung now to get it resolved and they told me they would call me back in a day or two.
Can you go back to Costco and see what version they are running in the store? If it is working with the older version, you could reset your device back to the stock device and disable software updates form inside settings. Or, perhaps Costco would work with you on setting up your system mirroring with your phone, in their store?
Click to expand...
Click to collapse
I've been looking into it more. And contacting Samsung Support, with no resolution so far.
I'm assuming Costco was running v1003, since it was the version mines came out of the box. They just had the blu-ray sitting with the price tag and it wasn't connected to anything. I asked them to plug it into a TV and they did and they grabbed the remote for it. The blu-ray player at the store wasn't ever connected to the internet and I was able to Miracast with my Nexus 4. I would downgrade back to v1003, if I could, but I don't think the player would allow me to even if I could somehow find the firmware file on the internet.
The player at home, I updated immediately to v1007. And it no longer worked with my Nexus 4 (and removed reference to Miracast).
For Allshare Cast device (GS3), it looks like people are having issues with the Allshare Cast Hub dongle (that costs $100) and rooted devices, such as in this thread: http://forum.xda-developers.com/showthread.php?t=2089479. Since you could never use the mirroring, I wonder if it's because of rooted / flash counter status?
After more attempts, I was able to use Screen Mirroring with my Nexus 4 on the v1007 firmware. It took many connecting disconnecting some restarting but it finally connected and paired and I was able to start mirroring. Again this is on the CM 10.1 Linaro nightly, so it could be something related to the ROM making it difficult to start mirroring.
Ironically, still no luck mirroring with Allshare Cast on stock rooted Galaxy S III...possibly related to root status.
v1007 is ok?
realpg said:
v1007 is ok?
Click to expand...
Click to collapse
It looks like it. It took many efforts to get it I tried again after, and it did not connect again smoothly, so it seems tempermental, at least for me. But it all in all, it does work with Miracast on Nexus 4...eventually. There is about 1-2 second delay in the mirroring, so fast-paced gaming is not ideal.
ralphwiggum1 said:
Update: Stock rooted T-Mobile Samsung Galaxy S III does not work either with Allshare Cast. It connects then quickly disconnects without mirroring. So it seems to be a bad update. Or I possibly have a lemon.
Does anyone have this model or the new Panasonic models (BDT230 AND BDT330) with Miracast? I'm looking for a decent bluray player with Miracast, DLNA, and Amazon Instant Video. So far, these players seem to be the only ones that do this at least at a reasonable price
Click to expand...
Click to collapse
I just got the BDT-330 specifically for the Miracast feature. It does work, however it's not really ready for prime-time. DLNA works pretty well, though but not with the default Windows dlna server in Windows 7. I downloaded Serviio and it works really well.
ralphwiggum1 said:
I've been looking into it more. And contacting Samsung Support, with no resolution so far.
I'm assuming Costco was running v1003, since it was the version mines came out of the box. They just had the blu-ray sitting with the price tag and it wasn't connected to anything. I asked them to plug it into a TV and they did and they grabbed the remote for it. The blu-ray player at the store wasn't ever connected to the internet and I was able to Miracast with my Nexus 4. I would downgrade back to v1003, if I could, but I don't think the player would allow me to even if I could somehow find the firmware file on the internet.
The player at home, I updated immediately to v1007. And it no longer worked with my Nexus 4 (and removed reference to Miracast).
For Allshare Cast device (GS3), it looks like people are having issues with the Allshare Cast Hub dongle (that costs $100) and rooted devices, such as in this thread: http://forum.xda-developers.com/showthread.php?t=2089479. Since you could never use the mirroring, I wonder if it's because of rooted / flash counter status?
Click to expand...
Click to collapse
ralphwiggum1 said:
After more attempts, I was able to use Screen Mirroring with my Nexus 4 on the v1007 firmware. It took many connecting disconnecting some restarting but it finally connected and paired and I was able to start mirroring. Again this is on the CM 10.1 Linaro nightly, so it could be something related to the ROM making it difficult to start mirroring.
Ironically, still no luck mirroring with Allshare Cast on stock rooted Galaxy S III...possibly related to root status.
Click to expand...
Click to collapse
realpg said:
v1007 is ok?
Click to expand...
Click to collapse
Today t-mobile pushed an update for the Samsung S3, we now have Android 4.1.2 and allshare cast works as expected. My phone hasn't been rooted, so I've never messed with the flash counter status.
My blu-ray player also has the v1007 firmware. It connected on the first try this afternoon.
I have the same BD-FM59C player with 1008 firmware (before that it had 1007) and it NEVER worked with my stock Nexus 4. Not only that but the player itself (forget about miracast) sucks sucks sucks. I'm taking it back to costco. Sony is by far the best in similar low cost players
larryvand said:
I have the same BD-FM59C player with 1008 firmware (before that it had 1007) and it NEVER worked with my stock Nexus 4. Not only that but the player itself (forget about miracast) sucks sucks sucks. I'm taking it back to costco. Sony is by far the best in similar low cost players
Click to expand...
Click to collapse
It looks like stock may not work on Nexus 4. Not sure if it's related to software or even TV, but I only got it to work CM 10.1 with the HDCP off option enabled. I'm running Paranoid Android on the Nexus 4 and it's doing what my GS3 did where it would connect then disconnect.
I tried fully stock GS3 and it did not work either but Kitzy said it works w latest GS3 update from T-Mobile.
Maybe the common problem with All share Cast and Miracast failing is HDCP related?
Also I did like Sony's player (I had the S590) for usability since it allowed more apps to use keyboard/mouse and had better navigation, but it also had a lot of problems with DLNA. This Samsung has its problems with being too Samsung centric (the remote only works with Samsung TV's and isn't universal!) and horrible navigation but it also has a lot more features. Such as good YouTube app (with YouTube Tv support from mobile), better web browser, miracast (which may or may not work) and better DLNA support. It's even better for DLNA by using bubbleUPNP and screen mirroring also works with Intel WiDi. So I think it's the better bang for the buck right now.