Develop Bugs

Terminal command to switch 3g on and off?

While waiting for cyanogenmod and the toggle 2g app to land from the heavens, I had this idea. So is there a command to switch the 3g to 2g and backwards?
Using this command with locale and the terminal plug-in could be handy. I just don't have the linux knowledge, so that's why I'm asking here
Sent from my GT-I9000 using Tapatalk

Could it be as simple as echo-ing a value to something in /sys or /proc? I poked around for a minute in those dirs but didn't see anything obvious.

just use switcherpro widget great app and can turn on/off 3g

I thought it would be easy, since it's just probably one value to change somewhere, but as said I'm pretty much lost with this one
All of the widgets are just shortcuts to the settings. And that's exactly why I asked if anyone knows if this is possible, I don't like it that I have to click 5 times to switch the network (have to open the lockscreen also). I just want it to be automatic, so that it would switch to 2g at nights and when I'm at home where I use my computer to surf net. Also did you really think I wasn't aware of the widgets? If not, that wasn't that much of a contribution.

If it really is as easy as just echoing a value like so many other things are, you could do a listing of all files in the suspect dirs, then make the change manually, and then compare what files have changed. That might narrow down the search. There's probably some nifty grep or other linux command to make that easy, but I'm not real sharp at that.
I tried running logcat on the phone while switching network settings and while the log reflected my actions somewhat, it wasn't helpful in identifying what really happened.

TheMasterBaron just posted a non-signed version of the toggle 2g/3g app here http://forum.xda-developers.com/showthread.php?t=739530&page=15 I tried to sign it with the "auto-sign" folder, but it won't install. (For the record, I have signed apps from update.zips succesfully before with it). Anybody know how to make it compatible, since he (TMB) says it's down to the signign http://forum.xda-developers.com/showpost.php?p=8073786&postcount=149

[FIX] Tasker and the pattern lock

One of the things that I wanted to use Tasker for was enable the pattern lock when I was away from home and then disable it at home. Unfortunately due to recent changes in the Android SDK that is no longer possible with Tasker directly.
With a bit of searching I discovered the Secure Settings plugin which can be installed to /system/app and thereby provide Tasker with the functionality. However, it seems that Secure Settings does not work on the Galaxy S2 because Samsung have their own pattern lock and method of controlling it.
I started doing a bit of digging (mainly using logcat to see what the system was doing when the pattern lock was enabled/disabled via the Location and security settings menu). I discovered that the Samsung lock system is controlled by some files in /efs and with a bit of experimentation I was able to enable/disable the pattern lock via a root shell. I contacted the author of Secure Settings who suggested I use the Locale Execute plugin to run shell commands via Tasker.
So I present here the commands I am now using on my phone and hopefully they will be of some use to others. The commands include a check that should ensure that it does not attempt to enable the pattern lock when no pattern has been set, but this has not been fully tested!
WARNING: These commands require root access and you use them at your own risk!
Make sure to install the Locale Execute plugin first and then to enable the pattern lock with a task simply add a new "Plugin/Execute" action and set the contents to:
Code:
@! if [ "`cat /efs/cryptprop_lockscreen.patterneverchosen`" = "true" ]; then echo -n true > /efs/cryptprop_lock_pattern_autolock; fi
To disable the pattern lock create an Execute action with the following contents:
Code:
@! if [ "`cat /efs/cryptprop_lockscreen.patterneverchosen`" = "true" ]; then echo -n false > /efs/cryptprop_lock_pattern_autolock; fi
These have been tested on rooted stock KE7 firmware.
Enjoy,
Dan

Sorry for sounding stupid (I probably will)
But could you make a tasker-noob-proof-tutorial?
I couldn't find where to change, if it should be active inside or outside the given area (home or not home)..
Thanks in advance

mljjlm said:
Sorry for sounding stupid (I probably will)
But could you make a tasker-noob-proof-tutorial?
I couldn't find where to change, if it should be active inside or outside the given area (home or not home)..
Thanks in advance
Click to expand...
Click to collapse
He described the command action so you can apply your own rule... Google for tasker and you'll find a lot of howto
Sent from my Galaxy SII
If you find this post usefull please press the "Thanks" button

Great!
Is there a way to toggle 2G/3G and GPS via tasker on the galaxy s2?

great thread, thank you!
could you please export your tasker profile and upload it somewhere? i'm a tasker noob

