The radio in the Captivate is ATT crapware - have to pay a subscription to ATT and it appears to download/stream data instead of using the built in radio.
The Vibrant has an app - radio.apk
I pushed the .apk to the Captivate - but, it doesn't work. Most likely it needs to be modified to work properly or there are some additional files necessary for it to work. It opens fine and detects whether or not the headphones are in place, but when "Play" is pressed it says it can't start the radio.
Any help would be appreciated!
Please take this to the Vibrant or Captivate forums!
Sorry Mods! - didn't notice there were different forums for the different versions of the Galaxy S.
Please move the the Captivate forum. Thanks.
Thread moved.
So the Galaxy Nexus guys got Wallet working on their phone with just an .Apk. I installed the .apk and it installed but FCed every time I tried to run it with NFC enabled. I was hoping someone more talented than me would be able to make it work for us.
http://forum.xda-developers.com/showthread.php?t=1365360
[APP] Google Wallet (Flash: 1.1-R41v8, APK: 1.1-R41v8) [18/12/2011]
I'm running the taste of ics from and tried side loading the apk today. All I got was a black screen.
i installed the apk and when the app started up i got an error saying my version of android was not supported (2.3.5) and then a second error saying that my device is not supported. Im thinking that maybe if i installed a 2.3.6 rom and then modified my build.prop to fake my device as a sprint nexus s, maybe that would trick the app into working? The rom will need to have nfc enable of course too. Anyone know of a good 2.3.6 rom with nfc?
I'm running TPCv2 with DaG.3 kernel and didn't get any errors when installing it. The app came up and said NFC needed to be enabled and when I did that it FCed. But otherwise it didn't FC or error.
EvilEvo said:
I'm running TPCv2 with DaG.3 kernel and didn't get any errors when installing it. The app came up and said NFC needed to be enabled and when I did that it FCed. But otherwise it didn't FC or error.
Click to expand...
Click to collapse
Same here. Installed fine and asked to enable NFC in settings. Once enabled though, Wallet forced closed. Running Quikwiz 1.0.3
I'm curious if changing build.prop to what the galaxy nexus is would fix the issue.
I would be eternally grateful if a dev were able to get this working for us.
I got the same result. Launched at first to tell me NFC needed to be enabled, but after I enabled it, I got force closes. Running QuickWiz 1.0.3
Its sounds like we are missing some important libraries that are required for wallet to talk to the NFC hardware. I noticed that the process for the nexus includes adding another JAR and APK which look like they add additional NFC functionality. Has anyone tried going thru the install process listed on this thread?
http://forum.xda-developers.com/showthread.php?t=1365360
sclarke27 said:
Its sounds like we are missing some important libraries that are required for wallet to talk to the NFC hardware. I noticed that the process for the nexus includes adding another JAR and APK which look like they add additional NFC functionality. Has anyone tried going thru the install process listed on this thread?
http://forum.xda-developers.com/showthread.php?t=1365360
Click to expand...
Click to collapse
Instructions in that thread basically just say install the .apk. I just tried it again with the same result. With NFC enabled, it FCs when trying to load. When NFC is NOT enabled, it starts up and initializes and then says NFC needs to be turned on. When I do that, it FCs.
right, i was talking specifically about the section below that where it talks about installing NFC extras via a command line.
Has anyone looked in their logs to see if they can find a stack trace after a FC happens? It may give a hint as to what we are missing. I dont get the same errors on my phone so my logs aren't useful.
http://forum.xda-developers.com/showthread.php?t=1282890
XK72 said:
I've seen a couple posts regarding getting Google Wallet to work (and hopefully I'm not being redundant with this post). I've had Google Wallet working on my own 2.3.5 source ROM for quite some time now and I figured I'd share what got it working for me. As a matter of disclosure, I do have the 4G, but I haven't seen anything in the code that would give reason for why this wouldn't work.
While I'm able to build a ROM, I for some reason, don't know how to put together a flashable update. Maybe somebody with a little more know-how can piece this together and try it out, or at least tell me I'm wrong.
Files needed from the GWK74 ROM:
system/etc/permissions/com.google.android.nfc_extras.xml
(I just added the permission entry to the existing com.android.nfc_extras.xml file instead to keep the clutter down).
system/framework/com.android.nfc_extras.jar
The version in the GWK74 ROM contains code that has yet to be released, since korg is down and all. The extra file has something to do with NFC emulation, but I've only glanced at it, so I really couldn't tell you what it does.
system/app/Wallet.apk
Obviously.
Here's the catch: The Wallet app requires permissions from Nfc.apk (NFCEE_ADMIN). By default, the Nfc.apk is signed with the "platform" key, but as long as these two files are signed with the same key, it will grant it the proper permissions to Wallet.apk no matter what key that may happen to be. Considering that Nfc.apk also requests other permissions from "platform" as well, certificate consistency would be advisable.
Hope this works out or at the very least, gets the ball rolling.
Click to expand...
Click to collapse
I suspect that the reason the ADK does not work on the Skyrocket is because the phones have different NFC chip. According to this post, the Galaxy Nexus has the NXP PN65N which contains an NFC controller as well as an embedded secure element (SmartMX) supporting both JavaCard as well as Mifare technology. The Galaxy S II (of which the Skyrocket is a variant) comes with the PN544 which does not have the embedded secure element. This could explain why NFC can be enabled on the Skyrocket (with a custom ROM) but it would FC the Wallet app. The SE (Secure Element) is needed to securely store transaction info and perform all the card emulation functions. Without it, the GW won't work. The app probably just check to see if a SE is available or not, and finding none, simply FC. Now it is possible to use the SIM as a SE but that would require a different SW.
It appears that folks were able to enable GW on the Nexus S, but I think it also sports the PN65N chip with SE. Can somebody confirm it?
wyt168 said:
I suspect that the reason the ADK does not work on the Skyrocket is because the phones have different NFC chips.
Click to expand...
Click to collapse
I think I have found some support for my speculation. In a thread on Android Developer Google Group, Michael Roland explained the 3 different modes of NFC. In particular, the role of SE in the card emulation mode, supports my view expressed earlier, I've lifted the relevant paragraphs here:
So the card-emulation mode allows the emulation of a contactless smart
card (and not an NFC tag, although the smart card could *possibly* be
used as NFC tag). As applications like credit cards typically have high
security requirements, card emulation is not handled by the NFC device
itself (i.e. the application processor of an NFC-enabled mobile phone).
Instead, the NFC device has a dedicated hardware component (the
so-called Secure Element) that handles all the card emulation. (*)
(*) This is not entirely true, as some NFC controllers (like the
PN544) would theoretically allow the emulation of ISO/IEC
14443-4 contactless smart cards from the application processor.
Yet, I don't know of any NFC phone that makes this functionality
available to the user and I rather doubt that this will become
available on the Nexus S.
The Secure Element (SE) is typically a smart card itself. But instead of
a normal contact/contactless smart card interface it has a connection to
the NFC controller, which connects it to the NFC antenna.
The Nexus S has an integrated SE (a SmartMX combined into the same
package as the PN544 NFC controller). This SmartMX emulates a ISO/IEC
14443 (Type A) smart card and a MIFARE Classic card.
In addition to this integrated SE it is possible to use a special UICC
(also known as SIM card) that supports the Single Wire Protocol (which
is an interface designed for the communication between the NFC controller
and a UICC) as the SE.
Click to expand...
Click to collapse
DELETE
Looks like Google Wallet was just released for AT&T Nexus devices, hopefully Skyrocket isn't too far behind. Officially or otherwise androidcentral . com/google-wallet-now-available-nexus-s-and-galaxy-nexus-att
LoSt180 said:
Looks like Google Wallet was just released for AT&T Nexus devices, hopefully Skyrocket isn't too far behind. Officially or otherwise androidcentral . com/google-wallet-now-available-nexus-s-and-galaxy-nexus-att
Click to expand...
Click to collapse
I tried the newest version from the market and got a secure element error. I don't think we're going to get wallet support any time soon because our devices don't have a secure element.
Would it be possible to edit the build.prop to appear as a Nexus S or Galaxy Nexus GSM now to all it to work? It installed fine on my phone but now says my hardware isn't supported.
EvilEvo said:
Would it be possible to edit the build.prop to appear as a Nexus S or Galaxy Nexus GSM now to all it to work? It installed fine on my phone but now says my hardware isn't supported.
Click to expand...
Click to collapse
No because our phones lack a secure element. Physically lack. So no edits to the app will work until Google decides to update this specifically for phones without a secure element.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I bought some of the nfc tags from sparkfun and the task launcher app and tasker so I could use the tags to run tasker tasks. you know, swipe when you get home, to work, into the car.
When I swipe one I get a force close on the nfc service.:-(
I tried skyicecream and buoyancy roms. fixed permissions. super clean install of rom. Thoughts?
mcmasterp said:
I bought some of the nfc tags from sparkfun and the task launcher app and tasker so I could use the tags to run tasker tasks. you know, swipe when you get home, to work, into the car.
When I swipe one I get a force close on the nfc service.:-(
I tried skyicecream and buoyancy roms. fixed permissions. super clean install of rom. Thoughts?
Click to expand...
Click to collapse
the Alien ROM supports NFC to a certain extent
Hello all and especially to any that can help,
I recently purchased a Droid X from a co-worker who had upgraded to a Droid Razr (carrier Verizon, Android 2.3.4, model MB810). I found out later that the phone had already received the .621 OTA update and was unrootable (someone may have found a method by now).
I did 2 days of researching before I attempted any changes in the phone and found that although a reversal of the .621 update was impossible (again the info on this may have changed), the Milestone X's sbf could be used. I downloaded the flasher program and 2 sbf's for the Milestone X, tried both and liked the larger one better. The phone now reads as a Milestone X (carrier Alltel, Android 2.3.5, model MB809).
The question I have is "what is the best custom ROM to use with this device"?
Cares and Don't Cares:
1) Carrier: I won't be placing this device on any carrier's network - Wifi and Bluetooth are good enough for me. I will be using a hack I found on these forums to be turning off the carrier radio later. This also means I won't be needing this device to have any phone functionality. This is basically going to be used as a mini-tablet replacing my 3 Craig tablets (#1 broke, #2 has damage to a daughter board - I think a chip burned out, #3 is refusing to reliably boot, made #1.5 from parts of #1 and #2).
2) Bluetooth keyboard connectability: The only program that hints at this is Bluekeyboard JP and it mainly uses Apple products. I have a Freedom i-Connex keyboard I would like to use and maybe others in the future.
3) Multiple mounting points: Currently this device only offers 2 points, even after rooting: a fake CD-Rom, and the sd-card. If there is a way to create a folder/directory and make it USB accessible, I would love to know how. I use my portable devices as reference file storage.
4) Reduced bloatware: I won't be needed phone software (see #1) and I don't need the prepackaged games nor social software (they cause more trouble then they are worth to me - namely see the news about TWD - texting while driving - accidents, social website enabled stalking, and other physical and informational damage). Also, other than program(s) to backup the installed ROM/RAM (Nandroid?), no prepackaged backup program (seen that most people prepack Titanium, I like Astro file manager better).
5) I know this one may be next to impossible to get; WINE: emulating a whole OS just for 1 program is wasteful. I would love to have a mobile copy of "DC Creator" (character and gadget builder) from Mike Love for DC Heroes and Blood of Heroes (Mayfair Exponential Gaming System program, I updated the dc_data.dat file to include new powers from Blood of Heroes and the Web, file is now over 70k).
6) ICS: I know that people are working on this one for this device, several problems to go (like the camera), and a thanks goes to them for even attempting this.
During my research, CyanogenMod 7 and 9 kept coming up. If I read my info right, these are not actual OS updates but instead mods that give some next gen functionality to the current roms (Froyo gets Gingerbread mods, Gingerbread gets Honeycomb/Ice Cream Sandwich mods). I haven't tried either yet so I don't know if any of these would help me or load my system down more.
My thanks to the whole device hacking community for enabling us to get the most out of our devices (whether it be android, iOS, PSP, PS2, ..... you get the point).
Sorry for the long post but I wanted to get as much info to whoever could help as possible.
i need ur help
dear i need ur help i have samsung nexus s i have install miui rom but after installation the mobile signal is not working plz tell me what can i do 'i am waitting for ur prompt respose
thanks
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Miui or cyanogenmod9
this roms are perfect
Thank you for the information. I'll dl both next time I'm near a high-speed connection (dial up at home sucks, thank you CenturyLink for avoiding my area for yet another year).
Hmm, MIUI appears to be only useable if you are upgrading from Froyo - I'm Gingerbread and I don't know if it will revert back to Froyo - remember this phone has already received the infamous .621 OTA update. It was probably a fluke I found that the Alltel SBF worked. So MIUI appears to be out of the question.
The Cyanogenmod 9 links I found appear to be dead when I checked from work (blocked?), but I also found no information on requirements. I see that you need both that and the Gapps files to use this.
Has anyone else gone the path that I have to SBF and root my device (Verizon Droid X Gingerbread 2.3.4 -> SBF -> Alltel Milestone X Gingerbread 2.3.5, rooted) and applied a custom rom afterwards?
Anyone have complete instructions on how to install CM9 for the Droid/Milestone X ->still a noob here<- that has taken the same path as me (and any further information on getting the camera working, last update looks to have been in February)?
Thanks again for any help.
Anyone know of a stable download link for Cyanogenmod 9?
All links I have found are either dead (404), 'server down for maintenance', or access denied (403).
Since I am new to posting on the forum, I am not able to post this to the Developer thread where this belongs, but would like it to be available for people searching for an answer to this problem.
This is regarding the thread [ROM][GB] Hybrid (Stock/CM7), Multilingual, Deblur
The thread is made for the Photon 4G, but can also be used on the Electrify, and in particular, the locked 2.3.5 version of the 4G.
There has been a ton a research done to get it cleaned up to work on the Electrify, but one thing I found was that Google Play was still having some issues resolving the Electrify as a proper phone with some of the mods out there.
This is mainly informative for anyone who has loaded this ROM onto an Electrify and not been able to access some items in Google Play.
Google Play uses information from your build.prop file to figure out what items in it are compatible with your device.
The biggest item with this is LCD Density. I throttled mine back to 180 to get more screen realestate, though that doesn't completely make sense, since the higher numbers are supposed to be more dense.
Either way, it worked for that, but also screwed up some items in Google Play.
This can be resolved in 2 ways:
1) Reverting to the standard of 240 for the device resolved this issue
2) Using the LCD Density Modder pro version will load a modified Google Play apk that will make it function properly
But this still didn't fully resolve the problem. These items still needed to be changed to get this back to recognizing the device as a Motorola Electrify:
ro.product.model=Motorola Electrify
ro.product.brand=MOTO
ro.product.name=uscc_us
ro.product.model.number=MB853 (this is actually missing from the ROM's build.prop)
ro.build.description=sunfire-user 2.3.5 4.5.1A_SUN_USC_19.0 19 release-keys
ro.build.fingerprint=MOTO/uscc_us/sunfire:2.3.5/4.5.1A_SUN_USC_19.0/19:user/release-keys
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/motomb853/Profile/motomb853.rdf
cdma.nbpcd.supported=false
ro.build.version.full=Blur_Version.45.1.190.MB853. USC.en.US
A couple of other mods I had done through rooting tools caused the following changes, but I don't think they are related to Google Play not working, but I wanted to be sure. I plan on changing them back shortly, so if there is no other post, they work fine:
dalvik.vm.heapsize=42m
ro.telephony.default_network=4
I hope this is useful information for some of you out there.
The wifi only model of this tablet running 4.1.2 has screen mirroring capability. However AT&T in their "infinite wisdom" decided to leave it out. I am looking for hopefully just a quick and dirty hack to enable it. Here are possible solutions in order of what I would like. I will accept any answer that get the feature, but I would like to not have to put some completely different custom ROM on it as it is for my dad and he is used to the interface as is. Thanks all for reading.
1. The stuff is all there and they just disabled it (maybe just edit a file after rooting the device)
2. They left out some files to offer screen mirroring (just copy some files over after rooting device)
3. Putting a custom ROM on (as long as I can get play store and all other normal functions)
I was thinking, does anyone have the stock firmware for the wifi only version of this? I was going to get that and get the firmware for this AT&T one and see what files the wifi version has that the AT&T one is missing. I tried searching online but it is old and all the links I find aren't there. The only model I can find is the 5113 which seems like a foreign version because all of the firmwares are from some other bloody country. I need the US version since the 1497 has the US version. Please help