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?
Related
can some help me with the tethering on 2.3.4.
i try everything i could but it never work.
when i try the tethering it keep freeze for a few second and rebooting..
i have to go back the RC4 2.3.3(90% good accept mms video message)
Its working fine for me. Reflash the rom after full wipe.
Sent from my HTC Panache using XDA Premium App
now i feel dumb since i just made a new thread about this. Anyways OP did you try to full wipe and reflash the rom because i'm having this same problem since flashing royalginger 2.0 w/ 2.3.4? Did it work after you reflashed?
Also works for no problem
Sent from my Nexus S using XDA Premium App
Does not not work for me, I cleared both cache's, dalvik, wipe data factory reset, downloaded 2.3.4 from 3 different sites reflashed and once tether connects it reboots.
I would love to use their ROM but I need the teathering feature. I would also post my logcat file in their developer section but I need 10 posts to do that.
hi, i have a problem in my Nexus S i9023, after update/flashing to 2.3.6 i can't turn NFC on... i get an error. but when i'am going back to 2.3.3 (cause i had this version when i got him and it was working) it's working well, turning on and off normally, reading paypass cards, but even after full flash when i turn him on it's off and can't be turned on. anyone have the same problem?
sorry for my english btw
Yes, I have the same problem on my I9020T. If I downgrade to 2.3.3 or 2.3.4, it works fine, but as soon as I upgrade to 2.3.6, NFC is disabled and when you enable it, it just says an error occurred.
There's a topic on the Google forums for this as well.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=6b9bc174d2ce5651&hl=en
Yeah but google didn't respond on that... :/
Sent from my Nexus S using Tapatalk
2.3.6 , i can turn it on , but i don't have any card or application to test it...
hmmmm...
did you wipe and format them all before you reflash ROM?
Yes, wiping and reflashing has no effect.
http://forum.xda-developers.com/showthread.php?t=1284517
Google Wallet on i9020A/i9020T/i9023
Sent from my Nexus S using Tapatalk
maciejb84 said:
http://forum.xda-developers.com/showthread.php?t=1284517
Google Wallet on i9020A/i9020T/i9023
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Did flashing this fix your problem?
I can't I don't have root now
Sent from my Nexus S using Tapatalk
If you had tested previously a 2.3.7 ROM (CyanogenMod 7.1) then NFC will not work once you return to 2.3.6. There are fixes available but I chose to return to CyanogenMod and wait for ICS.
See my other posts in another thread about this problem.
But when I'm returning to 2.3.3 it is working so that's strange
Sent from my Nexus S using Tapatalk
ok I know this post is a little old but i came across it in a google search after noticing my nfc would not turn on on my stock 2.3.6 rom and the nfc fix on the post maciejb84 linked in his post fixed my issue and it allowed me to run gwallet on a non 2.3.7 rom which the other wallet fixes would not let me do so thanks maciejb84 and kibmcz(the OP of the link) for fixing my issue.
I had the same problem when i updated to 2.3.6. I solved my problem by going into app menu/all/nfc service and clearing data/cache and default values. Then reboot and you are ready to go.
Hope it works for u.
P
Sent from my Nexus S using xda premium
working fine on 2.3.6 for me on my i9023
Okay folks, if somebody could bring my issue to the attention of anybody who knows what to do about it I would appreciate it.
My issue is twofold:
1)I'm still getting random reboots with RandomROM Thunderhawk 3.3 despite the posting on the thread that says (NO MORE REBOOTS) Is there anything that can be done about this?
2)I checked my baseband version and the modem is still EC05, is there a way to flash or ODIN an EI22 modem for this ROM without getting a black screen when the icons should come up? Could this also be what's causing the reboots?
Thanks for anybody's help that is willing to give it.
Are you using a custom theme? And you have to flash the stickied modem delta. If you are using a theme, I would blame that.
Sent from my ICS NookColor using Tapatalk
I was using thunderhawk too and I had some reboots but onlyyyyy on the lockmod version. When I flashed the regular one I had no problems at all
And for basband I would probably try this
Nandroid backup
Flash "ec05 to ei22" its somewhere in the development section I believe
Reboot
If that doesn't work then a fresh new start is what I would Recommend
Odin back to stock
Root
Install cwm
Flash "eco5 to ei22" modem
Flash thunderhawk 3.3 (without lockmod if you could live without it)
Sent from my SPH-D700 using XDA App
I got the EI22 modem here and flashed it in CWM and it worked well. Only problem I had with thunderhawk is the lockscreen mod, and I'm having data issues on wifi after the phone's been on a while.
I was ec05 but when I flashed the Thunderhawk and it changed to ei22. never had a problem. Got a wild hair up my butt to flash the shadow kernal 1.0.6. Never been happier. no reboots, wifi works perfect, and very responsive. running a live wall paper and still get awesome battery life. give it a try
I saw several posts from folks having some wifi-4g interaction problems...switching back and forth causing one or the other to fail...is that a common problem to all 3.3 users, or are most people not seeing it? I want to give this a try, but I use 4g (at work) and wifi (home) everyday, so I'd like to see how common that issue is. I'm currently on Mostly-stock with Nubernel's latest released kernel...
Sent from my SPH-D700 using XDA App
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
You could always try a clean install with doing a factory data reset in CWM and wiping Dalvik, flash ROM, check to see if stuff works, then do an advanced data restore from your last nandroid. If you stll have problems then the best bet is to set everything up fresh after the clean install.
Cluefree said:
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The deal with the wifi/4g issue is that 4g will show 0.0.0.0 for ip, baseband, and dns if used after wifi in most cases. This is on official releases of 3.3 and newer. If you turn off wifi, reboot, then turn on 4g it should work. This is oviously annoying. Random provided me with alpha builds of 3.4 and 4.0, and the issue was squashed for me. However, the issue still persists in 3.4.3 official release according to some reports. I have limited access to 4g and can only test on certain days.
Thunderhawk is in a transitional period right now, and 3.4.5 should be released today. Random is hopeful this might solve some issues, including the dialer issues some are reporting with the 3.4 official builds. After that his focus will be on 4.0, which is EL30 based. Consider anything from 3.4 on a beta, and only run it if you want to help find bugs. Obviously you don't mind reporting or I wouldn't be replying lol. Just follow the threads and wait untill it looks stable enough for your usage needs.
Sent from my SPH-D700 using xda premium
Thanks! I certainly wasn't busting on Random's work...and I know he has limited access to 4g for testing, so that makes it harder for him to verify these things. So
I absolutely saw what you describe going from wifi to 4g. Going from
4g to wifi, I had wifi that wouldn't turn on at all (error when trying to enable), and, like you and others have mentioned, a reboot resolved both cases. I will hang out and see if he pushes out a fix soon, and just eagerly await 4.0. If it gets too annoying, I'll restore to my
Mostly Stock... Hmmm... Is there an issue restoring an rfs backup if I am now on ext4? Heh...
Sent from my SPH-D700 using XDA App
Just installed the latest 3.4 revision...I think...Heh. The update was so fast its hard to tell!
Sent from my SPH-D700 using XDA App
And...confirming...the wifi/4g issue persists. 4g ip address is messed up on the first connect after being on wifi...reboot resolves.
Sent from my SPH-D700 using XDA App
My WIFI network at home is visible and it showed full connectivity until I connected to it. It took a while but finally connected then showed no signal and disconnected, then showed full again, then tried to connect again, you get the idea. I have tested this with AOKP and Gummy with the same result. ALSO, I prefer to keep the network hidden but on setup, I hit "Save" it says "Setup has Stopped Working." I have seen this problem on AOKP and Gummy, the two ROMs I prefer at this time.
Root and ROM process I use:
- Started with stock Droid X (.621), SBF'd .604 through Linux (actually Windows the first time then had to call Verizon to fix. They were less than helpful until I got mad. I won't do that anymore)
- Zergrushv4 root through Windows
- Installed Droid 2 Bootstrapper
- Booted into ClockworkMod and formatted the various data's
- Installed ROM (AOKP build-39 is latest)
- Installed .604-to-.621-kernel-update (same result without doing this) <-- Currently running 15p radios if that matters.
- Installed Gapps
- Reset and performed initial setup
For sht's and gigs, I also tried installing the WIFI lib fix (I know it is for Blur) but that prevents AOKP from ever booting. It just sits on the rotating unicorn splash screen until I get bored and cut it off after 10 minutes. From there I have to go back to Linux and SBF .604. Ideas?
I was a noob as of last week but have learned a lot because of these forums. This is the first time I have had to post to get a question answered because there is so much good info out there. I appreciate the mostly accurate and educational information that is openly shared in this community.
EDIT: I tried SBF-ing .621 through RDS in Windows and then .604 in Linux. It is acting the same with Liberty (tried the wifi lib fix), and Cyanogen 7 and 9.
Does it connect to the network when on stock based roms or Gingerbread based roms?
Sent from my Galaxy Nexus using Tapatalk 2
infazzdar said:
Does it connect to the network when on stock based roms or Gingerbread based roms?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It connects fine with the .621 and the .604 .sbf's
I just tried CM7 and that wouldn't even install (after a fresh .604 load)
I need to find another good Gingerbread to load and try that. Suggestions? Pref not blur
I got Vortex working with the WIFI. I would REALLY like to get away from Blur though. Suggestions?
lowriderdog37 said:
I got Vortex working with the WIFI. I would REALLY like to get away from Blur though. Suggestions?
Click to expand...
Click to collapse
Vortex is about as close as you can get to a blurless stock based ROM.
Have you tried MIUI to test the WiFi?
There is a Gingerbread version and an Ice Cream Sandwich version.
Sent from my Galaxy Nexus using Tapatalk 2
OK, crisis averted. I don't know 'why' but it is.
Before, when I was trying to get everything working the ROM Manager load of Clockwork wasn't working at all, I was stuck using the Droid 2 bootstrap. For whatever reason I tried using the ROM Manager again to load Clockwork and flashed AOKP to find that everything worked out of the box.
infazzdar said:
Vortex is about as close as you can get to a blurless stock based ROM.
Have you tried MIUI to test the WiFi?
There is a Gingerbread version and an Ice Cream Sandwich version.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did try MIUI a while back but didn't care for the UI.
Stupid Noob question. Will it benefit me at all to install the .604 to .621 image update with 2nd init ROMs?
Rom 4.3 for mytouch 4g ?
Sent from my myTouch 4G using xda app-developers app
airport19832000 said:
Rom 4.3 for mytouch 4g ?
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Dude you already asked this I think...
There is no way any one of us can _ask_ for a 4.3 ROM for good old Glacier... Going for 2.2 to 4.2 was a huge feat. Going to 4.3 would be the most incredible feat ever. We should all appreciate the developers we have more, and thank them for their time, even if we will never have a 4.3 ROM.
Thanks guys!
I agree that all the devs deserve a huge thank you. I have a SGS4G and the devs there work very hard to get our phone to 4.0.4 to 4.1.2 to 4.2.2 to 4.3 even though Samsung said the phone can't handle it.
My buddy has a glacier and I have seen the great quality of Deva you guys have here and am sure they want 4.3 just as much as everyone here does. All I can suggest is patience and maybe a donation.
One thing we did to help "motivate" everyone is start a bounty threat. Everyone chip in and the pot goes to the dev that makes the first fully functional 4.3. Just a thought.
Sent from my SGH-T959V using xda premium
i cant wait for such rom to be out
Mods can close this since we now have 4.3 ROMs
Sent from my HTC Glacier using xda app-developers app
Speaking of that 4.3 ROM for the Glacier... my keyboard isn't working.
N_otori0us_ said:
Mods can close this since we now have 4.3 ROMs
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly, so I thought I'd give this thread a shot.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (gapps-jb-20130726.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem. I never had (unusual) keyboard issues with 4.2 or any older ROMs, and it works fine now, so this doesn't appear to be a hardware issue.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a d-bag? Thanks in advance...