Everything about this rom is fantastic aside from this NFC issue and a little bit of misc. theming stuff...
The NFC thing really just messed me up ... I've had to wipe to fix this ROM so many times... But yet it still seems to be the best out there for our ATT note 3...
I'm happy with NFC disabled... I know there's a way to remove setting options from the settings app... It's really the only thing that would stabilize this ROM...
As with NFC service disabled... Settings quits... Perhaps decompiling and editing the settings apk may be the fix?
UPDATE - I ended up wiping again.
Let me be the 10th person to say this in this thread.
DO NOT INSTALL GOOGLE WALLET OR ANDROID PAY - THEY MESS UP NFC AND CAUSE CONSTANT FORCE CLOSES.
UPDATE - Found a fix for this. Read below a few posts.
I am having the same issue, though it started after installing the Uber app ( I think). Would be great if someone could figure out a fix :/
---------- Post added at 06:05 AM ---------- Previous post was at 05:26 AM ----------
**BETTER SOLUTION A FEW POSTS DOWN**
So this fixed the constant NFC errors. I take no responsibility if this crashes your phone because it pretty much involved deleting things for no logical reason.
Regardless, this seemed to fix it:
- go to /data/data/com.google.android.gms and delete everything with "wallet" in the filename. One of the files specifically references google wallet for third-party apps, such as Uber and Lyft, both of which have previously set my phone off into NFC crash loops
- go to /data/data/com.google.android.gms/shared_prefs/com.google.android.gms.tapandpay.service.TapAndPay ServiceStorage.xml and change "tap_and_pay_enabled" from "true" to "false."
I restarted and hung at the AllianceRom boot video. Pulled the battery. Rebooted and everything works fine!
Cannot emphasize enough YMMV, I would only do this if you are at your whits-end and are seconds away from factory wiping anyway.
Thanks I'll definitely try your way too. It turns out that after testing a bit more, even having Lyft installed causes the wallet files to reappear! Uber, meanwhile, seamed to play nice. I'll try disabling the services as you mentioned and report back!
SUCCESS!! The seams to have fixed it. Thanks!
Thanks for the AllianceROM, the first one I chose to customise my device.
How do I get back to NC2 without hitting 0x0. Confusing that various sources differ that Odin burns 0x1 or not ?
I received a stock NC2 n900A, rooted it with Towelroot, got Alliance v12 thru SS 3.75 after going thru the OP.
It said I could get back to NC2 with SS backup of my stock NC2. Great.
Installed ARv12 isn't executing certain things as expected - there's couple Stagefright leftovers, Add Call Record button didn't show up...
Decided to get back to NC2 stock backup.
Reboot to SS, Wipe, Restore backup, reboot system got me to blank screen post Att white anime with "Unfortunately ... has stopped" pileup. Even to the only System restore which won't even show those FCs.
My Priorities - 0x0 stays
After days of gleaning thu, still confused what all can trip knox. People just talk evolved.
I had 3.4.0 722276 Kernel before with Odin Mode reading - 0x0 and S2, T2, R2, A3, P2 (How this interprets & restricts?)
After ARv12 I have 4335446 kernel and same Knox readings. But my Stock Recovery says OC1 at the top.
How do I get back to NC2 without hitting 0x0. Confusing that various sources differ that Odin burns 0x1 or not? I downloaded Stock NC2 4 files. Leaving out BL bootloader file would do?
My V9 alliance was stuck in a bootloop so I downloaded v12 and installed it from recovery. However when I go to my version in the about device it still says its V11 even tho im 100% positive I flashed the V12 I downloaded The MD5 also matched what was in the description. I am also getting the blank google music task bar too. Is there a known bug where it still says V11? Thanks for any help!
I have a Samsung Note 3(AT&T), rooted, with the N900a_v12 Rom installed for about 6 months now. The following issues I have not been able to work through. Although I must say, it runs great and I appreciate the ROM.
1. It takes literally 5-8 minutes for the phone to turn on. It will go in the the Alliance startup screen and run for a very long time and when it does show come on, a pop-up with "Updating Android Apps X of XX" appears. It acts like the rom is reloading at each start up. it is the same with Hot Restart as well.
2. My Dalvik-Cache is filling up the phone with over 3GB of stuff. I have deleted the folder and it came right back.
I'll be glad to send any additional information to help with these issues.
True, I can understand that, but, I've only erased it once and it has rebuilt itself during succeeding restart. However, even though it's there, it still takes 5-8 minutes to restart.
OK, I'll check out my apps and see what's going on with them.
Thank you for responding.
|Thread Tools||Search this Thread|