Hi! Is there a way to change the Bluetooth's MTU to 512 on the Redmi 7? To match most Samsung phones' MTU and use the Amiibo support on the Joy-Con Droid app. I've been asking on various rom developers' threads, and other channels but I don't get any answer.
Thanks in advance.
As shown here:
https://github.com/Evolution-X/system_bt/commit/5445c98fef4dbc718ad9145d507d984ec31a5db8
Related
Hi there,
right now I am researching for a possibility to emulate a smartcard with a smartphone. As we all know, the standard os and api won't let us do this. What I want to achieve is create a way to use the smartphone for physical access without the need to change the existing infrastructure. o achieve that, the smart phones gets a localy and time limited informationtoken it should present to the reader. In other words, I actually dont realy need access to the secure element, as any data would be temporary.
Right now I am a bit confused about this. Is there a way to use card emulation, without the need of a secure element? I have searched for different ways to acchieve this, but on many ends, I can't seem to find a definitv answer.
For example I stumbled on OpenNFC. They praise that they can acchieve card emulation. Yet, they don't provide any examples on this and fail to actualy deliver some sort of information on the requirements of this. As I understand it, it seems like this method only works when the smartphone uses Inside Secures Chips MicroRead or SecuRead. Anyone knows more about this?
I'm realy open to ideas on this one, as it seems theres little to no documentation or examples to go on.
I'd realy be happy to read about what you guys found out on this issue as of yet.
I've been looking into it too. This is what I have found:
EddieLeeDefcon20.pdf
nfcproxy
(Google them, I can't post links)
So, yeah, it can be done, but you have to modify android to be able to.
I ended up to OpenNFC too, but no sample code!
I have a good background on Mifare Classic 1K and 4K programming using RFM130 under linux and win.
Sent from my HTC One X using Tapatalk 2
Ok, so after browsing the mailinglist like a maniac I found this answer from one of OpenNFCs developers:
Hello,
The OpenNFC stack porting on Android complies to the Google API, as far as the applications are concerned.
Since these API do not allow an APK to do card emulation, it is not possible to use this mode on the Nexus,
nor on any Android phone, with or without OpenNFC.
However, OpenNFC provides card emulation feature for other porting (Win32, linux), depending on the hardware capabilities.
Kind regards,
Stephane
Click to expand...
Click to collapse
Source is on their mailing list on sourceforge, cant post link....
So seems we can forget this one... Only option would be using the Cyanogenmod patch that is used by NFCProxy.
When this message has been posted? I think things has changed (not sure)
Anyway, I posted a message yesterday to have more informations about their projects on Android
The Message is from March 29th, 2012.
Again as I said, if that has changed, they really have to work on their communication to the outside. There seems to be noone but the devs that can say anything about this. And that means quite a lot.
When there is no API for something, we can use native code and directly communicate to NFC hardware. Agree?
Sent from my HTC One X using Tapatalk 2
Well, the way I understand it is, that we could take a build of android and tinker with it to get it to work. We would have to change the NFC softwarestack and its interaction with the rest of the system in order to make software emulation possible. That is quite some pile of nontrivial work to do if you ask me.
Sorry for doing a new reply instead of editing the old one, but I think this is interesting enoug to not get overread.
I got an answer from the OpenNFC Developerteam regarding my question. Part of my question was also if it was possible to emulate for example a Mifare Tag through their NFC Stack. Here is the answer:
Hello XXXXX,
The Open NFC stack is designed to be largely hardware-independent, with a small adaptation module (NAL) for each hardware chipset. However, currently we only provide the NAL module for the MicroRead / Securead chipsets; therefore out of the box we are only compatible with these chipsets.
It is possible to emulate ISO 14443-4A and -4B cards and Type 4 tags from the Open NFC stack; for emulation of MiFare Tag, you’d indeed need to use a Secure Element.
Best regards,
Sebastien.
Click to expand...
Click to collapse
Hope this clears some questions regarding OpenNFC.
Hey,
Does anyone know if there is a working TAP implementation for connecting to a VPN server on android. I know the API doesn't support it, but I thought there might be a work around. Root is acceptable.
Doing a search for "TAP" and "android" together is futile, since tap is also a verb described how you interact with your device. It's very frustrating.
Thanks,
-PW
Perhaps try searching for "tun", as they're often listed together?
With the numerous types of vpn endpoints, you may find better answers from people if you clarify what you're attempting to access (cisco, openswan, etc)
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
spycedtx said:
Perhaps try searching for "tun", as they're often listed together?
With the numerous types of vpn endpoints, you may find better answers from people if you clarify what you're attempting to access (cisco, openswan, etc)
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Click to expand...
Click to collapse
I'm trying to access a openVPN server that is set up on a remote host. These are not public services. The "endpoint" is usually on the same hardware as the gateway of a particular LAN, but can occasionally be a node behind a NAT firewall. These are set up by my employer.
The reason we use tap instead of tun is because we need to monitor broadcast traffic on the remote LAN. Tun clients are supported on the android API, but Tap is not supported officially. I was asking to see if anyone found an unofficial way to do this. So far, I've only come across one solution that was apparently broken with newer versions of android.
What solution was it you found that's now broken? Did they remove tap from the newer kernels? Could be an easy enough fix for one of the custom kernels to patch back in.
I haven't used openvpn since 2.something, and I recall it working well, once you got the proper iptables and such patched in. So, I'm asking and following from curiosity.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Hi Guys Out there.
i need help from you if you can modify [NExtRadio APP] LINK& edit this app so that apart from searching ODD Frequencies it also start searching EVEN Frequencies.
If anyone can make this modification then by the help of "HeadsetButton Controller App" we would be able to Switch Tracks Via Default Headset even in Radio App.
Curretly in india it searches following Stations:
91.10
93.50
98.30
But it want it should also search Even Frequency Stations Like:
95
104
104.80
102.60
106.40
Thanks in advance.
I need to install Mobileiron and the secure apps from there that include Divide PIM mail, tasks, calendar and contacts. I am able to install Mobileiron and download the Divide PIM apps. But these apps do not open. I have not had this problem on my previous mobiles, Nexus 5 and Note 3 neo. Does anybode else have this problem? Any solutions, suggestions?
Thanks for your help.
Were you able to get this working? I just got my new ASUS Zenfone 2 and I am having the same issue.
Cheers!
Hi,
Have either of you managed to get this working? I'm in the exact same boat. Zenfone on latest update. Mobile Iron and Divide PIM at latest version. Selecting any of the secure apps results in a pause and then no response.
Any help would be appreciated.
Bump - anyone have any success with this?
There is a post on Reddit, search reddit.com for "Mobileiron work for anyone else?"; it suggests that someone got it working, but it's short on details. (My account is too new to post links.)
If you read the Mobile Iron documentation (for Divide PIM or Secure Apps Manager), it says they actually only support Android running on ARM. I don't know if that's just a blanket statement to give them an out, or if their programs have pieces that use native ARM compilation. If it's the latter, then we're likely completely out of luck; but if it's the former (and the Reddit post suggests that is the case), then there is some hope.
I have same problem, this is answer from mobileiron.
In the Android Limitations Document it is noted that only 32 Bit ARM CPUs are supported. Support for x86
devices is not a roadmap item.
AppConnect for Android is not recommended for devices with an Intel chipset (please see http://
software.intel.com/en-us/android/get-device for a list of these devices)
Also MobileIron is aware that some Asus devices such as Asus MeMo Pad 7 incorrectly identify the CPU
architecture as "armv71" rather than "Intel, this device is not supported and is currently a vendor issue.
Little late to reply to this but I do have MobileIron working for my corporate mail and apps.
I've personally never had an issue with this in the past with any of the mobileiron versions nor with the ZF2 firmware upgrades.
Make sure that you are running stock and are unrooted. You should be able to receive the certificates and proceed like any other Android phone.
I've started using NFC Tags with ICODE chip by NXP. There are several kinds of ICODE, such as ICODE SLIX, SLIX 2, SLIX-L, SLIX-S, but all are NFC Type V / ISO 15693.
I'd like to have a list of Smartphones, and maybe tablets, that are able to read and write these Tags. I've tried to contact directly NXP, but they didn't answered. I've tried with several smartphone, Android 4.4, 5.1, 6 and they work, but I'm not sure about compatibility with all smartphones, especially Windows ones. Is there anyone that have experience with ICODE that can help me?
I understand that an exhaustive list is utopian, but maybe there are some useful parameters. I.e. ICODE can be read by all Android 4.4+ ? Can be read just by devices with an NFC sensor made by NXP?
Thanks in advance.