@mljjlm
I'm sorry but this is not a tutorial for Tasker, it simply provides the information necessary to configure your own profiles for toggling the pattern lock. Although the information at the end of this post may prove useful.
@bgx
No idea I'm afraid, I've not had a chance to look into those although I'm pretty sure it's not possible to switch 2G/3G or GPS in the same way that the pattern lock is toggled here.
@js931
My profile is based on location (using the "Cell Near" state) and so will not be much use for anyone else. However I basically configured the following:
Create profile called "Home".
Add a "Cell Near" state and configure for my local towers.
Add a task called "Home" and include the "Execute" action described above for disabling the pattern lock (I also turn off mobile data and turn on wifi here).
Add an exit task called "Away" which includes the "Execute" action to enable the pattern lock (I also turn on mobile data here).

In your code for disabling the pattern, should the code read 'patternneverchosen' rather than 'patterneverchosen' as you have written? I haven't tested, but the spelling seemed odd.
If it's correct, ignore me

Major_Sarcasm said:
In your code for disabling the pattern, should the code read 'patternneverchosen' rather than 'patterneverchosen' as you have written? I haven't tested, but the spelling seemed odd.
If it's correct, ignore me
Click to expand...
Click to collapse
It is actually correct (I double checked the first time I tested it out since it was an ambiguous name), it is supposed to be:
pattern-ever-chosen
which is why I check for it being true in my command since we want a pattern to have been set.
Edit:
It has actually been properly tested today, I was away from home and the pattern lock was enabled, when I got back home the pattern lock was disabled.
One thing to be aware of, when setting up the Tasker profile, is that each "Execute" command requires its own root permission, so you have to make sure that these have been allowed before it will work quietly in the background (you should be able to trigger them by testing the task).

It works . Thanks !!!

It works great, however when the Lock Pattern is disabled, I still get the "slide to unlock" type of screen when waking the phone up. Any command for that?
I am running the stock SGS2 ROM (rooted obviously)
Thanks !

I am new to tasker and would like some help/advice
I want to save power a bit so want my gps to only turn on in certain cell tower locations (in order to aid more specific tasks when in those cell locations). my issue is not setting this up, it is in the fact that taskers default gps toggle settings do not work on the sgs2. Can anyone help with this, rather than me having to keep it checking gps all the time (which I have currently delayed to 10 minute checking slots).
Edit: Also not sure if it is me just being dumb, but I cannot see that plugin on that link in the OP..?

Excellent work, do you know if this will work with the original Galaxy S as well?

@julien.me
The slide to unlock keyguard is handled differently to the pattern lock, but you should be able to enable/disable it using Tasker without any hacking. I use Tasker to disable the keyguard when it is plugged in.
@Lennyuk
I mentioned in an earlier post that I have no idea how the 3G or GPS is enabled disabled, but I am fairly sure it cannot be achieved using a method like this.
@m.shafik
The original Galaxy S handles the pattern lock differently so this solution will not work, but the Secure Settings plugin may be of use.
Regards,
Dan

m.shafik said:
Excellent work, do you know if this will work with the original Galaxy S as well?
Click to expand...
Click to collapse
I used Tasker to do the same thing on my Galaxy S last night coincidentally - only in a somewhat more simplistic way as I am not as technically strong as most people here.
I have a simple Tasker profile that checks my location and if I am at home it executes an action to turn "Keyguard Off". Keyguard is under "Display" in the Action categories. Setting Keyguard to Off disables both the pattern lock and the slide lock.
My case is actually a little more complex because I want to disable the keyguard in two situations, when I am at home or when I am driving in the car. I did this by creating two profiles, the first of which checks to see if the GS is connected to my home wifi, and the second of which checks whether I am connected to my car Bluetooth. If either case is found to be true the relevant profile sets a variable. When the case become untrue (ie. I leave the house or turn the car off) the profile will clear the variable (via an exit action). I then have a third profile that simply turns off the keyguard when the variable is set.
I appreciate that there are probably cleverer and better ways to achieve the objective but I only installed Tasker last night so I am only just lifting the lid.

Hi terranim, I was using your script several days and it worked like a charm, but now I updated to 2.3.4 and it does not work anymore. Any advice ?
Sent from my GT-I9100 using Tapatalk

@hotsync100
I have not gotten around to updating my phone to 2.3.4 yet. As soon as I have I will try to figure out what is going on with my pattern lock hack.
Regards,
Dan

