I had my phone rooted and unlocked with freegee. I have had many roms on the phone and nfc worked great. I flashed a couple of the 4.4.1 and 4.4.2 roms and never had a problem with nfc working. Google wallet did not work and isis would refuse to install. Even with the xposed trick. So I went back to my trusty nocturnal rom and everything worked great. Then I seen that isis updated and now says it supports kit kat. So I flashed psx 4.4.2 12/31 and the att nfc fix. At that point I was unable to turn on nfc. I flashed back to nocturnal from a back up and same thing, nfc would not turn on. I did a wipe and a reflash and same thing. Even did a lgnpst using and same thing. So I went and got a new phone under warrenty. rooted unlocked and reflashed psx and same thing happened. I attached a logcat in the hopes someone can help me out.
Hmm, not sure if this is any help, but I am running PSX 12/2 build and I can confirm that NFC is working. Never tried Isis though.
Its so strange, and I figure out how this happened twice. I could just return this phone but I don't think it's a hardware issue and flashing back to stock should have fixed any software issues
Sent from my LG-E970 using xda app-developers app
Related
First off my Google Wallet works....EVENTUALLY. It takes many many tries for it to finally read and/or acknowledge my phone when I try to use it. This happens when completely stock and locked or rooted with several different ROMs. The secure element isn't bricked or it wouldn't work at all. It used to work perfectly then all of a sudden stopped working. I've tried uninstalling it, wiping the phone, factory resets, all the normal stuff like that. I don't know if this just localized to google wallet or if all NFC functions are like this. I don't have any way to test the NFC any other way.
Has anyone heard of anything like this? Or know of anything else I could try to fix it? I am pretty much spent out of ideas on what to do.
Like I said I get the same thing if the phone is completely stock and locked but here's my phone stats.
EVO 4g LTE
HBoot 1.19 S-Off
CM10 Deck's 12/4 Build
Stock Kernel that came with Deck's CM10
Baseband 1.12.11.0809
If you'd like any info on the phone, I'd be happy to post it for you.
You put a new case on your phone recently?
Sent from my LTEVO running MeanRom
Install OTA root keeper, temporarily unroot the phone using that then try again.
Sent from my Evo with CM10
Recently Flashed to CM10 and can't get wallet to work
onlybob said:
Install OTA root keeper, temporarily unroot the phone using that then try again.
Sent from my Evo with CM10
Click to expand...
Click to collapse
I recently flashed CM10 on my EVO (12/7 nightly) and I'm having trouble getting Wallet to work. From all I read, I should be able to install or sideload the .apk but that hasn't seemed to work. I'm wondering if I've missed something in my research. Now I'm getting the "Not Supported: Unfortunately, google wallet is not yet supported for your device or mobile network." When I try to launch Wallet.
Any Ideas? Maybe point me to the right thread. I could very well just not be getting the search results i'm looking for of course.
Always appreciative of the help.
http://forum.xda-developers.com/showthread.php?t=1881914
Sent from my Evo 4G LTE ( ͡° ͜ʖ ͡°)
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Same exact issue !
cauger24 said:
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Click to expand...
Click to collapse
My evo lte has been doing this for as long as i can remember also. I've been through dozens of roms and full wipes and still no bluetooth at all, not even recognizable.
Try deleting everything that is paired or was paired and then reboot. You may have Bluetooth defects if that still doesnt work. I have used on many sense roms, cm10, 10.1 varients with no problems. Hope that helps.
Sent from my EVO using xda app-developers app
Im having the same issue
I have updated my radios and noticed that i lost my Bluetooth connectivity. I was originally running meanrom ics until JB came around. Then updated my radios and moved to JB MeanBean. I did an Ruu and got it back to stock. No dice, stock rom Bluetooth still cannot find or be found. I tried my laptop ipad macbook car audio everything and nothing works. I ve never had any issues with my phone and it seems after Jelly Bean Bluetooth is non existent.
Currently I am running
Twrp 2.3.1
Arc Reactor Kernel
MeanBean3.09
Is there a way to see if the actual Bluetooth is borked or if its working properly, "if its sending a signal"?
Is it possible that something happened when upgrading that the BlueTooth became corrupted? or can it just plain old stop working, died?
At that point if it's Borked on several roms
Then it's time to take it into sprint. That's a manufacturer defect / issue and they should swap it out. Assuming you bought legit from them
Sent from my EVO using Tapatalk 2
Yes I bought it legit when it came out. I also have the insurance plan with Sprint. The only thing I'm worried about is the new hboot and unlocking/rooting the new phone .
But I guess if it means a new phone then I guess its best... To get a fresh new evo
Sent from my EVO using xda app-developers app
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
More things I am noticing:
The Flashlight app doesnt work anymore
Camera doesnt work then causes the whole phone to become unresponsive.
Bump!
Can anybody help me out? Im dying over here without a phone that works.
the phone app keeps crashing. If i reboot, things work ok UNTIL I make a phone call....then nothing works.
Very strange!
I would try wiping 3 times
Sent from my EVO using Tapatalk 2
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Also are you restoring things from the titanium backup?
Sent from my EVO using Tapatalk 2
MerkoPCS said:
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
Click to expand...
Click to collapse
i say you should flash MEANBEAN, its a stable JB rom and some of the bugs like the proximity sensor have been fixed thanks to the devs here at XDA. its running very smooth for me. the only issue for me is that google's navigation doesnt work, but telenav works just fine. just wipe your phone about 3 or 4 times (i always do that to ensure i get a clean install on any rom). good luck!
I would re-download CM10 and verify checksum since you didn't mention that.
Sent from my EVO using xda app-developers app
Thanks for the replies.
Really all I want to do at this time is go back to stock, which I currently am on.
But even on the stock 3.15 ROM, it is very very unstable. The phone is majorly delayed. I get 1 ring on incoming calls before it goes to voicemail - but the person calling hears the normal 5-6.
For CM10, I used the same zip file (stayed on my SD card) that I used without problem for almost a month.
I took the phone to sprint (back to stock) and they couldnt figure it out. Getting a replacement tomorrow.
Could I just have a coincidental hardware problem? Seems odd if that is the case, the phone was working perfectly until I went back to stock using the 3.15 RUU
I got my replacement phone last night, did an OTA upgrade to JB in the store and the proximity sensor didnt work...
was about to tell the rep to just order me a GS3, but I said hold off....I really prefer the 4GLTE over the S3
Went home and flashed Meanbean......WOW!
Just like stock, and the prox sensor works!
so my plan is to just keep this ROM until HTC fixes the issue in their next maintenance release.
in TWRP, i made a backup and selected all the options Is this sufficient to get me back to stock, then do an OTA upgrade for the maintenance release, if and when it comes out?
Today for whatever reason my phone decided it didnt lke verizon anymore and decided to jump to USCC. Seriously though. I flashed the latest test build of CM 11. played with it. then wiped data and flashed CM 10.2 and booted. next thing i know it is trying to activate on USCC. So i odined to stock MDK and attempted to get it fixed. There was no help given there. Lady was really nice but still no help. I a trying to figure out what is wrong and get it fixed. Im not sure how in the world this even happened. I do this all the time and never have issues. I am open to all suggestions. Right now i am on stock rooted MJ7 using wifi as i cant even activate the new sim she issued (I keep new ones at home) to activate as it dials USCC for some reason. Any ideas. I did enable the hidden menu if that helps
scarmon25 said:
Today for whatever reason my phone decided it didnt lke verizon anymore and decided to jump to USCC. Seriously though. I flashed the latest test build of CM 11. played with it. then wiped data and flashed CM 10.2 and booted. next thing i know it is trying to activate on USCC. So i odined to stock MDK and attempted to get it fixed. There was no help given there. Lady was really nice but still no help. I a trying to figure out what is wrong and get it fixed. Im not sure how in the world this even happened. I do this all the time and never have issues. I am open to all suggestions. Right now i am on stock rooted MJ7 using wifi as i cant even activate the new sim she issued (I keep new ones at home) to activate as it dials USCC for some reason. Any ideas. I did enable the hidden menu if that helps
Click to expand...
Click to collapse
I did the same thing and now I am stuck in roaming as well. I'm trying to restore a nandroid backup right now to see if that fixes it.
Edit: I restored from a nandroid backup and it still is stuck roaming. Even though it is roaming I have no cellular connection even though I have bars.
Same thing. I am trying to find a fix or a way to wipe the current carrier info. Or manually push the right info
Sent from my SCH-I545 using XDA Premium 4 mobile app
Fixed it. Flashed cm10.2. Set the CDMA subscription to ruin/sim and rebooted. Fixed it.
Sent from my SCH-I545 using Tapatalk
scarmon25 said:
Fixed it. Flashed cm10.2. Set the CDMA subscription to ruin/sim and rebooted. Fixed it.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
This worked for me as well. Thanks scarmon25.
I had an unlocked S4, which took an unfortunate dive and ended up non-functioning. I used my phone insurance to acquire a new (unfortuantely) updated phone running the full MK2 suite. First order of business was a root & install of SafeStrap, followed by installation of Hyperdrive to Rom Slot 1. I use my phone with my 2013 Subaru XV Crosstrek's bluetooth handsfree for both calling and media playback, and I use this feature EVERY SINGLE DAY. Unfortunately, not any more. I cannot get more than 15 seconds of connected time over bluetooth with the phone. I've tried multiple wipes. I'm fairly certain the issue doesn't exist on stock rom; so I may end up just customizing a stock rom in slot 1 by removing absolutely everything and building it from the ground up, since I don't have to use the (apparently buggy) mk2 modules.
Edit:
I'm seriously considering selling this phone and getting something more friendly to modding, this is a repeat of the Droid Bionic at this point.
Is there a question here? Did the stock rom blue tooth work ok?
Sent from my SCH-I545 using XDA Premium 4 mobile app
And this is why I shouldn't hastily write a post.
Yes there should be a question:
What can I try to fix the issue of frequent (alarmingly) bluetooth disconnects?
What kind of logging can I do to try and help provide developers with the information to fix this?
Anybody else have this problem? Any experience fixing it?
If I can't get this fixed, I have no choice but to move to another phone. Preferably at Verizon's expense.
Even more irritating: The phone is listed as compatible with the Crosstrek. I'm going to test that it works fine using the stock rom and bluetooth, and factory resetting my head unit.
Did you install the MK2 modules after installing Hyperdrive?
s.whiplash said:
Did you install the MK2 modules after installing Hyperdrive?
Click to expand...
Click to collapse
Yes. Originally when I installed it WiFi and Bluetooth didn't work at all. I realized quickly my error was the lack of installing the MK2 modules. I wiped and installed again, this time ensuring the MK2 modules followed the rom install. I got everything set up the way I like to, and began day to day use of the phone. Since then I have had the bluetooth connectivity problems I described above.
Bluetooth is rock solid on stock. I'd really rather not have to play this game where I can install stock or.... basically stock... and now that I'm locked kernel and radio wise if I have issues further with OTAs I'm just as stuck with a near useless phone as I was with my Bionic
I'm afraid that I don't have anything else for you, except try a different ROM. Bonestock or Eclipse? Bluetooth works pretty good for me with multiple headsets and vehicles. My only issue with Bluetooth is not all the apps will pass metadata to my truck. This happens with all 3 of these ROMs and I think it is a TW 4.3 limitation.
Are you doing anything to boost the Bluetooth volume? With my previous phone I boosted the Bluetooth volume via some hacks and my truck would not like it.
I know what you mean about having a locked down phone. I came to the S4 via a warranty replacement from an unlocked S3 running SlimBean and SlimKat.The problem is that most of the new phone that are coming out all have bootloader hurdles.
I'm having the same issue with my SGH-M919 (T-Mobile) running rooted stock TW. I've documented my issues and a few LogCats here. Have you figured out a solution?