Can We Have Wifi Direct Feature??? - Huawei Ideos X6

Hi,
Request To All The Dev Working On Ideos X6
Can You Let me Know If There Is Any Possibility OF Having Wifi Direct Feature On Our Phone
more here:
http://www.engadget.com/2010/11/03/samsung-galaxy-s-first-smartphone-to-be-wi-fi-direct-certified/
It Will be Better than Bluetooth For Big File Transfers

there are only two devices in the market with this feature atm. lg optimus black & sgs2. sgs 1 don't have it..
i have sgs2, but not other phone to use wifi direct with it..
hope we can have it too.. but will have to wait till official or a custom ics rom as base for a easy porting.. as current android library don't support it.. it is coded on the above devices as a result of open souce android license b/w these omes... and also they have native 3g video calling feature and we don't have it in short they modify it desirely ( ui + system library )..
currently it would not be possibly to port whole layer of code as its very difficult as it would be embedded in ics it eould easy then just to port wifi port thing,atm no one can say about its dependencies on other files
ics adding wifi direct feature-
android-developers.blogspot.com/2011/10/android-40-platform-and-updated-sdk.html?m=1
also this depends on hardware which i'm not sure if one used in our is really supported...(still searchin' or that )

Related

[Q] WiFi Direct gingerbread

Hey guys,
Does anybody know if WiFi Direct is working on gingerbread?
I can't find a cooked ROM with this capability.
Wifi cast lite
There is a work around for this called WiFi Cast Lite ...just Google it and you can find it ....just like WiFi direct you need this app in both the devices to do the transfer....
The process is to enable hostspot on one device and connect to that hotspot using the other device and you are connected....then u can use the app to transfer the files ....
sridhar2malladi said:
There is a work around for this called WiFi Cast Lite ...just Google it and you can find it ....just like WiFi direct you need this app in both the devices to do the transfer....
The process is to enable hostspot on one device and connect to that hotspot using the other device and you are connected....then u can use the app to transfer the files ....
Click to expand...
Click to collapse
FC on HTC Explorer everytime
Totinsky, WiFi Direct was officially implemented by Android in ICS, but it sucks huge lemons and it crashes the phone all the time. WiFi Direct was finally stabilized in Jelly Bean (thanks to a certain little company). There is no official support in anything pre-ICS, I'm sorry to say. On another note, if you happen to get JB, we are building a proximity P2P file sharing app that uses WiFi Direct. The app is called Drop, and it is a simple, fast, and secure way to share files with people/devices in proximity. We are going into a limited Private Beta soon, so if you're up for the challenge, (and running Jelly Bean) then sign up at www.get-drop.com. Seats are limited, and we have a rolling enrollment, so check it out.

New skype release today!

http://techcrunch.com/2011/06/30/skype-for-android-now-support-video-calls-works-over-wifi-and-3g/
Not working on the transformer or the gtablet yet. But hopefully we'll get a working app soon either from microsoft or from the dev community.
I tried a patched version that took out the restriction. It force closes when trying to accept a call and enable video, but the settings and buttons show up...
gtab
Can some one upload the APK when they get the new video skype so we can try this on the gtablet.
Here's the issue, I think...
The support for video chat requires Gingerbread. If I understand correctly, this is because GB finally introduced a standard API to access the front camera.
Until Gingerbread did this, all apps that accessed the camera needed their own drivers to do so (there was no standard camera driver to access back then, which is why apps needed to have built in support for specific devices).
Skype is using this to their advantage by releasing an app that doesn't require much code change to support device almost any device (why they are only supporting specific devices at a time is mostly political AFAIK).
But here's the problem- There is no official Gingerbread for our hardware! All the GB roms we have are hacked together with peices of code with missing native hardware drivers since they don't exist! That means, I would guess, the new Gingerbread camera API is USELESS BECAUSE GINGERBREAD LACKS THE NATIVE HARDWARE SUPPORT!
Yes, this is awfully depressing. But without a real Official Gingerbread rom, unless Skype starts offering Froyo camera support (unlikely since they would go back to the old problem of suporting each camera hardware individually), this is just not going to happen.
Maybe if the rumors of official Honeycomb drivers turn out to be true, and Skype eventually supports video with HC (another *IF*), then maybe. But that's a long way off.
Very depressing- I was very excited about this working until I came to this realization.
Wrong thread.
How's that? Looks like the correct thread to me.
Dishe said:
How's that? Looks like the correct thread to me.
Click to expand...
Click to collapse
I meant myself. I put a post here and then realized it was meant for elsewhere. Multiple windows openned.
Here's the apk for the new released skype vid app.

[Q] What's in Touchwiz?