I'm now running Lite'ning v2.2 and the tasker fix still seems to work.
Which ROM for 2.3.4 have you upgraded to?
Dan

terranim said:
I'm now running Lite'ning v2.2 and the tasker fix still seems to work.
Which ROM for 2.3.4 have you upgraded to?
Dan
Click to expand...
Click to collapse
Stock kg1
Sent from my GT-P1000N using Tapatalk

Tried again and worked. I do not know what did I changed, may be the kernel . Thanks anyway .
Sent from my GT-I9100 using Tapatalk

I can't get it to work well on my SGS2 2.3.3 stock unrooted. I enabled admin and set Tasker to disable the keylock in a profile (when I'm at home and the wifi ssid is visible). The profile activates but I always get the lock.
And I mean the stock lock screen with the pin (not the pattern one which I read that requires rooting and the method explained in this thread)
Missing something?

[TESTING] 3.3/3.4 kernels

Let's make life less complicated and start a new thread for people to provide feedback on 2.6.39, ... 3.3, 3.4 (NEW) RHODIUM kernels. The source repository is here. Note, older trees are not under active development.
By the way, these kernels are developed jointly with jonpry, WisTilt2, and bzo. In addition a lot of code is shared with people that maintain active msm kernel branches (emwe, acl, Alex). Finally, all Xdandroid Kernel developers have in one way or another contributed code.
1. Feel free to use any of these kernels, however DO NOT submit a post in this thread that amounts to "This feature does not work for me." If you wish to submit a bug report, make sure you are proficient at using ADB, AND have installed GetLogs. In your post you should:
a. Include GetLogs output of the problem (or it didn't happen).
b. Include Rhodium model (100, 210, etc).
c. Try to reproduce the problem on the other kernels.
All other bug reports will likely not receive full attention.
2. These kernels are to be used with GBX0B.
3. These are auto-built at:
Auto Built Service generously provided by WisTilt2
The autobuild is down. Please use these links, they were the final kernel builds that were on the autobuild site.
2.6.39.3
3.0.18
3.3.8
3.4.3
4. What works:
This list should look very similar to the current status of .27 with your device. Meaning, if you have a rhodium on which the camera does not work with .27 (for example), camera will not work with these kernels as well. Please do not report issues that are present on .27+your device.
- Only 3.0 has BT support. Would appreciate some feedback on this. I get the impression that pairing/connecting takes a bit of patience, but I am interested in how this compares to BT in .27. If we get some positive feedback we can enable BT support across all three kernels.
5. How do these three kernels differ: They are maintained by the same group of people, and consequently differ very little. There are slight variations in power management code, but other than that they are hard to distinguish in terms of functionality.
6. Kexec: To hot-swap the kernels (boot with a new kernel without rebooting into WinMo):
a. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
b. Go to the shutdown menu in GB, and select "Kexec".
c. Phone will reboot within Android, using the new kernel.
7. Finally, I don't have too much time to hang around xda, so you shouldn't hope for "next-business day" response policy I am just hoping we can attract the advanced user to these kernels, that can do most of the troubleshooting on their own.
Enjoy, RHOD has to be one of only a handful of android devices that are pairing android with kernels as advanced as these.

This you should note:
I. If you are experiencing problems with turning Wi-Fi on, try the procedure outlined HERE before posting.
II. With regards to usb related functions and 3.4:
This kernel uses ICS style usb drivers and as a consequence, usb notifications in GBX no longer work. To work around this issue we wrote a little app XdaRndisToggler, which should allow you to turn on ADB, as well as USB Tethering (RNDIS).
Using this app is pretty self-explanatory:
0. Plug your phone in (No notification will appear in GBX).
1. Start the app.
2a. To start the ADB service, select "ADB only" and click apply. At this point you can use ADB to connect to the device.
2b. To start USB tethering, select "ADB+Rndis" and click apply. At this point go into Settings->Wireless->Tethering and check the box that says USB Tethering. The blue "USB Tethering" notification should appear in your taskbar and you should be all set to tether.
3. To stop using ADB and/or RNDIS, select "Disable USB" in the app and click Apply.
FOR ADVANCED USERS:
Alternatively, you can use ADB without the use of XdaRndisToggler (app is still needed for tethering), by making the following changes to init.cfg/init.gingerbread.rc (note, you will need to remount / as rw)
Code:
on property:persist.service.adb.enable=1
- start adbd
+ start adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/idVendor 0x0bb4
+ write /sys/class/android_usb/android0/idProduct 0x0c01
+ write /sys/class/android_usb/android0/functions adb
+ write /sys/class/android_usb/android0/enable 1
on property:persist.service.adb.enable=0
stop adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/bDeviceClass 0
Above, minus/plus is used to denote delete/add line respectively.
Downloads:
XdaRndisToggler 06/19

Ts-calibration is not working on the 3.0.9 kernel.
I can't see the [+]'s.
I was forced to use my own calibration file.

I am using the temporary 3.0 kernel and till now, I have faced a few problems:
1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.
2) On some random calls, the sound simply gets disappear and doesn't come. Normally this doesn't happen on every call (trust me, I called more than 7-8 phone no. for more than 1 hours today itself) but suddenly, but on one call, the sound just vanished and I couldn't hear anything from the caller on the other side. The problem remained there until I rebooted my phone.

