Database Users

Me, wallet, cm7 and 2.3.7

I'm having issues starting nfc in cm7. It won't start.
Well I decided to try out the 2.3.7 update yesterday and use the google wallet. Everything worked well, I used my 10 dollars at McDonalds. So I nandroid back to the latest cm7 nightly and nfc won't turn on. I checked out the logcat and it has a bunch of errors saying "download firmware" and "can't download firmware". I went back to
2.3.7 and nfc works again. The logcat for 2.3.7 had a bunch lines saying secure nfc enabled, etc.
So I'm guessing my nfc on cm7 won't work correctly till 2.3.7 are released. Anybody else seeing this behavior?
I will try to post detailed locate, later.
Sent from my Nexus S 4G using xda premium

Just a thought: Kernel? I know that some versions of Trinity kernels disabled NFC for some testing...

I'm using petes kernel in cm7. It worked before using cm7 nightly. I'm thinking 2.3.7 injected some kind of security into the nfc chip that 2.3.5 can't read because it works perfect on 2.3.7.
Sent from my Nexus S 4G using xda premium

i think 2.3.7 unlocks access to what they're calling the 'Secure Element' chip which Google Wallet uses to store your credit card data (and keep it separate from the phone's internal memory making it harder to hack). so like you said, i assume it's a security thing in 2.3.7

Here's a pastebin of my nfc enabled on 2.3.7
http://pastebin.com/qw9Dtgca
Sent from my Nexus S 4G using xda premium

I can confirm nfc no longer works on cm7 after flashing stock 2.3.7
Sent from my Nexus S 4G using xda premium

I posted else where but I figured I'd drop a line here. Same issue here. NFC won't turn on. Wasn't worried about it previously as I just assumed it changed some of the settings for the NFC and obviously didn't change back when flashed to CM7. IE Anything under 2.3.7 after 2.3.7 would not have compatible NFC software in the background.
And, as you said going back to 2.3.7 it works fine.
Has anyone else had the problem from the other thread I saw? Where Google Wallet is FCing on them after flashing back and forth?

Google Play Server Error

Ok last night I flashed the gingerbread miui rom and I couldnt get the market to work. I didnt pay it any mind. It continued on today with the same problem. So I flash nb stock rom, cm7.2, cm6.1.1 and cm 7.1 and I keep gettinf server error. Is this a problem that google play is having and is anyone else experiencing this problem?

Have you tried re-flashing google apps? When I used the MIUI ROM, I installed this version: gapps-gb-20110613-signed.

That's strange. I didn't have that problem... Try flashing the gapps.

Tried flashing the recommended gapps but its still a no go, even on stock rom. This is crazy
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App

Got the problem solved, just downloaded market enabler and spoofed my provider and now it's working again.

I had this problem too, I cleared data on the Google play app and all is fine again.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

aaldiar said:
I had this problem too, I cleared data on the Google play app and all is fine again.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice, this just fixed my Google Play connection issues after an update to Calkuin Mod on E4GT.

NFC is not working anymore on my GT-i9505 !

Hi,
I have an issue with my GT-i9505 on XXUAMF8.
When i bougth the phone, nfc worked perfectly and i used it occasionally.
Now, after a few update (always stock rom), the nfc seem to not work anymore.
I have the option to activate it, all is ok and green, but there is no action when i use tags or other device like s4 for S-beam fonction.
I just have the last Faux kernel, some nfc application to write tags...
Don't know the source of the problem !
Thanks.

No idea ?

Do you use wireless charging now? Because it could block the antenna which is in the battery.

No, i don't have that.

Stock rooted or pure TW stock?
Heard something somewhere about custom ROMs (rooted) or kernels blocks NFC or something like that.
Sent from my GT-I9505 using xda app-developers app

I just have custom kernel, custom recovery and root.
My dad have same phone, just rooted and his nfc works.

Try a different kernel. Perhaps the same one that your dad is using. If that doesn't work, try powering down and pulling the battery to reset the NFC circuit (located inside the battery).
Sent from my GT-I9505 using Tapatalk 2

I try to remove the battery, no effect...
My dad just have stock rom with cf-auto-root...

Then try the stock kernel. The custom kernel might be the problem.
Sent from my GT-I9505 using Tapatalk 2

Even with stock kernel i have the issue... maybe hardware problem ?

I don't know what else to suggest besides returning to 100% stock to rule out a hardware failure.
Perhaps try clearing data from the NFC Service app in the application manager?
Sent from my GT-I9505 using Tapatalk 2

jowabi said:
I don't know what else to suggest besides returning to 100% stock to rule out a hardware failure.
Perhaps try clearing data from the NFC Service app in the application manager?
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
I just have the same problem. NFC was working now not anymore

I think i'm gonna wait for a stable google edition 4.3 rom and do a full wipe...

Go to a service centre if you have warranty and they will do all the dirty work, figure out if it's hardware / software and fix it themselves, return to stock first.

I did a full wipe and nothing... Mybe the MF8 rom has issue with french s4...