It may seem a stupid question but, since the news that Samsung won't be releasing ICS for the SGS I've been pondering my alternatives.
I would imagine a port of Nexus S ICS would work on the SGS' given their similar hardware specs but, of course, you would lose TW; Samsung's reason for not developing ICS for the SGS as there is not enough ROM for ICS + TW
I read on another thread that video-calling was not part of the standard Android build and was something that Samsung added. I myself originally bought an ICS because it was the only Android phone with a Bluetooth SAP stack, which I need to support Bluetooth integration with my car.
I have used video-calling and use BT SAP every day so would I be able to add these to a standard ICS build or are they integrated into TW? Back to my original question what else is built into TW?
Touchwiz is the layout of the original samsung galaxy s rom+some unique apps.The problem is in device maybe small amount of RAM and ROM.The Samsung would update to ics but only with touchwiz,like samsung galaxy s II

[REQ] NFC support for S II

have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Edray said:
have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Click to expand...
Click to collapse
The main problem is handling the fact that some of the NFC stuff behaves VERY badly if put into a device that doesn't have the hardware.
No one ever figured out a way to get it added to the P without either having a separate build or breaking the non-P I9100.
Although with the new infrstructure for "unified" device builds, this might now be possible.
As an FYI, the I777 (which REQUIRES a different build due to having different call audio, touchkeys, and a few other things) has NFC. The main blocker on the P was not wanting to create yet another build.
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Edray said:
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Click to expand...
Click to collapse
We don't do separate flashable ZIPs and stuff like that. Our build system doesn't support it, among other things.
One more in the request
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
bajajel said:
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
Click to expand...
Click to collapse
Sorry, but adding NFC to the I9100P won't help you here.
AOSP is missing HCE support for any device with an NXP NFC chipset. Until that changes, the I777/I9100P will not be payment capable even if NFC is added for P builds.

[Q] Could the Remix OS be ported to Droid 4 for use with a Lapdock?

Hi,
I just discovered Remix OS on Kickstarter, which sounds like an improved version of Webtop. Based on Android 4.4.2, with a Taskbar and improved multi tasking where you can switch through apps like with Alt-Tab and show tiles of running apps on the desktop. That actually sounds great for the use of a Lapdock, which I just recently got.
Now the developers offer it for a pledge of only 1 dollar and I'm thinking about pledging, but only the Nexus 9 and 10 are officially supported.
So that got me thinking, if I buy the ROM for 1 dollar, there should be a way to customize it to run with our Droid 4, right? Does anyone know how to do that or could help/teach me how to do it?
Just asking, if anyone else too thinks that this could be an interesting addition to an existing Lapdock. Now that I got CM12 running on the safe slot, the rom slot 1 would be free to test it there.
For those interested in the OS, here is a video, because the kickstarter site seems to focus more on their tablet.
Best regards and thanks in advance!
Probably not, probably android have bug and thats why lapdock doesnt work very well
Fervi
ferviverus said:
Probably not, probably android have bug and thats why lapdock doesnt work very well
Fervi
Click to expand...
Click to collapse
Which bug are you referring to?
The Lapdock 500 works fine for me, I just boot to stock slot and then Webtop activates itself automatically.
On stock it works perfect (but Remix OS is not stock)
But if you want use any other system or phone with Android - it doesn't work propertly (it works, but you have only part of your screen)
http://www.android-hilfe.de/attachm...pdock-fuer-rdh-2013-01-23_16-19-31_296_cr.jpg
Like that
And if you connect for example - Samsung Galaxy Note 2 - you still have it
But if you connect for example - computer, console or Miracast - you have full working screen
https://robpol86.com/lapdock/Atrix-Lapdock-with-a-Laptop/
I think it is a Android bug
Fervi
Why should it be a bug in Android? It works with the stock ROM, which is Android 4.1 or so. Clearly it's not a bug but something special Motorola put into that ROM, which prevents it from running if it's missing. Or maybe it just doesn't work for more recent Android version because something changed or was removed in those versions.
For non-Android-devices like a Rasberry Pi: Of course those work, because if you break it down, it's just an hdmi screen, usb keyboard and usb mouse. Those things have standard drivers in windows and linux, that's why they work.
Now this standard drivers also exist for Android, so my guess is, that Motorola somehow blocked it, but apparently people got it to work with a Samsung Galaxy S3, so it can't be an Android bug.
So maybe it is protected for Android devices, but all other (Miracast, Windows, Linux etc) works
But remember - Android have forked Linux kernel and on Linux it is working, so it is very "interesting"
Fervi
I think the problem is, only motorola and the HDMI driver on webtop is able to output a resolution different from the phone screen. CM12 for example is able to mirror the screen just fine, but only in native resolution to the phone (960x540). It would require specific software for this phone to get a different output resolution, kinda like re-writing Webtop.
Its not impossible, but I dont think its easy either, and I have no idea on how to do it.
It is possible to change resolution in phone from 960x540 to 1366x768
But you cannot resize Android on fullscreen
http://www.android-hilfe.de/attachm...pdock-fuer-rdh-2013-01-23_16-19-31_296_cr.jpg
Only stock rom do that
Fervi

Categories

Resources