I discovered a bug on the S5.
NFC deactivates itself.
For example: I installed "banking card reader" from Google Play.
I turn on NFC. I read a NFC tag.
Android says that NFC is still on. BUT IT IS NOT.
I try to read a new NFC tag and nothing happens (this proves that NFC is off).
If I turn off NFC, and turn on NFC again, I can again read ONE NFC tag.
Android says that NFC is still on. BUT IT IS NOT.
I try to read a new NFC tag and nothing happens (this proves that NFC is off again).
I think you understand what I mean.
This happens also when power saving is OFF. This happens also when the battery is FULL.
I have no clue how to stop NFC from deactivating itself.
Does NFC deactivate itself also on your S5???
If you can read a NFC tag MORE THAN ONCE in sequence, it means NFC does not deactivate itself on your S5.
Android Friend said:
I need help about a bug I discovered on my S5.
NFC deactivates itself.
For example: I installed "banking card reader" from Google Play.
I turn on NFC. I read a NFC tag.
Android says that NFC is still on. BUT IT IS NOT.
I try to read a new NFC tag and nothing happens (this proves that NFC is off).
If I turn off NFC, and turn on NFC again, I can again read ONE NFC tag.
Android says that NFC is still on. BUT IT IS NOT.
I try to read a new NFC tag and nothing happens (this proves that NFC is off again).
I think you understand what I mean.
This happens when power saving is OFF. This happens when the battery is FULL.
I have no clue how to stop NFC from deactivating itself.
Does NFC deactivate itself also on your S5???
If you can read a NFC tag more then once, it means your NFC does not deactivate itself.
Click to expand...
Click to collapse
mine works on my passport all the time.
fyi bug reports should be emailed to samsung not put here
-PiLoT- said:
mine works on my passport all the time.
Click to expand...
Click to collapse
You have a SM-G900F with Firmware J1 and you can read your passport once, or: more than once in sequence?
The bug is: not being able to read MORE THAN one tag, or: not being able to read one tag MORE THAN ONCE IN SEQUENCE.
Hope the bug is clear now.
I am not sure whether this is a software of hardware bug. It may even be a "feature" and not a bug. LOL!
-PiLoT- said:
fyi bug reports should be emailed to samsung not put here
Click to expand...
Click to collapse
fyi1: XDA rules do not forbid discussion about possible Android software bugs. Do not censor me.
fyi2: Do not moderate. You are a RETIRED moderator.
Android Friend said:
You have a SM-G900F with Firmware J1 and you can read your passport once, or: more than once in sequence?
The bug is: not being able to read MORE THAN one tag, or: not being able to read one tag MORE THAN ONCE IN SEQUENCE.
Hope the bug is clear now.
I am not sure whether this is a software of hardware bug. It may even be a "feature" and not a bug. LOL!
Click to expand...
Click to collapse
Im on ANG2 and it can read as many times as i put the phone on the pasport or any other nfc
Android Friend said:
fyi1: XDA rules do not forbid discussion about possible Android software bugs. Do not censor me.
fyi2: Do not moderate. You are a RETIRED moderator.
Click to expand...
Click to collapse
FYI1: XDA rules do not forbid discussion about where to file bug reports. i was simply saying if you have an actual bug tell people here sure but make sure to email samsung aswell
FYI2: you original post wasnt censored in anyway, again moderation doesnt equal to offering help and advice
-PiLoT- said:
Im on ANG2 and it can read as many times as i put the phone on the pasport or any other nfc
Click to expand...
Click to collapse
Many people complain about the NFC bug I am talking about.
As you can read here:
forums.androidcentral.com/samsung-galaxy-s5/383092-nfc-turning-off-itself.html
Why do we have it, and you dont?
Are you using a SM-G900F?
Are you rooted?
Is your knox disabled?
Do you use fingerprint unlock?
Android Friend said:
Many people complain about the NFC bug I am talking about.
As you can read here:
forums.androidcentral.com/samsung-galaxy-s5/383092-nfc-turning-off-itself.html
Why do we have it, and you dont?
Are you using a SM-G900F?
Are you rooted?
Is your knox disabled?
Do you use fingerprint unlock?
Click to expand...
Click to collapse
im g900f rooted knox is flagged yes i use fingerprint stuff
-PiLoT- said:
im g900f rooted knox is flagged yes i use fingerprint stuff
Click to expand...
Click to collapse
Are you using a stock samsung rom or a custom rom?
Android Friend said:
Are you using a stock samsung rom or a custom rom?
Click to expand...
Click to collapse
i already said i use ANG2
This is so strange. I don't understand the cause of this.
Will try to research the problem further.
Nobody else here is having this NFC bug? Did anyone find a solution?
For the record I have experienced this this issue before, I used to use NFC Tags at home, at my work and in my car with my old galaxy nexus but that's an impossible task with my S5 (GM900M), the NFC keeps disabling itself it is a annoying to turn it on every time I want to use a tag. I am NOT rooted, knox is 0x0, and stock rom, in other words my S5 is a virgin. This could not be an issue but a security feature, by disabling NFC the system avoids the chance of getting info stole.
Same here, you can turn off the screen and it would work again
Having the same issue. NFC would work once then stop. i can either turn it off then back on. it would scan once then stop.
Turning the screen off then on, i can scan an NFC tag ONCE, then it stops working. very annoying.
Samsung Galasy S5
Model: SM-G900F
Android version: 4.4.2
Build number KOT49H.G900FXXU1ANG2
Stock, did not root.
fyi: fingerprint auth is on
Related
Hi,
So I've noticed alot of people have problems with their GPS from time to time on these forums so I've decided to collate any and all fixes into one place. Here they are:
NOTE: I'm not responsible for any harm done to your phone. These suggestions are tried at your own risk. These steps can be taken in any order you want and a reboot is recommended after you try each step.
First thing you can do to get accurate fixes is to go to the Location settings on your phone. Tick the boxes next to 'GPS Satellites' and 'Google's location service' (Press agree when the prompt comes up). Also click 'GPS Source' and make sure 'Use Internal GPS' is selected.
Click to expand...
Click to collapse
Second thing you can do is download the 'GPS Status & Toolbox' app from the market. Once installed go into the app and hit Menu and then select Tools. From the popup menu select Manage A-GPS state. Select Reset and then Download. Reboot and see if you can get a fix now.
Click to expand...
Click to collapse
It is recommended you have a Nandroid backup before trying anything below.
Third thing you can do is download this GPS Fix made for the Legend (From Kot_Ik’s CM7.2 unofficial thread). Put it on your SDCard and reboot to recovery and flash it.
Click to expand...
Click to collapse
Fourth thing you can do is flash a new radio in recovery. Get one from here. Try the bottom 2 first before trying the top one. This doesn't seem to be supported in the latest versions of CWM so you should load an earlier fake flash zip file. Go here for the recovery and instructions (Thanks ranger4740)
Click to expand...
Click to collapse
Last thing I can think of is to change ROM's and see if that fixes anything.
Click to expand...
Click to collapse
That's all folks. If you're reading this part and your GPS still isn't working then I've got no idea what's going to fix it
smithchipz said:
Third thing you can do is download this GPS Fix made for the Legend. Put it on your SDCard and reboot to recovery and flash it.
Click to expand...
Click to collapse
This is not needed for old stable releases and was fixed a few weeks ago (so recent RCs and nightly builds already contain that bugfix).
smithchipz said:
Fourth thing you can try is download a gps.conf file from here that's related to your country/continent and flash it in recovery.
Click to expand...
Click to collapse
All of the files I checked there are invalid.
ali ba said:
This is not needed for old stable releases and was fixed a few weeks ago (so recent RCs and nightly builds already contain that bugfix).
All of the files I checked there are invalid.
Click to expand...
Click to collapse
Ali Ba, as you are the legend master, can you please explain why my legend could never achieve GPS lock on ANY version of CM, stable or not, no matter how long my phone tried until I started using the GPS fix mentioned above. I ask because you are the master, and you did say its not nessasary. So that advice is a bit confusing.
Thank you
sent from my legend using zeubeas cm9 beta2
ali ba said:
All of the files I checked there are invalid.
Click to expand...
Click to collapse
Hello ali ba,
can you explain, how a valid gps.conf looks?
alligator_asl said:
can you explain, how a valid gps.conf looks?
Click to expand...
Click to collapse
It is a config file parsed per line. This means that there shouldn't be any new line characters for lines that the system has to interpret as one.
It's perfectly OK to use a local NTP-server, by the way. It just doesn't fix problems at all. The short differences in the time the packets take to be sent and received are eliminated by the NTP protocol anyway.
Most so called "GPS fixes" are bogus at best (using the newest baseband firmware is something I'd recommend though).
ranger4740 said:
Ali Ba, as you are the legend master, can you please explain why my legend could never achieve GPS lock on ANY version of CM, stable or not, no matter how long my phone tried until I started using the GPS fix mentioned above. I ask because you are the master, and you did say its not nessasary. So that advice is a bit confusing.
Thank you
Click to expand...
Click to collapse
Everything I say is right so you are wrong per definition. Also, I'm the reincarnation of an ancient demigod and I'll send a shipload of trained African killer bees to decompose your cell phones after you should you dare to question me. Any more questions?
ali ba said:
Everything I say is right so you are wrong per definition. Also, I'm the reincarnation of an ancient demigod and I'll send a shipload of trained African killer bees to decompose your cell phones after you should you dare to question me. Any more questions?
Click to expand...
Click to collapse
Well, good question by ranger4740, but bad answer...
This fix gps.agps.legend.zip is not for CM9. If you flash this, you are flashing a lib which nobody knows where is from.
zeubea said:
This fix gps.agps.legend.zip is not for CM9. If you flash this, you are flashing a lib which nobody knows where is from.
Click to expand...
Click to collapse
Sorry the fix is from Kot_Ik’s CM7 thread. Updated the post to show this.
Sent from my Legend using XDA
Exactly, it is for CM7 Kot_Ik, because it is built in that rep for that version, only clarifying for avoid to see posts from people flash CM7 libs on CM9, because it is not the way.
smithchipz said:
Sorry the fix is from Kot_Ik’s CM7 thread. Updated the post to show this.
Sent from my Legend using XDA
Click to expand...
Click to collapse
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
EDIT: after updating from latest to newest radio (now useing 47.26.35.04_7.05.35.26L) it can't even find any satelites, earlier it was finding up to 13-14.... I've reset and downloaded A-GPS state..... and still nothing
maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
Click to expand...
Click to collapse
I'm not sure apart from all the steps I listed in first post. Sorry :/
maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
EDIT: after updating from latest to newest radio (now useing 47.26.35.04_7.05.35.26L) it can't even find any satelites, earlier it was finding up to 13-14.... I've reset and downloaded A-GPS state..... and still nothing
Click to expand...
Click to collapse
Ok, what I have noticed so far using legend. Don't mess with gps.conf using other custom gps.conf I've use some before (instant lock) and its bogus as Ali ba put it.
Just use faster fix is enough.
OK, now currently I'm on zuebes cm9 and GPS works but getting it to lock is something else. And I love my waze.
I'll get in my car and start waze. Wait for a minutes or 2 than start moving. Lock or no lock, just start moving. Don't drive so fast but stay constant either 40kmh or 60kmh will do just fine. My lock usually happens when I stop at a junction or a traffic light or slow down before a corner.
Then when you lock for the first time. You can combo for the next trip as long as you on your waze at the same spot before leaving. It's instant lock for some cases but need to start over if it does not lock. Assume you use waze.
But if GPS is important. Use stock based rom and ogo2s rom also have good GPS if I remember well... I think its something about HTC didn't release GPS source that we ended up like this.
Sent from my Legend using Tapatalk 2
Alright I've changed the post and removed the step about changing the gps.conf.
maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing
Click to expand...
Click to collapse
I'm sorry that it broke your device, but I can't do more than pointing out that these files are invalid.
Oops... said:
Well, good question by ranger4740, but bad answer...
Click to expand...
Click to collapse
So I point out that these files are not only useless (as most GPS fix instructions are) but also broken and invalid and what do I get? Some random guy jumping at me telling me how stupid I am because GPS coincidentally started working on his device after doing some useless things?
You know, that's not even something I have to do (as if I was getting paid for support), I'm doing it because I'm basically a nice guy.
And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
psyionx said:
Ok, what I have noticed so far using legend. Don't mess with gps.conf using other custom gps.conf I've use some before (instant lock) and its bogus as Ali ba put it.
Click to expand...
Click to collapse
Thank you for actually reading what I write.
psyionx said:
I think its something about HTC didn't release GPS source that we ended up like this.
Click to expand...
Click to collapse
That's right. There's a bug somewhere in the GPS module but we never got any sources so we don't really know how to work around it. The GPS module on the Legend doesn't have public sources so we hacked together some code from different versions. It works pretty well - once it starts working.
I sometimes can't get a GPS fix either when I started the device with GPS turned off or after toggling GPS a few times. Yeah, it is broken and I am aware of that.
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Using the latest radio (=baseband firmware) for your region has been reported to kickstart GPS as well. That's the only fix I can confirm, everything else is shenanigans and you should get your money back .
ali ba said:
I'm sorry that it broke your device, but I can't do more than pointing out that these files are invalid.
So I point out that these files are not only useless (as most GPS fix instructions are) but also broken and invalid and what do I get? Some random guy jumping at me telling me how stupid I am because GPS coincidentally started working on his device after doing some useless things?
You know, that's not even something I have to do (as if I was getting paid for support), I'm doing it because I'm basically a nice guy.
And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
Thank you for actually reading what I write.
That's right. There's a bug somewhere in the GPS module but we never got any sources so we don't really know how to work around it. The GPS module on the Legend doesn't have public sources so we hacked together some code from different versions. It works pretty well - once it starts working.
I sometimes can't get a GPS fix either when I started the device with GPS turned off or after toggling GPS a few times. Yeah, it is broken and I am aware of that.
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Using the latest radio (=baseband firmware) for your region has been reported to kickstart GPS as well. That's the only fix I can confirm, everything else is shenanigans and you should get your money back .
Click to expand...
Click to collapse
By quoting me you are implying I'm some one that only knows how to register and start attacking people, how did I attack you, most people here know your the master who gave us all cm for our legend which is wonderful, and I simply asked you as you are the expert to explain how? Then you come back with your B.S answer attacking me, for no real good reason Instead of explaining humanly the answer, you also imply I attack people, when all I do here is try and learn to do stuff, and help others when I can.
Any way best you add me to your ignore list then you won't have to see me attack and abuse every one on xda developers ever again! Hey better still report me to the mods and get me permanently band from xda forums if you've seriously got some evidence of constaintly attacking members.
Sent from my Legend using XDA
ali ba said:
... And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
Click to expand...
Click to collapse
Calm down. Nobody attacks people. I appreciate your work concerning the Legend port - and stated that several times.
Not giving an answer is ok - as you said, no paid support.
However, I can't agree on statements like ...
ali ba said:
... Everything I say is right so you are wrong per definition. ... Any more questions?
Click to expand...
Click to collapse
as they are rude by definition. No more questions ...
btw, thanks for clarification
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Click to expand...
Click to collapse
ugh! this is unnecessary fighting, ali ba might just misunderstood ranger4740 questions, cos it sound corny at first look but if you read it again it's just a genuine question.
about gps fixes, we should trust the expert, yes this won't work as ali ba said there's some bugs in gps module. This fixes might work on other devices but I wonder if it does anything for our Ancient Legend
homi3kh said:
ugh! this is unnecessary fighting
Click to expand...
Click to collapse
Agree. Back on topic
...So I am using Zeubea's ICS ROM (BETA3) and my GPS isn't working.
I have refreshed the AGPS-data and flashed the newest (?) radio (7.13.35.05).
In what way is the radio dependent on my geographical location? I live in Sweden, am I using the correct radio?
I get no lock, but I get accuracy of roughly 2km. How is this?
Also, I'm searching for an app to see how many satelites I am connected to, havn't found one yet.
Any help in this would be greatly appreciated - thank you in advance ♥
MarkInDaPark said:
...So I am using Zeubea's ICS ROM (BETA3) and my GPS isn't working.
I have refreshed the AGPS-data and flashed the newest (?) radio (7.13.35.05).
In what way is the radio dependent on my geographical location? I live in Sweden, am I using the correct radio?
I get no lock, but I get accuracy of roughly 2km. How is this?
Also, I'm searching for an app to see how many satelites I am connected to, havn't found one yet.
Any help in this would be greatly appreciated - thank you in advance ♥
Click to expand...
Click to collapse
try using mobile data to get a good starting point (google's location service), also check gps source in location settings, and then try to get the precise location somewhere with a good view of sky....every next time it'll be faster, (you can even disable google's location service if you don't like it being turned on,it should still work faster than the first time after flashing)
edit: i just tried what i wrote above and got fix in no time,even from my room,using zeubeas cm9 beta3 freshly flashed... so, enable mobile data for a brief time until you get gps lock then you can disable it if you wish
I was looking into NFC and what things you can do with it. I found it pretty interesting and wanted to try it out. I did some google searching to see what the status is on the Samsung Captivate i-897 and found the wiki here. It states that the NFC is "Not Known"
Now is there a possibility to get it working some how? Or should I hold off on getting those NFC tags?
I think it would be pretty cool to set them up all over the place.
Ronin_Spartan said:
I was looking into NFC and what things you can do with it. I found it pretty interesting and wanted to try it out. I did some google searching to see what the status is on the Samsung Captivate i-897 and found the wiki here. It states that the NFC is "Not Known"
Now is there a possibility to get it working some how? Or should I hold off on getting those NFC tags?
I think it would be pretty cool to set them up all over the place.
Click to expand...
Click to collapse
I'm not sure if the Cappy can have it but it would need to be built in the kernel if I remember right and it's not something that has been done for the Captivate yet (if ever).
sgh-i897 does not have NFC hardware. you can't flash it to make it operate as an NFC device.
http://en.m.wikipedia.org/wiki/Near_field_communication
NFC is an extension of RFID technology. it operates by using inductive loops that communicate at a different frequency and rate than bluetooth, wifi, or cellular data networks.
Sent from my SGH-I897
Hi all,
I'm having problems with NFC in my HTC One and perhaps you can help me in order to solve them.
I mean, I bought NFC tags (Myfare Classic 1K), and initially I worked with them very well using NFC Task Launcher and Tasker. My issue is that I can read these tags sometimes... but sometimes no. It's frustating. Of course I have activated NFC option in my mobile and I put it close to the NFC tag using the area of the rear camera (where is located the antenna).
I try to connect with my new bluetooh headphones by NFC (Sony MDR-1RBT) and sometimes connect... sometimes no.
My HTC One is not rooted and bought free.
Any idea? Help please.
Thanks a lot!!
You probably have the same issue as I do. We've got faulty NFC chips. I'm sending mine in for warranty soon
I looked for information about NFC problems with HTC One but I didn't found nothing. Bad NFC Chips? Oh my God! Is this usual and reported?
I thought that perhaps it would be something related to software (i.e. some process running in background)... but if we are talking about a hardware issue I'm going to worry a lot.
Could we expect news with new release of android? What do you think?
Thaks a lot for your answer!
Best regards
Did you unlock your screen before using the tag? U must unlock first or the tag wont work
Yes, I try it after unlocked screen. I am not able to say when NFC fails or woks, but I try to read tags with unlocked screen.
Thanks
cta1234 said:
Yes, I try it after unlocked screen. I am not able to say when NFC fails or woks, but I try to read tags with unlocked screen.
Thanks
Click to expand...
Click to collapse
For me, mine I think is a little loose. I cna read NFC tags if I put it near my camera and press it really hard against the phone. That seems to push the NFC chip back into place and I hear the "Boop" when it detects the chip. A fully working will beep instantly upon contact.
ArmedandDangerous said:
For me, mine I think is a little loose. I cna read NFC tags if I put it near my camera and press it really hard against the phone. That seems to push the NFC chip back into place and I hear the "Boop" when it detects the chip. A fully working will beep instantly upon contact.
Click to expand...
Click to collapse
Obviously that would mean a hardware issue. In my case, doing always the same I get different results. I don't press the tag against the phone, and trying with the same tag I don't get the same result (sometimes reads the tag and sometimes not). It's crazy.
I haven't been able to get nfc to work either. I don't have any proper tags but I tried my MasterCard paypass that worked fine in the past. Can somebody with working NFC try to scan their MasterCard with paypass and let me know if it works?
Sent from my HTC One using Tapatalk 4 Beta
NFC on HTC One has issues. My device for one doesn't show any NFC icon on the status bar when switched ON and there is no Android beam option at all. Please share any information on the NFC feature in this thread. Thanks
phsetaknev said:
NFC on HTC One has issues. My device for one doesn't show any NFC icon on the status bar when switched ON and there is no Android beam option at all. Please share any information on the NFC feature in this thread. Thanks
Click to expand...
Click to collapse
And what kind of issue is that ? Mine doesn't show it too and I'm very happy it doesn't (why would one want another place in status bar taken ?). Also, why do you need Android Beam option ? If you tick the NFC option, everything works as it's supposed to, doesn't it ?
Well i tried with other phones, it doesn't detect my phone, i tried with other HTC One user too.........will it detect like bluetooth or should we add the devices and thereon proceed? But i've seen in forums with other users getting this icon, so i thought mine isnt working. I tried to pair with Sony devices and it didnt detect mine.
phsetaknev said:
Well i tried with other phones, it doesn't detect my phone, i tried with other HTC One user too.........will it detect like bluetooth or should we add the devices and thereon proceed? But i've seen in forums with other users getting this icon, so i thought mine isnt working. I tried to pair with Sony devices and it didnt detect mine.
Click to expand...
Click to collapse
Mine doesn't show the icon as well and everything works fine (GSM 4.2.2). I can use NFC in order to connect and beam to my galaxy nexus without problems. The only thing is that the NFC chip in the One sits right behin the camery, while in other phones its inside the battery. So you have to position the phones right.
wictor1992 said:
Mine doesn't show the icon as well and everything works fine (GSM 4.2.2). I can use NFC in order to connect and beam to my galaxy nexus without problems. The only thing is that the NFC chip in the One sits right behin the camery, while in other phones its inside the battery. So you have to position the phones right.
Click to expand...
Click to collapse
Just now tried with XperiaS..... it doesn't even detect, the range for NFC to work should be 20cms right? I tried with other HTC One as well.
phsetaknev said:
Just now tried with XperiaS..... it doesn't even detect, the range for NFC to work should be 20cms right? I tried with other HTC One as well.
Click to expand...
Click to collapse
20 cm? Not really. 20 mm maybe.
Hold the phones back to back.
I think there isnt a 'n' logo in 4.2.2 because a lot of people who updated to 4.3 from it were asking what the n logo was but still nfc is on just no status bar logo?
Sent from my HTC One using XDA Premium 4 mobile app
wictor1992 said:
20 cm? Not really. 20 mm maybe.
Hold the phones back to back.
Click to expand...
Click to collapse
Yeah i guess its 20mm, it worked fine when i joined the nfc modules face to face without any distance it worked, with Xperia S. :good:
nathlynn22 said:
I think there isnt a 'n' logo in 4.2.2 because a lot of people who updated to 4.3 from it were asking what the n logo was but still nfc is on just no status bar logo?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On my GSM One this N(escafe)-icon was added with 4.2.2 update, but it has been removed by a minor update only some days later. Maybe some carrier models didn't receive that minor update or skipped the first one.
phsetaknev said:
Yeah i guess its 20mm, it worked fine when i joined the nfc modules face to face without any distance it worked, with Xperia S. :good:
Click to expand...
Click to collapse
That's the way it works On some devices you also need to know where the NFC chip is. On One it's placed right above the camera, while most other phones have the NFC integrated into their battery (GNex). So you might have to hold the devices in an awkward way in order to get a connection.
I've managed to enable WiFi on lenok by coping several files from bass and kernel with the wlan driver enabled, courtesy of intersectRaven. It seems to be working without any issues, so here's a flashable ZIP.
Requirements:
LG G watch R running the 5.1.1 update (LDZ22D). This wasn't tested on anything else.
TWRP installed as custom recovery
unlocked bootloader
Instructions:
(optional) make backup of system and boot in TWRP, so you can revert changes my ZIP makes
install intersectRaven kernel 20150530_08XX or newer. Doesn't matter if you choose single or dual core. I recommend reading through his thread first. kernel thread | link to folder with his lenok kernels
reboot into TWRP
flash lenok_wifi_zip-XX.zip (you can get it to the device with adb push lenok_wifi_zip-XX.zip /sdcard/)
reboot the device
Whenever you flash anything that modifies boot.img (say, a kernel), you have to re-flash lenok_wifi_zip-XX.zip file.
Needless to say, this breaks OTAs - when next Android update hits, you'll have to restore from backup or flash whole images.
Downloads:
0c8d3fa95380e7ac75201bed0cab85fb lenok_wifi_zip-02.zip
AndroidFileHost: https://www.androidfilehost.com/?fid=23991606952612046
Basketbuild: https://basketbuild.com/filedl/devs?dev=Tassadar&dl=Tassadar/lenok/lenok_wifi_zip-02.zip
dev-host: http://d-h.st/FLCk
Notes, warnings...
You're flashing this from your own will. This file brings over bunch of files & bits of firmware from Urbane, something might break. There's also a chance LG didn't just do this because "hey, buy urbane, it has WiFi!" and there is some actual reason why WiFi was not enabled on lenok - including some HW difficulties. Using this method to enable WiFi has the potential to cause permanent HW damage. Also keep in mind that WiFi on G Watch R might not have been certified for use.
It's working just fine for me so far, but I haven't been using it for very long. The voice recognition is slower than on BT and less reliable (sometimes even claiming "offline"), not sure if that's "how's it's supposed to be" or if it is bug specific to this mod. Some guessing about what might be causing it in this post.
One last thing - please, don't discuss common "halp I don't know how to install recovery/flash kernel/flash a ZIP" problems in this thread and focus only on issues related to the mod itself. Thanks.
Lets start the party, flashing right now
Flashed everything. Now the G Watch R reboots into TWRP or maybe Bootloader. But no normal reboot into android?
Glad to see that someone mirrored what Paul O'Brien did for me back in the N1 days. He gave me the ROM and I gave the kernel to enable FM radio.
Flashed stock boot.img, recovery.img and system.img to get the G Watch R back to work. Now I'm waiting for comments with working hack until I'm gonna try it again..
tried,everything seems good,got the wifi
Why the kernel requirement?
SferaDev said:
Why the kernel requirement?
Click to expand...
Click to collapse
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.
Tasssadar said:
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.
Click to expand...
Click to collapse
Alright seems logical, G Watch R had the hardware inside but no certification in the device specs. I'll give it a try later. Thanks, if you need anything don't hesitate to ping me.
SferaDev
Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?
fabioio said:
Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?
Click to expand...
Click to collapse
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us
Tasssadar said:
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us
Click to expand...
Click to collapse
yeah i meant that! i actually can't use voice recognition i always get some connection problem!
Why would they disable it when it clearly works?
Works great
123421342 said:
Why would they disable it when it clearly works?
Click to expand...
Click to collapse
Clearly for market reason. LG want everybody buy urbane.They are sucks.
akaHardison said:
Clearly for market reason. LG want everybody buy urbane.They are sucks.
Click to expand...
Click to collapse
wifi certifications take time and cost money, that is probably why
suljo94 said:
wifi certifications take time and cost money, that is probably why
Click to expand...
Click to collapse
You should know that this watch has already have certification it needed.FCC has already approved this watch using WiFi.
No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?
Koopa777 said:
No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?
Click to expand...
Click to collapse
It's just that we have no idea. While I'm inclined to believe lenok doesn't have wifi just due to marketing reasons, there might be some key differences between bass and lenok that I don't know about, and that _might_ cause some problems later.
Great work Tasssadar!
Regarding the voice recognition "issue" I've noticed it works pretty decently if I'm close to the WiFi AP but gets worse and worse as I move away, so it might have something to do with WiFi signal quality.
Shame on you, LG.