Related
Wrote this FREE application for the Android Community.
https://market.android.com/details?id=com.nxp.nfc.tagwriter&feature=search_result
NXP TagWriter allows to store contacts, URLs and text messages on any NFC tag.
The NXP TagWriter application allows you to store contacts, URLs and text messages on any NFC tag.
Features:
- Easily create tag content from your contacts and bookmarks;
- Write multiple tags in sequence;
- Backup the contents of a tag before writing it;
- View the existing contents of a tag;
- Erase the contents of a tag;
- Write-protect a tag;
- Keeps a history of all written and backed up tag content.
The application fully supports the NFC Forum Type 1 Tag, Type 2 Tag, Type 3 Tag, Type 4 Tag portfolio.
This includes a whole range of NXP and third party contactless IC card products like MIFARE UltraLight, MIFARE Classic, MIFARE DESFire and many others.
no one has 2.3.3 yet :-(
Wow, great to see some early practical demo work! Gives me hope that NFC might not be so useless in the near term after all.
Thanks! ...Now I just have to wait for 2.3.3. >.>
wow! thank you!
time to play with it
darn that sucks, it wont let me install it because of the version
Sorry we made you guys wait, but we wanted to make sure it was in the market the second the OTA came out, which is any day now according to google.
AllGamer said:
darn that sucks, it wont let me install it because of the version
Click to expand...
Click to collapse
Correct, we make hooks in the software so it only installs on phones with 2.3.3 and NFC. These requirements are needed to do NFC tag writing.
thepro8 said:
Sorry we made you guys wait, but we wanted to make sure it was in the market the second the OTA came out, which is any day now according to google.
Click to expand...
Click to collapse
Great, so unless the OTA is on this weekend, maybe in the coming weeks
Can you tell us of other features on 2.3.3 other than the official ones? bugfixes and whatnot?
chaval said:
Great, so unless the OTA is on this weekend, maybe in the coming weeks
Click to expand...
Click to collapse
OTA is expected to happen any day now (I'm hearing Monday is the day, but don't know for sure).
Sounds good to me, don't know where I am going to be able to test it out though, not much nfc stuff on the go in the UK lol
Sent from my Nexus S using XDA App
Yubikeys are quite neat, fairly inexpensive, USB security tokens. They happen to have a MiFare classic NFC chip built in too. Fairly easy to get hold of across Europe if you want to experiment.
http://www.yubico.com/rfid-yubikey
Check you WWW.Laks.com too. They sell a NFC watch.
Sent from my Nexus S featuring NFC by NXP
ok so its clear that 'some' I9023's have 2.3.3 pre-loaded. its also clear that NXP guys have it, coz well they made the chip in the nexus (right?) and they cant test it without it. there's apparently some BT profiles also coming with 2.3.3 (file transfer, etc). can anyone confirm this?
I wonder what the hold up is.
I now have 2.3.3 but it still won't let me install.
Sent from my Nexus S using XDA App
lancehudson said:
I now have 2.3.3 but it still won't let me install.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
same problem!
Same for me grrrr
Sent from my Nexus S using XDA App
NFC TagWriter doesn't show in Android Market.
Can NXP investigate the problem?
Thanks.
Same for me. I just upgraded to 2.3.3 but I can't find the TagWriter app in the Market from my phone. If I go to https ://market.android.com/details?id=com.nxp.nfc.tagwriter on my PC, it won't let me push it to my Nexus S either as the device is grayed out.
argilo said:
Same for me. I just upgraded to 2.3.3 but I can't find the TagWriter app in the Market from my phone. If I go to https ://market.android.com/details?id=com.nxp.nfc.tagwriter on my PC, it won't let me push it to my Nexus S either as the device is grayed out.
Click to expand...
Click to collapse
Things like this are common when google updates a handset. They need to update the servers to allow the updated devices to access apps. some other apps will be missing to like the official Paypal app.
Have to wait.
Seen this on another thread somewhere the other day.
For those of us who manually installed the update early is there any chance of NXP posting up a direct link to the apk? Not sure if that will work but I dont see why not
I'm starting to think this is Vapor Ware, or maybe Malware, they hyped the app, then seemed to falloff the face of the earth. Anyone try to install the app and see any weird things on the phone after?
Not saying I have, just asking if anyone has.
Does anyone know of a way to do the tethering hack using Linux?
Sent from my DROID3 using XDA App
There aren't any diagnostic mode NV access tools for linux that I am aware of.
Certainly none publicly available, although I am sure they exist.
try a virtual machine
Sent from my DROID3 using XDA App
hack
edited to say there is a zip file around that may work ,we will have to ask cellzealot
That zip file is for use with radiocomm only. Radiocomm isn't supported on linux:-[
Sent from my DROID3 using XDA App
There is a way to do this like we did for the DX and D2 in update.zip format.
We haven't released it in this form because the entire subject of free tethering has become a very high profile and controversial matter and has caused us a lot of grief, including having our app pulled from the market and many other issues surrounding this exploit.
We may decide to release it again in this form, but leaving it as a pure hack that involves a PC and serviceware raises the bar and forces users to take greater responsibility for their actions.
Using the NVM tables I posted in that thread will automate the NV writes in RadioComm and work on any device.
zip files
will the one that is around work on this d3,I have it ,I saved it but dont use it since I have wifi in the house now,pm sent to dsw361
nutpn said:
will the one that is around work on this d3,I have it ,I saved it but dont use it since I have wifi in the house now,pm sent to dsw361
Click to expand...
Click to collapse
No, it won't...that is why we haven't re released it for MDM6600 chipset devices.
This is serious business with a capital "B" for Billions of dollars at stake!
People don't seem to realize this and understand why the carriers and OEMs are trying so hard to put an end to it and limit its use.
We have very mixed feelings about packaging it in such a way that anyone with a rooted device can flash an update.zip having no concept of the underlying principles and or liabilities for theft of services.
Before we ever released it the first time we had serious reservations about it that turned out to be true. This is one of the primary reasons for moving to SIM based authentication for all future LTE devices.
disregard the PM
I knew if anyone would know it would be cellzealot,thanks again
Disregard the PM dsw361,I was so tickled we finally got wifi here in the country
If anyone is looking to purchase NFC tags for the Nexus 4 be aware that Mifare Classic 1K tags are not going to work with this phone. Stick to NFC Forum Type 1-4 tags. If you need more than 144 bytes look for large Topaz tags or Desfire tags (2k, 4k).
krohnjw said:
If anyone is looking to purchase NFC tags for the Nexus 4 be aware that Mifare Classic 1K tags are not going to work with this phone. Stick to NFC Forum Type 1-4 tags. If you need more than 144 bytes look for large Topaz tags or Desfire tags (2k, 4k).
Click to expand...
Click to collapse
Hey can you explain the reason why? Is there some sort of NFC specs? sort of how there are HDMI specs v1-v4?
Warbuff said:
Hey can you explain the reason why? Is there some sort of NFC specs? sort of how there are HDMI specs v1-v4?
Click to expand...
Click to collapse
Mifare Classic 1K tags *aren't* part of the NFC Forum specs. They are a legacy tag. NXP's controller (the one used in the Nexus S, Nexus 7, Galaxy Nexus, S3, etc) supported them in Android though.
They aren't supported on other devices (Blackberries, Windows Phone 8) as they technically aren't part of the NFC Forum standards.
With the Nexus 4 the NFC controller isn't from NXP. As a result it won't support the Mifare Classic 1K tags.
Thanks for the info
Sent from my HTC Vision using xda app-developers app
krohnjw said:
With the Nexus 4 the NFC controller isn't from NXP. As a result it won't support the Mifare Classic 1K tags.
Click to expand...
Click to collapse
Do you know which controller it is? And if that supports swp/hci? I.e. UICC secure element.
Can you tell me, which kind of tags i can use?
or maybe post a link to them?
I'm looking for this ones:
http://www.ebay.de/itm/10x-NFC-Tag-...dy_Zubehör&hash=item337d14a9b9#ht_2012wt_1208
They had ISO 14443A standard, which seems to be nfc type 2? can i use them with nexus4?
//EDIT: Or this ones, maybe work they?:
http://www.nfc-tag-shop.de/nfc/nfc-ntags-anti-metal-5
Oggy512 said:
Can you tell me, which kind of tags i can use?
or maybe post a link to them?
I'm looking for this ones:
http://www.ebay.de/itm/10x-NFC-Tag-...dy_Zubehör&hash=item337d14a9b9#ht_2012wt_1208
They had ISO 14443A standard, which seems to be nfc type 2? can i use them with nexus4?
Click to expand...
Click to collapse
Those look like Classic 1K tags.
You can use Mifare Ultralight C, NTAG, Topaz, Desfire, Felica tags without any problems.
okay, thanks!!
the second link i posted seems to use the "NXP Mifare NTAG 203" chipset with 168 byte. this would probably work you say?
Oggy512 said:
okay, thanks!!
the second link i posted seems to use the "NXP Mifare NTAG 203" chipset with 168 byte. this would probably work you say?
Click to expand...
Click to collapse
Yeah. Generally speaking anti-metal tags are more expensive as they have an isolation layer between the surface and the IC so that they work on metal.
ok. i'm not sure which way i'll use the tags, but if i now buy them wihtout "metal-funktion", i have maybe to buy another ones.
so i now buy the "metal-funktion" tags and i'm on the secur side, u know
The NFC controller is a Broadcom BCM20791 according to anandtech tear down.
there goes $30 i dropped on MiFare Classic tags
I'm having problems reading or writing tags with NFC Task Launcher on the Nexus 4. They are Topaz tags but if I try to write, even a very simple launch app task it says it is too large!
I've written to these tags before with my Xperia S and they work fine on that.
3Shirts said:
I'm having problems reading or writing tags with NFC Task Launcher on the Nexus 4. They are Topaz tags but if I try to write, even a very simple launch app task it says it is too large!
I've written to these tags before with my Xperia S and they work fine on that.
Click to expand...
Click to collapse
That's odd, Topaz tags should work AFAIK. Can you scan one with NFC Tag Info and send me the resulting XML? Can you also try writing it with debugging enabled in NFCTL and send me that log?
krohnjw said:
That's odd, Topaz tags should work AFAIK. Can you scan one with NFC Tag Info and send me the resulting XML? Can you also try writing it with debugging enabled in NFCTL and send me that log?
Click to expand...
Click to collapse
3Shirts said:
I'm having problems reading or writing tags with NFC Task Launcher on the Nexus 4. They are Topaz tags but if I try to write, even a very simple launch app task it says it is too large!
I've written to these tags before with my Xperia S and they work fine on that.
Click to expand...
Click to collapse
I have the same problem but these are the tags http://goo.gl/MvbqL that i had bought which they work with my Galaxy Nexus
yozpalang said:
I have the same problem but these are the tags that i had bought which they work with my Galaxy Nexus
Click to expand...
Click to collapse
They weren't Topaz tags. They were Classic 1K tags, which don't work with the Nexus 4 (but work fine with the GN).
The reason they were identifying as Topaz tags is due to how the identification logic was written. They were falling into the NfcA tech case but had already missed all other tag types (MifareClassic included) therefore they must be topaz tags. On the Nexus 4 this is not true as the Classic 1K tags don't report the MifareClassic tech as they aren't supported.
krohnjw said:
They weren't Topaz tags. They were Classic 1K tags, which don't work with the Nexus 4 (but work fine with the GN).
The reason they were identifying as Topaz tags is due to how the identification logic was written. They were falling into the NfcA tech case but had already missed all other tag types (MifareClassic included) therefore they must be topaz tags. On the Nexus 4 this is not true as the Classic 1K tags don't report the MifareClassic tech as they aren't supported.
Click to expand...
Click to collapse
will you link me to the tags that you know they will work for sure?
yozpalang said:
will you link me to the tags that you know they will work for sure?
Click to expand...
Click to collapse
Any NFC Forum type 1-4 tags will work.
NTAG203, Desfire, Topaz, Ultralight, Ultralight C, Felica
Everything here that isn't a Mifare Classic 1K: http://nfctags.tagstand.com/
If you're not in the US or want to use a different Vendor look for the tag types above. Type 1 and Type 2 are the most commonly found. These are tags that use the NFC forum standards and work on all NFC enabled devices (Android, BB, WP8, Symbian).
I recently brought Mifare Classic 1k tag at amazon.com/gp/product/B008P066GE/ref=oh_details_o00_s00_i00. It seem to work with my N4. I was able to program the tag to turn on bluetooth, open spotify and turn off wifi using nfc task launcher.
Sorry I cant post url yet.
godofdoom999 said:
I recently brought Mifare Classic 1k tag at amazon.com/gp/product/B008P066GE/ref=oh_details_o00_s00_i00. It seem to work with my N4. I was able to program the tag to turn on bluetooth, open spotify and turn off wifi using nfc task launcher.
Sorry I cant post url yet.
Click to expand...
Click to collapse
It's not actually reading/writing anything on the 1Ks on the Nexus 4. It's merely mapping the actions based on the ID. The actual tags don't work for reading/writing.
I'm the owner of AndyTags.com and my sole business is selling NFC Tags so you can imagine how thrilled I was when a customer contacted me shortly after the Nexus 4 came out to let me know his tags didn't work with his phone. To make things even more fun, a few days later another customer contacted me to say he had just gotten the Nexus 4 and was worried that his tags wouldn't work, but they did. So I began a lot of research, and along with a fellow Android fan who owns a Nexus 4 conducted extensive testing to get the final word on compatibility. There's a lot of confusing info out there so I thought I'd share these facts with you guys to make it simple so you could buy the correct NFC Tags for your new groovy Nexus 4.
The Nexus 4 & 10 are NOT compatible with Mifare Classic tags because Mifare Classic tags do NOT adhere to the NFC Forum's Standards. They can not write to the tags nor can they read information that someone else has written to the tags. However, they can detect the UID Code (kinda like a UPC code) of a tag which is unique to every tag. So, if you use an app like NFC ReTag or NFC Task Launcher which has the ability to just detect a tag and read it's UID code, and then launch settings/profiles/etc then you can still use Mifare Classic tags with the Nexus 4 & 10. This is why some people keep saying they are compatible. Just remember, technically they are NOT compatible - the phone can just read the UID code off of the tag.
What kind of tags DO work with the Nexus 4 & 10? Any tags that do adhere to the NFC Forum's standards. The most popular of which is the NTAG203. Unlike the 1K Mifare Classic which has 700 bytes of usable memory and is fairly inexpensive, the NTAG203 tags have about 140 bytes of usable memory and are slightly more expensive in general. However, 140 bytes is plenty of memory for most settings/tasks launching NFC Apps. Many apps, such as NFC Smart Q, allow you to create tasks and see how much memory is needed even without having tags so you can do that before ordering tags to make sure it's enough. The only things that it might not be enough for are vCards or if for some reason you want to program a really long text string to a tag (like more than 130 characters); but since most of us want to use tags to automate things, 140 bytes is enough for that.
What problems might you encounter using Mifare Classic tags to trigger events using the tag's UID? If you only use one app that detects a "blank" tag (Mifare Classic's are seen as blank by the Nexus 4/10) and read's its UID code and triggers a set of rules/settings/tasks based on that then you shouldn't have any problems at all! However, if you have more than one app that detects blank tags, then anytime you tap a Mifare Classic tag, you'll get a pop-up box asking you which app you want to use to execute the action which defeats the purpose of automation.
What is the deal anyway? Why don't the Mifare Classic tags work with the Nexus 4/10 like they do with all other Android phones? Basically, NXP is one of the leading manufacturers of NFC products. They not only manufactured the NFC hardware built into pretty much every Android phone out there up to this point, but also manufactured most of the popular NFC Tags in use. At some point they designed the Mifare Classic NFC Chips and designed them specifically to be compatible with their NXP hardware, but did not design them according to the NFC Forum standards which meant they wouldn't necessarily be compatible with all NFC hardware by other companies. Since pretty much all Android phones used the NXP NFC hardware, this wasn't really an issue and still isn't for most people. However, either Google, LG, Samsung or all three decided to use another company's (Broadcom) hardware in the Nexus 4/10. While any NFC Tags made by any company that adhere to the NFC Forum's protocols will work fine, because the Mifare Classic does not meet those criteria it is not compatible with the Nexus 4/10.
Great info. Thanks.
The kind of post intended to be on xda. Great information and very helpful!
Sent from my Nexus 4 using Tapatalk 2
Thanks for this. Just bought some more tags to replace the old mifare.
Excellent post, and information! Thank you!
Hopefully this will push the industry towards fully NFC standards compliant tags, rather than Mifare classic.
Thanks for the information. Just placed an order for the ntag203. Looking forward to trying them out.
Sent from my Nexus 7 using XDA Premium HD app
Thank you for the useful information and I just ordered a 20 pack for shipping to the Philippines.
Sent from my GT-P7300 using xda app-developers app
Thanks - This is terrific information. I already have a Nexus 7 and a nexus 4 is on the way.
Have few questions. Would appreciate your inputs:
1) Do you ship to international addresses? What do you charge for the shipping?
2) Will be using the NFC tags for lots of automation - for ex: turning off WiFi while leaving, enabling BT when getting in the car etc. Are these functions pre-programmed in tags you sell?
3) If I want to customize functionality, what kind of hardware would I additionally require?
4) Do you sell blank NFC tags so that I can program tags as I wish?
5) Costs - how much per tag and how much for the NFC reader / writer?
I haven't visited your site yet (as It's blocked at work), so apologies if this information is already available on the site.
,
your nexus 4 will be your nfc reader/writer, no additional hardware required. There are apps to program these tags
Sent from my HTC Desire using xda app-developers app
Awesome. Thanks!
managed to browse through the site as well, and got most of the information I wanted.
...now, If my nexus 4 came along...
If I want to place a tag on my router so that guests coming over dont need to ask for the password, will the native NFC app on their phone be able to read the data or do they need a specific app? If their phone will automatically read the tag, how will it be displayed on the device?
I have an n4.
Is there a way to make a tag that any android phone using 4.xxx (I.e. gs3, gn2, n4, gnex) do a check in with Facebook etc?
I bought a few tektiles to play with, but obviously can't write then properly.
Is 140 bytes enough to write a check in on Facebook command?
Sent from my Nexus 4 using Tapatalk 2
I wonder about security. Say you make a tag for your office, don't lock it and while you are gone someone wants to rewrite the tag to steal your information is this possible? If so is there any way to tell if your tag has been rewritten without reading the tag before using it? Can you read the tag before using it? Do any tags allow security like requiring a pin number to write to them?
Sorry, but my classics are working fine for both read and write. Definitely reading more that just the uid. Make sure your device is on 4.2.1.
Sent from my Nexus 4 using Tapatalk 2
pedxing said:
Sorry, but my classics are working fine for both read and write. Definitely reading more that just the uid. Make sure your device is on 4.2.1.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I am, and I can't write anything to a tektile.
And according to documentation, I'm not supposed to be able to. What NFC app are you using?
Sent from my Nexus 4 using Tapatalk 2
mrbkkt1 said:
I am, and I can't write anything to a tektile.
And according to documentation, I'm not supposed to be able to. What NFC app are you using?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
It can't write them, period. This shouldn't even be a discussion, it's not capable of reading or writing classics. It wasn't updated in 4.2.1 to support classics.
You *can* pull a UUID from a classic tag. However you cannot write to the physical tag or read regardless if the tag is blank or already formatted NDEF.
I couldn't write to them either until 4.2.1 was released. But all i own is 10 mifare 1k classics and all but one was blank prior to owning the n4. I've written to 4 others since that time using NFC task launcher.
Sent from my Nexus 4 using Tapatalk 2
pedxing said:
I couldn't write to them either until 4.2.1 was released. But all i own is 10 mifare 1k classics and all but one was blank prior to owning the n4. I've written to 4 others since that time using NFC task launcher.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
It's not writing them.
Sent from my Nexus 4 using xda premium
Duuuuude.... what the heck is it doing then? You think I'm lying about this? What possible reason would i have to do that?
Edit: also if you look at the ota package for 4.2.1 you'll see that a couple of NFC related packages and driver files were edited. I haven't bothered to look at the source on git but I'm fairly sure that was the mod they made.
Sent from my Nexus 4 using Tapatalk 2
Hi everybody,
I like the FM and TV apps. They replace two rather clunky devices. I also like ROMs like PAC, AOKP and CM. None of which have the former.
Is there a (preferably free) way to get TV and FM on AOSP roms? Or is there something like closed source drivers preventing this?
I tried Spirit FM, it didn't work.
Thanks,
sauprankul
I don't think the FM radio app works on aosp. I do know that tunein radio works. Its an FM radio but runs through the network connection. Its not exactly what you were looking for but it may help.
p3tr0s said:
I don't think the FM radio app works on aosp. I do know that tunein radio works. Its an FM radio but runs through the network connection. Its not exactly what you were looking for but it may help.
Click to expand...
Click to collapse
I know that the app doesn't work, but I was hoping for a mod or app that would replace it.
Tunein isn't as clear and Sprint doesn't have very good coverage around here (yet, they say).
Oh well.
Might work for FM radio http://forum.xda-developers.com/showthread.php?p=13379669
Sent from my HTCONE using Tapatalk 4 Beta
for the tv i think peel should work
Outside of Asia and a prototype or 2, there are no "over the air" TV chips in Android devices, AFAICT.
A few people have reported my FM app works OK on HTC One. And at least one said it didn't work. AFAIK, my app Spirit is the only non stock app that will work (for "real" over the air FM), and I've heard no indication that will change anytime soon.
The Sprint HTC One has a stock FM app, right ?
I will likely buy and officially support the HTC One within a few months.
mikereidis said:
Outside of Asia and a prototype or 2, there are no "over the air" TV chips in Android devices, AFAICT.
A few people have reported my FM app works OK on HTC One. And at least one said it didn't work. AFAIK, my app Spirit is the only non stock app that will work (for "real" over the air FM), and I've heard no indication that will change anytime soon.
The Sprint HTC One has a stock FM app, right ?
I will likely buy and officially support the HTC One within a few months.
Click to expand...
Click to collapse
I don't think the OP was referring to an "over-the-air" TV app, but rather the TV app on stock HTC ONEs that basically turn your phone into a remote.
tkoreaper said:
I don't think the OP was referring to an "over-the-air" TV app, but rather the TV app on stock HTC ONEs that basically turn your phone into a remote.
Click to expand...
Click to collapse
OP can clarify but when he says "...way to get TV..." it certainly sounds like he's asking for an OTA TV type app.
For TV etc. remote control, there ARE several apps on Play, and I think at least one of them works with the HTC One specific IR blaster hardware.
Oops, my bad.
I meant the app named TV, which allows me to use the IR blaster. I looked it up on the play store, only got apps that used network, links?
And I thought I had posted this a while back, but I get no audio from Spirit FM. (I'll try it again?) EDIT: Yeah, no audio... Am I supposed to let it scan networks or wait for it to tune or something?
mikereidis said:
OP can clarify but when he says "...way to get TV..." it certainly sounds like he's asking for an OTA TV type app.
For TV etc. remote control, there ARE several apps on Play, and I think at least one of them works with the HTC One specific IR blaster hardware.
Click to expand...
Click to collapse
I don't think the hardware is the problem, but rather the lack of IR support in AOSP.
sauprankul said:
Oops, my bad.
I meant the app named TV, which allows me to use the IR blaster. I looked it up on the play store, only got apps that used network, links?
Click to expand...
Click to collapse
Here's one of the IR apps on Play (more if you follow "Users who viewed this also viewed") : https://play.google.com/store/apps/details?id=com.microcontrollerbg.irdroid
App description says "Uses and needs external Irdroid module" and indicates it's a port of LIRC.
IR ports and their drivers are relatively simple, compared to audio, graphics, FM, etc.
So I'll bet that somebody will find/build an HTC One AOSP IR solution in the next 3-6 months. I've briefly considered it myself, but there are enough apps out there already IMO for when drivers become available.
BTW, I got the app link from this good thread about things missing from the coming Nexus Experience version: http://www.androidpolice.com/2013/0...tc-camera-features-and-no-beats-audio-switch/
My impression right now is that HTC One sales are doing better than many of us expected. The Nexus Experience thing has convinced me that I'll be getting one soon. And Samsung GS4 sales seem lower than expected. I think HTC One is "stealing" some GS4 sales.
My point is that I think HTC One XDA/custom ROM and apps development will do well, and solutions for IR and some other Sense related features will be found.
sauprankul said:
And I thought I had posted this a while back, but I get no audio from Spirit FM. (I'll try it again?) EDIT: Yeah, no audio... Am I supposed to let it scan networks or wait for it to tune or something?
Click to expand...
Click to collapse
AOSP based ROM ?
I've had a few HTC One success reports, but I think on stock ROM where the "HTC" Audio-> Method setting talks to the HTC proprietary audio stuff.
Send me a debug log with Menu-> Test-> Email-> Logs . After 20 seconds or so press Send.
There may be some simple ALSA controls to set to enable FM audio. But often I have to get a phone in my hands and spend some time on it before learning the FM audio enable secrets.
If this phone were using the Qualcomm WCN3660 FM/combo chips, like the Qualcomm reference designs used in One X LTE, One S and similar devices, then the "HTC OneS/X LTE ALSA" Audio-> Method would work, as well as "Digital OneXL/S".
AFAIR, this phone DOES use the reference WDC9310 audio chip, but the Qualcomm FM chip has special audio connections that I'm pretty sure the Broadcom BCM4335 FM/combo chip does not.
My guess is that HTC added some special FM audio controls to the WDC9310 driver. EDIT: OK someone sent me a debug log from a rooted One, I'll look to find new FM controls.
mikereidis said:
Here's one of the IR apps on Play (more if you follow "Users who viewed this also viewed") : https://play.google.com/store/apps/details?id=com.microcontrollerbg.irdroid
App description says "Uses and needs external Irdroid module" and indicates it's a port of LIRC.
IR ports and their drivers are relatively simple, compared to audio, graphics, FM, etc.
So I'll bet that somebody will find/build an HTC One AOSP IR solution in the next 3-6 months. I've briefly considered it myself, but there are enough apps out there already IMO for when drivers become available.
BTW, I got the app link from this good thread about things missing from the coming Nexus Experience version: http://www.androidpolice.com/2013/0...tc-camera-features-and-no-beats-audio-switch/
My impression right now is that HTC One sales are doing better than many of us expected. The Nexus Experience thing has convinced me that I'll be getting one soon. And Samsung GS4 sales seem lower than expected. I think HTC One is "stealing" some GS4 sales.
My point is that I think HTC One XDA/custom ROM and apps development will do well, and solutions for IR and some other Sense related features will be found.
Click to expand...
Click to collapse
I'm sure the ONE isn't doing much to hinder sales of the S4. If you take into consideration that the S3 and S4 release dates are roughly a year apart not many people are available to upgrade let alone fork out the full price for the phone. People tend to pick brands and stick with them.
Also, according to Wikipedia, "Upon its release (S4), it became the fastest selling smartphone in Samsung's history, with 10 million devices sold as of May 22, 2013, according to Samsung." AND "the One sold around 5 million units through its first two months of worldwide availability.[" So I don't know where this stigma comes that HTC is dominating Samsung right now. I'm assuming it's just pure fanboy-ism.
tkoreaper said:
So I don't know where this stigma comes that HTC is dominating Samsung right now. I'm assuming it's just pure fanboy-ism.
Click to expand...
Click to collapse
There isn't any, AFAIK. Samsung is still top dog. Just with a LITTLE less domination than was expected, and HTC doing a bit better than many expected for them. HTC has lost a LOT of market share in 2 years, now I think they've climbed back (just a bit !) from the precipice.
My very non-scientific survey of the front page of XDA forums seems to show about twice as much activity for all S4 variants, versus all One variants. One activity should have an edge because it came out first though...
Against the S4's expected dominance, I think a 2:1 activity ratio means the One is clearly among the most popular new devices, despite enthusiast complaints about non-removable battery and no SDCard.
For FM:
- AFAICT, the people who reported success with Spirit on HTC One were running stock ROMs.
On stock derived ROMs, deny SU to Spirit or better yet, set Debug-> FM API to "OEM Proprietary" and restart Spirit. If the stock FM app can work, then Spirit should be able to work this way.
Debug-> Audio Focus should be enabled, but this is done automatically on recent Spirit releases.
- I've taken a quick look at the ALSA audio driver differences. Digital FM audio is I think possible, using some HTC One specific ALSA controls intended for Bluetooth. I will need a phone and time to figure this out. I'm not sure there is even an analog FM route available; it may be digital only.
If there's a service manual and/or schematic, I'd be interested to see.
- Even without audio, I'm not sure Spirit can control the FM/combo chip on AOSP ROMs or using low level stuff. The code that works an many old and new Broadcom chips directly via "UART" does not work on this BCM4335.
Maybe it could work if Bluetooth were turned on and/or Spirit has Debug-> HCI Access set to "BT Socket".
EDIT: Actually someone just emailed me running CM10.1 and the FM chip control works through UART.
Overall, I just have to get this phone to make it work well. Usually I get new phones on Ebay from Hong Kong or US vendors. But in this case I think I'd be better to buy one locally for $650 plus taxes. I'd buy an HTC dev phone, but they only sell to US and I think the same will be true, at least initially, for the coming Google Nexus Experience phone. And... I've been reading the One has S-Off and even carrier SIM unlock now (?)...
I got a One on the weekend and have added "early" support for Spirit FM on HTC One.
HTC One first AOSP/Google support: http://forum.xda-developers.com/show...7#post42922397
Now where is the guy or gal who will do the IR... and Camera...