apurohit said:
(I couldn't get the logs using Getlogs, don't know from where to pick it)
Click to expand...
Click to collapse
GetLogs

apurohit said:
1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.
Click to expand...
Click to collapse
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.
Are you using 3.0 for its bluetooth capability - if so, how's that working for you?

detule said:
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.
Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
Click to expand...
Click to collapse
Well, I tried pairing bluetooth with my laptop and a bluetooth headset, it takes forever however my laptop and the headset is always visible in the available device list. I have used .39 (wifi wasn't an issue on it but calls were problem) and .27 (provided with the bundle where voice issue was constant) and then used 3.0 (temporary provided by you), I am facing this problem on all of them. I have RHOD100, CSVs are attached with this post.
Also, I already have getlog installed on this build (it was provided in the Android App folder) but still, I cannot figure-out where exactly it is saving the file. Since you have provided the Getlog thread hence I will read it through and will provide you the same.
Update: Have attached logs taken from Getlogs. Thanks for the guidance.

apurohit said:
Update: Have attached logs taken from Getlogs. Thanks for the guidance.
Click to expand...
Click to collapse
You instincts were right, it is proximity related. In the file you attached if you search for "proximity" you will see a few "proximity 0" and no "proximity 1" -> meaning the proximity sensor is always reporting "user is near" and consequently the screen stays off.
Here is a silly question, do you have a case on your device, one that might be obstructing the sensor?

detule said:
question, do you have a case on your device, one that might be obstructing the sensor?
Click to expand...
Click to collapse
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.
The screen comes back the moment I pull hardware keyboard but goes off if the call is on or I press power button (general practice to turn the screen on) and then it won't come even if I pull the keyboard.
I have one more question which may sound off topic but thought it's good to ask an expert rather suffering forever.
I am wondering which key should I use to disconnect the call since the end key doesn't work in this case and throw me back on the home screen.

apurohit said:
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.
Click to expand...
Click to collapse
Yes, GBX0B is the first time (apart from NAND) that proximity-related functionality has been enabled.
If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.

detule said:
If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
Click to expand...
Click to collapse
I'm definitely leaning towards that myself. If it's busted in WinMo, chances of it working correctly in Android are slim-to-none.

detule said:
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
Click to expand...
Click to collapse
I understand, though I will wait for a resolution in near future
Still, thanks for sparing your time answering me

For whatever reason, the link to the autobuild is opening like this
http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/
Not sure why (I know how to get to the page, I'm just pointing this out)

JDog2pt0 said:
For whatever reason, the link to the autobuild is opening like this
http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/
Not sure why (I know how to get to the page, I'm just pointing this out)
Click to expand...
Click to collapse
Works fine here... FF9/Chrome16.

JDog2pt0 said:
For whatever reason, the link to the autobuild is opening like this
Click to expand...
Click to collapse
arrrghhh said:
Works fine here... FF9/Chrome16.
Click to expand...
Click to collapse
Thanks for the heads up i fixed it earlier today.

Now to legitimently post something...
3.1 does not funtion well on my RHOD500 GBX0B. Enabling wifi caused a soft reset that never seemed to clear up. 3.0 works alright. I will probably post the logs in a bit as I've switched to 3.0, however it is incredibly easy to replicate.

JDog2pt0 said:
Now to legitimently post something...
3.1 does not funtion well on my RHOD500 GBX0B. Enabling wifi caused a soft reset that never seemed to clear up. 3.0 works alright. I will probably post the logs in a bit as I've switched to 3.0, however it is incredibly easy to replicate.
Click to expand...
Click to collapse
Can't reproduce on RHOD400 with 3.1, wifi functions flawlessly for me. Since 400 and 500 are basically the same device, I would expect the same to be the case on your device as well.
This is where logs would have been useful.
Not sure what a "soft reset that never seemed to clear up" means. Reset to bootanimation? This is usually a user-land miscue.

detule said:
Can't reproduce on RHOD400 with 3.1, wifi functions flawlessly for me. Since 400 and 500 are basically the same device, I would expect the same to be the case on your device as well.
This is where logs would have been useful.
Not sure what a "soft reset that never seemed to clear up" means. Reset to bootanimation? This is usually a user-land miscue.
Click to expand...
Click to collapse
Decided to create a new post rather than edit the previous one. Anyways I'm not familier with "user-land miscue" so you'll have to explain that one to me, and yes it is a reset to boot animation. Upon manually reseting the device nothing on the homescreen loads and under wifi in settings it says "error"
data.txt contains only one intersting line that I could see.
Code:
E/WifiService( 1325): Failed to load Wi-Fi driver.
In logcat.txt the first line related to wifi is
Code:
I/ActivityManager( 1324): Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.WirelessSettings } from pid 1457
It's late and adb shell is giving trouble with the whole cat /proc/kmesg > dmesg.txt. The included terminal emulator crashes whenever I run it, I have little to no cell signal where I now live, and the Market refuses to work over wifi. I'll dig up an apk after I get some sleep.

JDog2pt0 said:
Decided to create a new post rather than edit the previous one. Anyways I'm not familier with "user-land miscue" so you'll have to explain that one to me, and yes it is a reset to boot animation.
Click to expand...
Click to collapse
Critical kernel errors (so called panics) end in a full blown reset to win-mo. When the device resets to bootanimation, this is Android (userland) freaking out for whatever reason.
JDog2pt0 said:
data.txt contains only one intersting line that I could see.
Code:
E/WifiService( 1325): Failed to load Wi-Fi driver.
Click to expand...
Click to collapse
Usually this is indicative of kernel/modules magic mismatch. Have you tried this http://forum.xda-developers.com/showpost.php?p=20887127&postcount=20 ? If that doesn't work, what kind of output do you get if you type
Code:
insmod /lib/modules/bcm4329.ko
JDog2pt0 said:
It's late and adb shell is giving trouble with the whole cat /proc/kmesg > I'll dig up an apk after I get some sleep.
Click to expand...
Click to collapse
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
...I feel like I am repeating myself.

detule said:
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
...I feel like I am repeating myself.
Click to expand...
Click to collapse
You are, rather unecisarily too. How do you think I got data.txt?
Code:
rm -rf /lib/modules
Did not solve the issue. Phone still goes to boot animation. Not sure what to do next, not sure why it's happening considering we basically have the same phone.

(Partial solution)NFC goes "to sleep"

Hi Y´all!
Deleted this post in the original forum. Decided to move it here instead.
I have a really annoying problem which i hope someone has an opinion about.
I´ve begun using nfc tags recently and have all sorts of ideas of how to make my day more automated.
The NCF concept however loses a great deal of value if you have to restart tag detection nearly every time you want to scan something. This however is a sad fact in my case.
What happens is that i turn nfc on, e.g. at work. Now tags are detected and everything is just peachy .
I get off, go home, ect. without changeing anything whatsoever.
The next day at work i scan a tag again and now it isn´t detected. NFC is STILL on but tags aren´t detected.
I restart nfc tasker without any effect.
Only when i shut off nfc entirely and restart in the basic wireless & network settings are tags scanned again. The next day everything starts all over.
Do anyone know anything at all about how tags are detected on the software side of things then please i could really use your input.
I found something here about nfc within android which mentions a "tag dispatch system" that evidently decides which app a tag is intended for when it is "discovered"
What i can´t figure out however is which part of android is "responsible for keeping a lookout"
The basic NFC app has been found to be running wether tags are discovered or not.
Please advise.
Regards
ELO
Update april 10th:
Unfortunately i have not yet been able to pinpoint the root of the problem. I have however figured out a workaround.
I´m fairly new to Tasker so perhaps there is a more elegant solution than the attached screendump shows.
I know - i know - crude symptomatic treatment at its worst. Basically a timer toggles the NFC setting on&off once every hour.
But it works.
Regards.
ELO

Polar67 said:
Hi Y´all!
I restart nfc tasker without any effect.
ELO
Click to expand...
Click to collapse
what's your "nfc tasker" app? and what's your phone & ROM & version?
Do your hear the "tag tap sound" when you scan the tag but the "nfc tasker" has no effect?

madfish73 said:
what's your "nfc tasker" app? and what's your phone & ROM & version?
Do your hear the "tag tap sound" when you scan the tag but the "nfc tasker" has no effect?
Click to expand...
Click to collapse
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO

Polar67 said:
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO
Click to expand...
Click to collapse
Something odd is happening. NFC tag detection and dispatch is handled at the system level by the NFC service itself. What tags?

Polar67 said:
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO
Click to expand...
Click to collapse
when problem present, you can try these steps to see what happens:
1. run Terminal emulator (you can download from play store)
2. type in terminal command line:
su
logcat
3. try to scan the tag again, and see what messages come out at then.

krohnjw said:
Something odd is happening. NFC tag detection and dispatch is handled at the system level by the NFC service itself. What tags?
Click to expand...
Click to collapse
Hi krohnjw. I use Xperia smart tags like these. My neighbour had a couple and he didn´t use them for anything. I will most likely get something else down the road but wanted to try this out first. I´ve been using the same tag all along. You think it might be flawed?
madfish73 said:
when problem present, you can try these steps to see what happens:
1. run Terminal emulator (you can download from play store)
2. type in terminal command line:
su
logcat
3. try to scan the tag again, and see what messages come out at then.
Click to expand...
Click to collapse
Interesting. Didn´t know that handy trick. Two questions please:
1: How do i exit logging without shutting down Terminal emulator, so that i can review whats been logged?
2: Is there an easy way to copy the entire logged entries to - say a mail for review on a bigger monitor?
Regards
ELO

Polar67 said:
Hi krohnjw. I use Xperia smart tags like these. My neighbour had a couple and he didn´t use them for anything. I will most likely get something else down the road but wanted to try this out first. I´ve been using the same tag all along. You think it might be flawed?
Interesting. Didn´t know that handy trick. Two questions please:
1: How do i exit logging without shutting down Terminal emulator, so that i can review whats been logged?
2: Is there an easy way to copy the entire logged entries to - say a mail for review on a bigger monitor?
Regards
ELO
Click to expand...
Click to collapse
hold down vol- & press "c"== ctrl + c
you can try logcat -d -f log.txt ( current dir must be writable), then copy log.txt to PC

madfish73 said:
hold down vol- & press "c"== ctrl + c
you can try logcat -d -f log.txt ( current dir must be writable), then copy log.txt to PC
Click to expand...
Click to collapse
It worked. Thanks. I´ll sift through the file and report back my findings.
I also installed Android SDK. Using USB debugging it should, allegedly, be possible to monitor error messages from a single app.
I´ll need to do some further study into that.
Does anyone know of a good beginners tutorial in this regard?
Regards
ELO

Logcat result:
Hi again!
Did stumble across this:
( 2272): Process com.jwsoft.nfcactionlauncher (pid 4900) (adj 10) has died. I/ActivityManager
Any thoughts appreciated!
Regards
ELO

Using NFC to unlock Nexus7

At work I have access to a Nexus 7 which is shared between 7 members of our team.
I would like to be able to issue each potential user a uniquely-coded NFC keyfob that they can use to unlock the Nexus' screen and maybe set it up in particular ways.
Is this even possible? I know I can run apps once the device is unlocked, but I need to use NFC to get into it in the first place.

Yea I would say it is possible. The N7 supports various user profiles. You should be able to use Tasker to read the UID from each Tag and log into a specific profile.
You will need a custom rom/kernel because by default, NFC is off when the screen is off. A custom kernel allows NFC on all the time which can start taking commands and wake up.
I haven't messed with Tasker or Profiles. I would say it would just be a matter of logic "Read NFC and IF UID=1818181818181 then Load Profile 1" stuff.
I used NFC's coded with a URL with a unique ID to load a web page and pass the ID variable in to the server, which recorded your login and submissions. Pretty cool stuff. Just make sure you get good NFC's because the cheap ones aren't as powerful and becomes a chore trying to scan it.
The sweet spot seems to be the "N" of Nexus on the back.

Double post