So, like the title says, does Nexus S have Wifi-Direct compatible hardware? Wifi-Direct does not show up in the settings on my NS. Some people have reported to have it though. Is it that they in fact have the 4G model, which has it? Or is it because my ROM / kernel does not support it? I am running CyanogenMod 9.0.0-RC0 v3.4.
i am not sure about it, but older motorola with gingerbread had it, so it is either a HW limitation of samsung vs. motorola, or motorola just implemented it in its bloatware roms
Related
I think the question does not need any more explanations.
Maybe someone that has the transformer can check this...
I highly doubt it.
I very much doubt it with the Asus stock ROM but I would hazard a guess and say that this may be possible with custom ROMs. It wouldn't make sense for Asus to support this as they will be selling a 3G version so it would be detrimental to their sales strategy.
I tested some "No name" android 2.1 / 2.2 tablets with stock kernel and the 3G dongle was recognized and more, GSM signal was displayed.
I see that a 3G modem is detected on Xoom, but no one tested this to the end.
http://forum.xda-developers.com/showpost.php?p=13012142&postcount=3
vipergrm said:
It wouldn't make sense for Asus to support this as they will be selling a 3G version so it would be detrimental to their sales strategy.
Click to expand...
Click to collapse
Why not? Why would Asus care if you buy 3G or WiFi version as long as you buy one of them?
Magnesus said:
Why not? Why would Asus care if you buy 3G or WiFi version as long as you buy one of them?
Click to expand...
Click to collapse
I'd imagine that Asus wouldn't care but any carrier they have a deal with to push the tablet might have issue with it.
It is hit or miss with tablets from what I'm aware of. I don't think it worked with the gtablet out of the box.
I can't imagine drivers and software for Honeycomb to support those USB 3g dongles...
I can imagine getting a Mifi or similar mobile wifi hotspot though and using it with the TF and other devices.
bcostea said:
I tested some "No name" android 2.1 / 2.2 tablets with stock kernel and the 3G dongle was recognized and more, GSM signal was displayed.
I see that a 3G modem is detected on Xoom, but no one tested this to the end.
http://forum.xda-developers.com/showpost.php?p=13012142&postcount=3
Click to expand...
Click to collapse
its very easy to figure out, if you're a developer, and you check the /proc/config.gz you know if its compiled with support for 3G dongle and which (huawai works 99% and a few others and some which not even yet has linux drivers ready)
so that will confirm, that xoom probably have no stock kernel support, and same goes for asus pad here...
On Folio100 we had to re-compile the kernel and re-write special pppoe drivers to make it work..(DerArtem made all this)
your reference tablet from china was a special edition, that they made drivers fror and a kernel with support for it.. and its was indeed 2.1...
most other chinatab's did not have 3g simslot or support..(stock does not mean android stock, but company default chosen kernel which can be with alot of functionality, or none at all, stripped to do what is needed and nothing more)
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 have a Galaxy S2 which seems to share the same chipset as the GT 7+.
I've just ordered a tab7+ and as there is a massive amount of roms available for the S2, including ICS. Would the binaries for the S2 help make an ICS rom for the GT7+?
Binaries? No - completely different screen, very different peripherals, and no Honeycomb for the Tab 7. Even when both have ICS, they will be very different builds.
Kernel source? Due to being 2.6.36.x, the Honeycomb source base for your kernels has differences from the S2 codebase - so a lot of stuff can't be directly applied, but a competent developer (you have one with garyd9) can apply the "concepts" in many cases.
Unfortunately, Samsung screwed up the wifi driver in the 7 Plus. It's binary-only (no source code) and it seems to have bugs.
Entropy512 said:
Kernel source? Due to being 2.6.36.x, the Honeycomb source base for your kernels has differences from the S2 codebase - so a lot of stuff can't be directly applied, but a competent developer (you have one with garyd9) can apply the "concepts" in many cases.
Click to expand...
Click to collapse
I don't think there are any kernel mods I'd want to bring over from that device. As far as what the OP called "ROMs", I have no idea what they are referring to. There doesn't seem to be any read-only memory in the tablet.
If he meant "firmware", then I have to admit that I'd prefer not to do that kind of thing. There are many different kinds of developers in the world... some get off working at the lowest possible level (kernels, etc) and others prefer higher level things. I'm the former, and it would take the latter to do firmware development.
Gary
Hi,
Dianxin Hybrid 4.0.4 maybe could include DAC support? Just saw "android engineering" and got a bit hopeful. I see that some roms for the Samsung Galaxy devices now have DAC support hacked into them, could we get this for our HTC's to?
Thanks for any reply that might come
Device: Xoom LTE MZ602 [STINGRAY]
ROM: OmniROM 4.4.4
Problem: No support/function for video calling and some other apps
Attempted resolution: Read below
So it seems that Android no longer supports the Tegra2 after 4.1.2 due to not having the NEON instructions set. I am currently running OmniROM 4.4.4 and am unable to get certain apps that I presume require NEON support.
The thing is, even attempting to use older versions of apps, Duo for instance (which originally supported 4.1), does not work. I believe that there are non-NEON hardware libraries that are not compiled into 4.4.4 ROMs available for the Xoom. Not sure what would be required to provide full compatibility.
OmniROM for this Acer device (https://forum.xda-developers.com/showthread.php?t=2705989) claims to have support for Tegra2. I have previously tried to place the non-NEON libraries from a 4.1.2 Xoom ROM into the one I'm using to no success (I'm no developer). I'm guessing the ROM either needs to have these baked in or there are other dependencies that are less obvious.
I just want apps like Messenger and Duo to work for video calling. At this point, I may just go to 4.1.2 even though I don't want to.
Thanks
You might as well just roll back. Its sad how bad tegra2 support is, but I guess thats what we get for using a motorola xoom in 2018. I for one am not giving up, this tablet is ****ing awesome, I am definitely getting a Xoom 2 Next.
Well I rolled back to 4.1.2 stock ROM w/ root. Still have the same issues with the app functionality. I will say it seems JB runs smoother than KK. Even Chrome Beta still doesn’t work. It doesn’t even open.