Related
As the subject stated, I have enabled the "Use Wireless Networks" under Location & Security, however, Google Maps and any location-enabled apps still complaint that I need to "...enable My Location...".
Is this not working in the current version of HC or do I need to do something else?
Note that this is for location based on WIFI, not GPS since Nook Color doesn't have a GPS chipset.
Try enabling GPS if you haven't. I'm not having any trouble with both location systems turned on.
I did, and same error:
"Please enable My Location source in system settings"
FYI, I am using the following:
- Barnes and Nobles Nook Color
- Kingston 8GB Class 4 card
- Honeycomb 3.0 (Deeper Blue's Preview v04) installed on SD card (NOT internal ROM)
The Google Map application was installed separate than the Honeycomb image building. I.e. push via adb.
I'm getting the same message with both WiFi and GPS turned on.
I'm running HCv4 off a SanDisk SD with the Maps 5.0 apk (3d buildings, rotation and two-finger swipe work great)
Anyone else? Or location feature in HoneyComb for Nook Color is a known bug?
I haven't tried it on HC yet, but I did find that on CM7 the google maps location and navi only works with the settings a certain way. It may be something to do with my setup and the way other apps/settings are somehow affecting my location, but I was at work yesterday and it was showing my location as being in my apartment; which I obviously wasn't. It had done this previosly too and I never could figure it out, but I had been anywhere recently where I had a reason to use navi so I didn't mess with it a whole lot.
Yesterday I was on my lunch break and I decided I wanted to solve this issue, it was showing me as being at home when I wasn't, again. I tried clearing the app cache, data, I tried force stopping, resetting the device, and even powering off for a few minutes on both my phone and my nook. Since I couldn't figure out which device was causing the confusion about my location I tried all the above on both, but still nothing. Maps opened up and placed me at home again each time. So finally I opened maps on my Incredible and the location was right, it showed exactly where I was. Then I knew it was something to do with the nook. I went into the location settings where I had the wireless network location AND the gps satellite options checked. I unchecked the wireless network location option and force closed maps to open it again fresh. Worked right away and FINALLY didn't show the blue dot over my apartment. I used the navi on the way to work this morning just to test it and the location and everything else was perfect.
I know you are on HC and I'm not, but there are so many factors that have to be done just right it setting this up that maybe it's still just a tiny difference in your settings. Hope I helped, if even just a little bit. It seems to be that the wireless network for location was throwing mine off and giving a false reading.
Confusion
I have been trying for several day's to get the v4 to run and all I get is the locked partition error.
I have formatted the card (Patriot 16gb Class 10) several times.
It will run other roms including CM7 with out problems.
What is so different with the honeycomb one?
It doesn't work reliably but it does work on the 2nd of the eMMC Honeycomb.
Note that this is for location based on WIFI, not GPS since Nook Color doesn't have a GPS chipset.
Click to expand...
Click to collapse
BTW, you can make it work with GPS Tethering, see this:
I have that card as well. I have installed several rom's using my Win7 x64 machine. ALL worked except the Honey. I tried writing the card on my eePC Net book. running WinXP. Success and it wrote @ 14.6 MB/s. I only get 4.3 MB/s on the win7 machine.
I believe that this ROM is VERY VERY sensitive to writing speed. I will test more and see what happens. BUT, If you have access to a WINXP machine. Try it and see what you get.
Ok guys, as i'm browsing, I keep seeing the same questions over and over gain in different threads talking about Google Wallet. I want to put everything out here in one thread. Keep in mind i'm in the US, I know our foreign friends will be different as Google is still working on getting it working outside the US. So this guide is for you US peeps.
1.) Yes, GW works fine on rooted devices. A banner will show that your device is unsupported, and a warning may appear during checkout...ignore this. The app still works just fine. The reason it says "Unsupported Device" is because when you are rooted, there is a security risk for GW (just like there's one for you device as a whole).
2.) GW will not appear on the Play Store from your device. However, if you go to the Play Store on your computer, it will be there.
3.) You have heard there was an update that allowed you add all major credit cards, but you can't see how to update it. You have two options:
~a.) My most recommended option. Go to the Play website using your computer. Click on 'My Android Apps'. Choose the Asus Nexus 7. Scroll through the installed apps until you find "Wallet." Click it. Click on 'INSTALLED' and it will offer to send the update to you. Send it to your N7, you may need to be on wi-fi, I'm not sure about that. Now you'll have the other options for credit cards.
~b.) IF IF IF IF IF and ONLY IF the first option does not work, you can use the hacked apk found here. Just follow the instructions. Now if you are outside of the US, there are instructions in that thread for getting GW to work outside of the US. If you have issues, post them there so the developer can work on it. It is his apk, so he needs to know of issues, not me.
4.) You have added your credit/debit card. When you use GW, it will actually use your virtual master card that goes through Google, which will then debit from your actual card. What does this mean? It means that if you get any kind of rewards for using your card at certain places, you may not get those rewards or only part of them, as your billing statement will show that it was a Google purchase.
5.) No. You do NOT have to have a data or internet connection to use GW.
So there you have it. And just point out the most frequently asked questions: no data/internet required, works on rooted devices regardless of the warnings you see, only shows up in the Play Store on your computer browser. There, those have been repeated twice, so you should not be asking anymore
That's awesome. I'd added a card online, deleted an old one, but the damned app on my N7 just showed a Citi card, and no option to update. I felt retarded... I'm glad this is finally set up. Thanks.
My N7 is rooted. I've installed the latest wallet and I've entered one of my credit cards. When I did that I got an email from google stating that my wallet was set up and ready to go. To test it I should open wallet and tap my card to authorize its use. It doesn't matter how much I tap, touch, or rub the card on the N7 it doesn't appear that it is reading my card.
Is it working properly? I'd kinda like to test it out before I actually take it in someplace and try to use it.
ba_hamilton said:
My N7 is rooted. I've installed the latest wallet and I've entered one of my credit cards. When I did that I got an email from google stating that my wallet was set up and ready to go. To test it I should open wallet and tap my card to authorize its use. It doesn't matter how much I tap, touch, or rub the card on the N7 it doesn't appear that it is reading my card.
Is it working properly? I'd kinda like to test it out before I actually take it in someplace and try to use it.
Click to expand...
Click to collapse
Is your card a paypass card? Never seen it ask to tap the card to the phone. Not sure why it would, frankly.
I was about to say the same thing. You can't tap just any ole card. Doesn't work that way. The card needs to have an RFID chip in it, or some sort of NFC chip. Someone correct me if i'm wrong.
Installed yesterday from the link that was posted and this is what I get.
Thoughts?
Sent from my Nexus 7 using Tapatalk 2
I am not rooted and I tried it at a Walgreens, but it didn't do anything. Can someone explain in elementary steps how it actually works when using it at a store? I just figured I had to have a data connection and that is why it didn't work, but this guide says otherwise.
Thanks for your help!
First, download the PayPass locator to find which stores near you actually have a console that is compatible with the device. Some Walgreens DO NOT have the mastercard paypass system. They have some other kind of technology. I tried at a walgreens by my place and felt foolish when the girl just looked at me weird.
You can use this at ALL McDonald's. Go there and order something. Turn your device on. Make sure NFC is enabled in the settings. You don't need to have wallet open already, but it would speed up the process. If you don't have it open, but with the phone screen turned on, rest the back of the device to the paypass surface. They need to be physically touching. You may need to move the device around just a bit. You will hear a ringing noise, and then google wallet will be active. It will ask you to type in your PIN and the press the device to the surface to complete the transaction. Sometimes you have to tell the person at the cash register that you are paying with credit. Once you tap it a second time to the surface of the paypass thing, it will say transaction complete.
NOW, sometimes it doesn't work 100% flawlessly. SOMETIMES you have to tap the device to the pad over and over again. Or move it around on top of the pad until it goes through. And sometimes, even tho it goes through on the end of the cash register, the device still tells you that the transaction may not have gone through. If the person smiles at you and gives you your receipt, it went through just fine. But the device will ask you to tap the paypass pad again. Just take the receipt and wink at the person if they are cute because they have never seen it before and they are probably blown away by it.
Oh, and even though people say that you don't need a data connection to use it, I have always been connected via wifi to my phone or the wifi at the restaurant when I use it.
One more question, I am getting annoyed by the "you need flash blah blah blah", so I am going to root.
In the past I thought I saw articles saying something about resetting google wallet before you root or it messes it up, but when I go into Wallet to reset it - I don't see that option.
Is this something that is still required? If so, what are the steps?
I was under the impression that you don't need a wi-fi connection to complete a transaction at a PayPass terminal. Has anyone used it successfully knowing there was no wi-fi connection?
Heaterz16 said:
One more question, I am getting annoyed by the "you need flash blah blah blah", so I am going to root.
In the past I thought I saw articles saying something about resetting google wallet before you root or it messes it up, but when I go into Wallet to reset it - I don't see that option.
Is this something that is still required? If so, what are the steps?
Click to expand...
Click to collapse
From Google wallet, go into the menu from the google wallet home screen. The three dots up in the right hand corner. Then settings. Then reset google wallet.
You do not need a wifi / data connection ! How many times does this need to be stated?!
Groid said:
I was under the impression that you don't need a wi-fi connection to complete a transaction at a PayPass terminal. Has anyone used it successfully knowing there was no wi-fi connection?
Click to expand...
Click to collapse
.....................really dude? Did you read the whole thing? I even said it twice. Let me quote myself:
5.) No. You do NOT have to have a data or internet connection to use GW.
So there you have it. And just to point out the most frequently asked questions: no data/internet required, works on rooted devices regardless of the warnings you see, only shows up in the Play Store on your computer browser. There, those have been repeated twice, so you should not be asking anymore
Click to expand...
Click to collapse
See? I put it in there twice. I'm not trying to be a jerk, I just have little patience for people who don't read and ask questions that were already answered. Hope the bluntness gets the point across so this doesn't happen in the future, that's all.
adamhlj said:
From Google wallet, go into the menu from the google wallet home screen. The three dots up in the right hand corner. Then settings. Then reset google wallet.
Click to expand...
Click to collapse
I can't believe I didn't see that until now, I tried that about 4 times using the menu button but it never had the settings option....before I realized I was within a card which didn't have that option. I had to hit the back button twice to get to the "homepage" of the app, then I saw the settings, reset option...
Thanks!
Thanks OP. Your method of updating the app worked flawlessly for me. Now I added another card. Can't wait to try this out.
Quick question: lets say I get a galaxy S3, it has Google wallet on it or I install it(I believe that device has nfc also, all I would have to do is sign in and data transfer KR copies to new device? Or will I have to set THST device up all over again ?
Here's an odd question:
Let's say you're at the end of your funds on your debit card, and you don't want to charge the whole amount on your (different)credit card. Is there a way to use Google Wallet to pay out the last of the debit card's funds, THEN cover the balance of the purchase with the credit card?
matrix0886 said:
~b.) IF IF IF IF IF and ONLY IF the first option does not work, you can use the hacked apk found here. Just follow the instructions. Now if you are outside of the US, there are instructions in that thread for getting GW to work outside of the US. If you have issues, post them there so the developer can work on it. It is his apk, so he needs to know of issues, not me.
Click to expand...
Click to collapse
I'm running Team EOS Rom build 19.
Nothing else would work for me, so I did this method.
I have tried installing it by just tapping the apk and I have also put the apk in /system/apps and set permissions. No matter how I do it, I always get this.
Any thoughts?
I can verify that this works when rooted on the stock ROM AND WITHOUT INTERNET CONNECTION. When I have used it on my Nexus 7, I have had the app open as it will ask you to put in your PIN number on the device.
Few things to make sure you have done before scanning. Make sure you have a card selected before hand WHICH DOES REQUIRE INTERNET CONNECTION. I have tried to scan my Nexus 7 and Galaxy S III without a card selected (although I'm not sure why the card was deselected) and neither would work.
When you scan the device at the NFC point of sale, make sure you center the "U" in "Nexus" on the back of your device over the scanning area (this is according to the instruction manual on the device). You can test this for yourself if you have another NFC capable device, using Android Beam. You will find that the scanning range of the NFC is very specific on both devices.
Sometimes, it will take a little bit of time for the device to be scanned and for the transaction to be completed. You will hear a sound from your device indicating that the NFC has been scanned, after which the Google Wallet app will pop up prompting you to put in your PIN or that the transaction has been completed, showing you a receipt.
matrix0886 said:
.....................really dude? Did you read the whole thing? I even said it twice. Let me quote myself:
See? I put it in there twice. I'm not trying to be a jerk, I just have little patience for people who don't read and ask questions that were already answered. Hope the bluntness gets the point across so this doesn't happen in the future, that's all.
Click to expand...
Click to collapse
I read the OP entirely and thought, hooray! In post 7 someone said his didn't work and questioned the data connection. Post 8 said he was successful and stated he had a wi-fi connection with his phone at the time. No one before my post had verified wi-fi or data was not needed except the OP. Trust, but verify. I just wanted one other person to say it worked.
Just curious if there was a way to reload the virtual card without having another credit/debit card added as an available card in GW? Is there a phone number or website where we could add funds, so the virtual card is the only card listed in GW?
Sent from my Nexus 7 using Tapatalk 2
Would greatly appreciate any assist with the following:
I have the following issue with my N2A powered Nook HD+. I have been using the N2A card exclusively for several months with almost flawless performance. However, I have recently run into the following issue with a successfully d/l and installed Zinio for Android app: "Failed to connect to the server. Please move to an area with a stronger wireless signal and try again." This happens no matter what my location is! I have a very solid, strong, and fast connection with all of my other apps.
Zinio says that it is because I am using a Nook (even though configured as an Android tablet) the app will not work and is not supported on that device. Here is the tech ass't manager's reply after I had several back and forths with a level one tech at Zinio:
"I apologize for any inconvenience. Zinio will not work properly on a Nook
device. If you are able to install the app, you will receive an error message
regarding not being able to connect to the internet -- this is normal behavior.
This is not something that we can resolve because Nook will not allow Zinio to
be used on their devices. There is no workaround that will fix this issue."
I had repeatedly explained to them in increasing detail that I was not using the BN software and that this issue was not displayed by any other app!
Their app d/l without any warning of conflict. It installed properly. It even starts up and displays its structure with no problem except for the all-important failure to connect.
Since everything else works just fine, what is the connection only issue? I have an online subscription to Aviation Week & Space Technology which is accessible only through Zinio. Desktop version is not a problem but I want to be able to access this on my HD+ which has the perfect screen size for it!
Thanks in advance.
Turns out that changing the identity of the HD+ to asus/Nexus 7 did the trick. Familiar with this process from my original NC days.
harryzee said:
Would greatly appreciate any assist with the following:
I have the following issue with my N2A powered Nook HD+. I have been using the N2A card exclusively for several months with almost flawless performance. However, I have recently run into the following issue with a successfully d/l and installed Zinio for Android app: "Failed to connect to the server. Please move to an area with a stronger wireless signal and try again." This happens no matter what my location is! I have a very solid, strong, and fast connection with all of my other apps.
Zinio says that it is because I am using a Nook (even though configured as an Android tablet) the app will not work and is not supported on that device. Here is the tech ass't manager's reply after I had several back and forths with a level one tech at Zinio:
"I apologize for any inconvenience. Zinio will not work properly on a Nook
device. If you are able to install the app, you will receive an error message
regarding not being able to connect to the internet -- this is normal behavior.
This is not something that we can resolve because Nook will not allow Zinio to
be used on their devices. There is no workaround that will fix this issue."
I had repeatedly explained to them in increasing detail that I was not using the BN software and that this issue was not displayed by any other app!
Their app d/l without any warning of conflict. It installed properly. It even starts up and displays its structure with no problem except for the all-important failure to connect.
Since everything else works just fine, what is the connection only issue? I have an online subscription to Aviation Week & Space Technology which is accessible only through Zinio. Desktop version is not a problem but I want to be able to access this on my HD+ which has the perfect screen size for it!
Thanks in advance.
Click to expand...
Click to collapse
Odd! I'm running Zinio with no problems at all on both my rooted HD and HD+ running stock.
I do remember having that error massage a some point while running CM10.1 from sd-card on my Nook Tablet though.
Glad you got it sorted!
asawi said:
Odd! I'm running Zinio with no problems at all on both my rooted HD and HD+ running stock.
I do remember having that error massage a some point while running CM10.1 from sd-card on my Nook Tablet though.
Glad you got it sorted!
Click to expand...
Click to collapse
It runs fine on rooted stock and has for awhile. It's just in CM10 and CM10.1 that this problem exists. I think Zinio is full of it when it comes to the reason it isn't working.
I need to spend more time looking in to this but I have just been to busy to do it.
" I think Zinio is full of it when it comes to the reason it isn't working."
Keep in mind the following:
1. Zinio d/l from GP with no error messages regarding the tablet type.
2. The install after the d/l went off without a hitch.
3. When opening Zinio, the app structure appeared.
4. The "only" problem was the weak wifi/ can't access server" message.
Thanks for the moral support and could not have stated it better myself!
However, now that v2.1 of the stock BN software includes Google Play access, all of this might be moot. Evidently Zinio does work with this new update. As I have never tweaked the internals of my HD+, will definitely give this a try and see how well things work.
While I would prefer using 4.1, living with full access to GP under 4.0.4 might be doable. As long as I can access HBOGo, I would be thrilled!
harryzee said:
" I think Zinio is full of it when it comes to the reason it isn't working."
Click to expand...
Click to collapse
I'm inclined to agree! Their explanation" doesn't make sense!
harryzee said:
Turns out that changing the identity of the HD+ to asus/Nexus 7 did the trick. Familiar with this process from my original NC days.
Click to expand...
Click to collapse
I have ran into exactly the same issue...with stock nook hd+ i can use zinio but with CM 10 it gives the network error.
Can you please share how you changed the identity of the HD+ to asus/nexus?
Finally - Zinio running on my Nook HD runing Android 4.4.4
i_m_jughead said:
I have ran into exactly the same issue...with stock nook hd+ i can use zinio but with CM 10 it gives the network error.
Can you please share how you changed the identity of the HD+ to asus/nexus?
Click to expand...
Click to collapse
Finally - Zinio running on my Nook HD runing Android 4.4.4
When I tried to run Zinio on my Nook HD under Android 4.4.4 (booted from the SD Card) I got a "Warning Zinio server not available..." even though Zinio ran fine from stock Nook HD. After I read harryzee's earlier posts (#1, #2) I wasn't sure how to change the identity. I finally figured out how - and Zinio ran without any problems. See how I did it below.
Nook HD running CM11 ROMS (KitKat 4.4.4) from the SD Card
Thanks to bokbokan for instructions on getting CM11 ROMS (KItKat 4.4.4) on my Nook HD loading from the SD Card. http://forum.xda-developers.com/showthread.php?t=2583952
Changing the Identity of my Nook HD
After looking for a while, I found the simplest instructions on how to change the identity posted by Timit on the AFN forum http://www.androidfornook.com/forum/thread-626-page-2.html
RE: Zinio Problem with JB Internal Install
This is probably the easiest workaround that I have ever performed. Using information that I gleaned from N2A forums and XDA Developers forums,
I was able to get Zinio working on JB 4.2.2 in about 10 minutes. Here are the steps that I followed:
1) Make sure that Zinio is NOT installed on your NT
2) Download Build Prod Editor from Google Play.
3) Start up Build Prod Editor.
4) Tap ok on the information screen that pops up.
5) Scroll down the list of properties until you see "ro.product.model"
6) Tap on "ro.product.model"
7) In the pop up window that appears tap the Property Value box.
8) Enter "nookhdplus" - without quotes.
9) Click Save.
10) It should ask if you want to reboot, if it does tap yes. If it doesn't ask then reboot the NT yourself.
11) Once the NT reboots go to Google Play and download Zinio.
This is all I had to do. Really easy. I was reading my magazines in probably 20 minutes.
Now the disclaimer.
FOLLOW THIS PROCESS AT YOUR OWN RISK.
I am just an average Joe who BADLY wanted Zinio to work. I am not sure if this will have any adverse effects on your NT but I am not responsible if something goes awry.
I hope this works for you and that you enjoy running Zinio on your Nook HD!
Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?
Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app
I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.
Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone
Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.
I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app
I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.
Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.
Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay
My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.
My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)
Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk
After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.
Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!
Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.