When i put my phone and a Xperia Z back to back, my phone make the NFC sound so it's not a hardware problem ?!

No other idea ?

Moz007 said:
I did a full wipe and nothing... Mybe the MF8 rom has issue with french s4...
Click to expand...
Click to collapse
I'm on MF8 and I have no problem with NFC. (Stock kernel and pre-rooted MF8)

Ok so it's not related to the rom...

ive only heard of deodexed roms not being able to use nfc?

[Q] nexus 7 keeps restarting after 4.3 update

this is my first time making an account/posting on xda after being a long time reader and user. just need some help with my nexus 7 32gb WiFi (Australian model) i have loved this tablet and I have never had a problem with it, its unrooted and has never been dropped or anything like that, i updated it to 4.3 ota last night and almost instantly after that I have noticed it keeps rebooting itself like so many other people have problems with on earlyr versions like 4.2, please tell me what I can do to fix this, I can't find any straight help, my location is off and always has been, but I have noticed every now and again I would notice (on earlyr version) fused location would always stop working and ask me to force close randomly, that now doesn't happen but instead it retstarts, so do u think this could be the problem? any help would be awesome, thanks.

If you're having a problem with 4.3 you can try two things.
1. Revert back to 4.2.2
2. Try a rooted official stock ROM.
Sent from my SGH-T999 using Tapatalk 4 Beta

fixed it!!
TheLastSidekick said:
If you're having a problem with 4.3 you can try two things.
1. Revert back to 4.2.2
2. Try a rooted official stock ROM.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I fixed the proble,m, I found a site that finally gave me a good option to try besides rooting as I don't want to root my nexus 7, turns out HD widgets was cashing the issue, but the issue only showed up after this update, thanks for ur help though.

adex9 said:
I fixed the proble,m, I found a site that finally gave me a good option to try besides rooting as I don't want to root my nexus 7, turns out HD widgets was cashing the issue, but the issue only showed up after this update, thanks for ur help though.
Click to expand...
Click to collapse
Ah good note. Thanks that's helpful for future knowledge. Glad all is well for you.
Sent from my Nexus 7 using Tapatalk 4 Beta

I've had random reboots on 4.2.2 and one since updating to 4.3. Usually happens when I am mounting or unmounting a USB drive, but sometimes it's for no apparent reason.
Sent from my SGH-I747M using xda app-developers app

[Q] Needed: DEVS to fix issue# 58317 (radio reboot)

Hi XDA Dev's,
SInce I'm not capable myself and Google isn't to keen on helping us N4 owners with known issue # 58317 (see issuetracker https://code.google.com/p/android/issues/detail?id=58317 ) I'm calling out to the XDA community...
This issue is affecting probably most (if not all) users that use MVNO's, like Tele2 in the Netherlands. What happens is the GSM radio reboots without notice and comes up again but is stuck on the SIM pin (if enabled), leaving us without being able to receive any calls.
Google is aware of it, but gave it lo priority as they say 'it effects only a small number of people'. But as you can tell from the thread, there's PLENTY of people all over the world experiencing this issue.
In the thread is a link to the proposed fix for AOSP, posted by the owner of the issue. Is there anyone out there that can fix this by giving a flashable ZIP for either AOSP or JWR66Y from Google?
Thanks - here's hoping for the best!

You can also just flash another radio you know? .48 is working fine for me.
Sent from my Nexus 4 using xda app-developers app

Remcotjuuh said:
You can also just flash another radio you know? .48 is working fine for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well... it's not the radio as you can read from all the posts in the issue tracker. Ofcourse I can stay on 4.2 and never update to 4.3 but that's kinda pointless when you have a nexus device? The issue is with the radio drivers, not the firmware and then only with MVNO SIM's. Simply flashing new radio firmware just won't cut it...
What provider are you on and what firmware?

I'm on 4.3 using the .48 radio, not 4.2. And it DOES fix it. I'm on Tele2, had exactly the same problem and flashing .48 fixed it for me.
Sent from my Nexus 4 using xda app-developers app

Remcotjuuh said:
I'm on 4.3 using the .48 radio, not 4.2. And it DOES fix it. I'm on Tele2, had exactly the same problem and flashing .48 fixed it for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok, well worth a try! Will flash when I find some time and let you know, thanks!

Remcotjuuh said:
I'm on 4.3 using the .48 radio, not 4.2. And it DOES fix it. I'm on Tele2, had exactly the same problem and flashing .48 fixed it for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Was on 4.3, seriously suffering from the simlock/heat/batterydrain problem. Now on Cyanogen Stable 10.1.2. The problem persists, it may even be worse. You say you flashed the .48 but not the 4.2? Which one? (Link?)

involver said:
Ok, well worth a try! Will flash when I find some time and let you know, thanks!
Click to expand...
Click to collapse
you okay dota aye?

This happens on an AT&T SIM as well.

Well at first my hopes where up, after flashing .42 radio no issues for a few days. Alas... today I got the sim pin again. So back to square one...