Now that theres a 2.3 rom for the Galaxy S, basically the same hardware as NS, can we use their browser.apk to enable hardware acceleration? or is it more involved than that, other drivers etc?
If I'm not entirely mistaken, it requires the TouchWiz framework, so no, probably not.
Related
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
I post this here, as I can't post in development section.
Well, I downloaded the kernel sources for ChaCha in htcdev.com and I have some questions.
Why there is the source for drivers of hardware the ChaCha doesn't have?
Can the real hardware be guessed from the modules/drivers used in a kernel? Can we know that from the sources?
Can a different flavor of unix (maemo, tizen, webos, debian...) installed on ChaCha by compiling the right kernel? Will bootloader support that?
I come from a N900 where all this things were possible, up to the extents were open source drivers could be used. There is a site where up to the tiniest piece of hardware is identified with the N900.
If exists such a list of hardware of the ChaCha, maybe much better things could be done with the machine itself, even (maybe) 'port' things that other phones with the same or similar hardware does and ChaCha doesn't.
People that hacked the N900 (again) could get it to record videos up to 720p, wihch the N900 didn't support, and even run many games of the Palm Pre, that had almost the same hardware as N900.
Thanks all for reading this.
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.
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