I noticed this odd file sitting in my /sdcard/ folder. It contains such gems as
Code:
2013-07-30 22:14:01
RichSmsListener.onReceive(): Received Screen ON Intent.
My concern is that I specifically opted out of the T-Mobile usage reporting. Is there any other setting I can disable to stop this text file from being created? It's kind of annoying as I try to keep a neat SD card.
Bump! This appeared on my device yesterday. not a fan. How can I get rid of it?
i think it is for network or something it appeared or atleast i noticed after i was poking around with the usb tethering. it wont let me open it as its "in use" but idk what it is my best guess is some kind of data usage log or something.
copy paste is your friend lol....
--------------------------
2013-07-30 21:23:19
MobileDataWidget.onReceive(): Widget received intent with action: android.intent.action.USER_PRESENT
--------------------------
2013-07-30 21:23:19
MobileDataWidget.onReceive(): Received Screen Unlocked Intent.
--------------------------
2013-07-30 21:23:19
MobileDataWidget.onReceive(): successful, starting parent onReceive() execution.
--------------------------
2013-07-30 21:23:19
BaseWidget.onReceive(): Received intent with action: android.intent.action.USER_PRESENT
--------------------------
2013-07-30 21:23:19
BaseWidget.onReceive(): successful, starting parent onReceive() execution.
--------------------------
2013-07-30 21:24:41
MobileDataWidget.onReceive(): Widget received intent with action: android.net.conn.CONNECTIVITY_CHANGE
--------------------------
2013-07-30 21:24:41
MobileDataWidget.onReceive(): successful, starting parent onReceive() execution.
--------------------------
2013-07-30 21:24:41
BaseWidget.onReceive(): Received intent with action: android.net.conn.CONNECTIVITY_CHANGE
--------------------------
Click to expand...
Click to collapse
Sieze said:
i think it is for network or something it appeared or atleast i noticed after i was poking around with the usb tethering. it wont let me open it as its "in use" but idk what it is my best guess is some kind of data usage log or something.
copy paste is your friend lol....
Click to expand...
Click to collapse
It is somehow connected to the latest T-mobile My Account.
Zandeer said:
It is somehow connected to the latest T-mobile My Account.
Click to expand...
Click to collapse
Correct! I started getting it after the update. Since I'm rooted, I just went on ahead and uninstalled it off my device.
HTC One™
Related
Hi,
I was just wondering if anyone with the SGS II has managed to upload their tracks to Google maps? Every time I try it just waits at the authenticating to Google Maps screen without ever uploading anything. If I try on my old SGS it still works fine so it looks like it's just the SGS II that has the problem.
I did read elsewhere that it could be to do with the phone not having the default language set to english, but I have checked the phone and the default language is set to english, so I'm stumped. Any suggestions?
Same problem here
tracks been posted in GPS thread so guess its at your end .
jje
JJEgan said:
tracks been posted in GPS thread so guess its at your end .
jje
Click to expand...
Click to collapse
I think they are being imported rather than uploaded using the sgs2 as that's the only way I can do it, although I could be wrong (and usually am)
Would be good to hear if anyone had successfully uploaded via the phone.
Same issue here.
Tested and tracks stick at 0 in the uploading window . However my SGS 1 did that at times as well ..
jje
Same problem here too. Had to import tracks manually.
Same problem for me. There seems to be a problem with certain apps accessing my google account for authentication.
If I plug my phone into the PC and watch the console in eclipse I can see in the system logs there is some kind of authentication exception that isn't being handled properly when you try to upload a track.
This affects My Tracks, Andlytics and probably anything else that uses your google account in the same way.
Same problem here, seems to be a bug, the SGS still uploads.
Yep, same problem here.
This is the logcat when I press the "Send now" button:
Code:
I/InputReader( 2680): dispatchTouch::touch event's action is 0
I/InputDispatcher( 2680): Delivering touch to current input target: action: 0, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
I/InputReader( 2680): dispatchTouch::touch event's action is 1
I/InputDispatcher( 2680): Delivering touch to current input target: action: 1, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
D/MyTracks(15555): Logging in to local...
E/JavaBinder( 2680): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E/JavaBinder( 2680): java.lang.StringIndexOutOfBoundsException
E/JavaBinder( 2680): at java.lang.String.substring(String.java:1651)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.createNoCredentialsPermissionNotification(AccountManagerService.java:944)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.doNotification(AccountManagerService.java:1803)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.access$300(AccountManagerService.java:79)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:917)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:899)
E/JavaBinder( 2680): at android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthenticatorResponse.java:59)
E/JavaBinder( 2680): at android.os.Binder.execTransact(Binder.java:320)
E/JavaBinder( 2680): at com.android.server.SystemServer.init1(Native Method)
E/JavaBinder( 2680): at com.android.server.SystemServer.main(SystemServer.java:807)
E/JavaBinder( 2680): at java.lang.reflect.Method.invokeNative(Native Method)
E/JavaBinder( 2680): at java.lang.reflect.Method.invoke(Method.java:507)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/JavaBinder( 2680): at dalvik.system.NativeStart.main(Native Method)
It's an unhandled exception in some non-MyTracks code.
Does this work for anyone yet?
Er NO thats why we is still posting it dont work .
jje
To view your tracks you can export them as KMLs, then upload the KML to somewhere online (I use Dropbox), copy the URL for where they are, then go to maps in your browser and paste the URL into the search bar. You can then see your tracks in Google Maps. Clunky, but at least can be done. I'm quite pleased with how the tracks are for me.
KML import to Google Earth works, too. Its a shame they cannot fix the upload, it's the same from WinPc.
ALexander
Reply from Samsung to my enquiry on the problem
06.05.2011 16:35:37
Customer reference number:
Email response ID:
Dear xxxx,
Thank you for contacting Samsung and I have pleasure in providing the
following assistance:
Regarding to your query, kindly be informed that you need to refresh the
software of the phone and that is by removing the SIM card and the
battery out of the phone and wait for 30 seconds and put them back in.
If this did not work, you would try to reset the software and that is by
going to applications>settings>privacy>factory data reset and if it
enquires you for a password it would be 0000.
Before doing reset to the software, please make sure that you will back
up the whole data on the phone as the reset will erase the whole data on
the phone.
If this did not work out , you need to visit our authorized service
center.Please click on the link below to guide you to the nearest
Service Centre that you can go to with the Proof of Purchase, by just
submitting your Post Code, and choosing Mobile Phones from the drop down
box:
http://www.samsung.com/uk/support/location/supportServiceLocation.do?pag
e=SERVICE.LOCATION
If the authorized service center is far away from you , you need to give
us a call in order to send your phone to book for you a service request
to get it repaired .
Please note that when you contact us:
http://www.samsung.com/uk/info/contactus.html
Samsung mobile: 0845 MSAMSUNG (67267864)
Monday - Saturday: 9am - 6pm
Sunday: CLOSED
You will need to provide our representatives with specific details on
the phone like: The Model number of the phone, as well as the Serial
number. This can be found, underneath the Bar Code when you remove the
battery off the back of the phone, and it begins with an “R”. This will
help us determine the warranty term on the phone.
If you require any further assistance, please contact Samsung again and
we will be more than happy to help.
Kind regards,
Heba Khaled
Online Support Team
Samsung Customer Support Centre
Copy and paste response from Samsung, what a crock of sh...
Same problem here. Any ideas of a fix??
Same problem here. Using the GPX or KML file won´t generate the nice resumee-gfx i guess, right?
Discussion on My Tracks development forum:
http://code.google.com/p/mytracks/issues/detail?id=255&q=samsung galaxy s 2&colspec=ID Type Component Status Priority Targeting Work Stars Owner Summary
Anybody else try setting the language to US English?
I'm pretty new to XDAndroid so apologies if I'm doing this wrong.
I've been playing around with Google App Inventor and run into an issue with sounds. I thought I'd pass this on just in case it's pointing to a potential problem (I have no idea).
If I add a sound component with an mp3 source to an app it doesn't work on the phone, though it works in the APP Inventor emulator. But if I attach a wav file instead, it works. Also if I use the Player component, it works.
I'm running the latest kernel on a RHOD500. Here's the relevant part of the log file in case this is of any interest.
I/ActivityManager( 1444): Starting activity: Intent
{ act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=appinventor.ai_Ca
rld256.HelloPurr/.Screen1 }
D/Form ( 1893): Form got onResume
I/Sound ( 1893): Got onResume
I/Sound ( 1893): Unable to play. Did you remember to set the Source
property?
Taking a wild guess here. Remove all tags from the MP3 (using something like Mp3tag for windows).
Maybe there's an 'invalid' character in the file name?
Perhaps the phone is trying to find the codec and can't?
I have never messed with this stuff, just throwing ideas around
A tag issue sounds likely. I'll try that soon as I get Android set back up.
Heh, Would be right.
Have a look at this: http://forum.xda-developers.com/showthread.php?t=1096895
ryannathans said:
Heh, Would be right.
Have a look at this: http://forum.xda-developers.com/showthread.php?t=1096895
Click to expand...
Click to collapse
Yep, it seems to have been a tag issue. I ran meow.mp3 through Mp3tag and it works on the phone now. At least I know what to do next time I run into this problem. Thanks much.
No problems, glad I could help
Whenever I scan an NFC tag I created with NFC Tag Launcher it brings up a prompt that says "Open in browser" with options for OK and Cancel. However, it does not do that for tags I create in Lightflow for turning sleep on or off. Is there any way to disable this prompt?
Can't offer any help but I'm having the same problem with NFC Task Launcher.
I too get this. Not sure why. I'm on a rooted Verizon S3.
Download an app for NFC from the market first, then overwrite the default command that was stored on it. Most likely the command was to redirect you the site of the brand or seller of the tag.
nunyabiziz said:
Download an app for NFC from the market first, then overwrite the default command that was stored on it. Most likely the command was to redirect you the site of the brand or seller of the tag.
Click to expand...
Click to collapse
These are blank tags that I wrote to myself. I click OK every time and it never opens anything in the browser.
Have you verified that it was blank or have you erased the tag yet? I had the same issue with blanks that were not completely blanks.
nunyabiziz said:
Have you verified that it was blank or have you erased the tag yet? I had the same issue with blanks that were not completely blanks.
Click to expand...
Click to collapse
How can I tell if it's blank? According to NFC Tagwriter by NXP it's blank, and according to NFC TagInfo, the first two pages are read-only factory locked..
What do you have using NFC taginfo under "NDEF"?
nunyabiziz said:
What do you have using NFC taginfo under "NDEF"?
Click to expand...
Click to collapse
The blank tags have no message. One that I've written with NFC Tag Launcher has a message of the following:
Code:
WELL-KNOWN: urn:nfc:wkt:U(URI)
Identifier: 0x03("http://")
"tags.to/ntl"
MIME: ntl
enU:2:M:0,Q:-1;O:7;E:h:1__3:M:2;S:2;E:h:0
One written by lightflow has the following:
Code:
MIME: application/vnd.lightflow
SleepToggle
I would imagine the first part is what's causing it, but I don't know what there is to do about it.
EDIT: looks like that URL goes to the play store page for NFC Tag Launcher. Not sure why it's not actually opening in the browser though.
I personally use "NFC task launcher" and "erase tag" option.
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Sounds like you got it figured out.
nunyabiziz said:
I personally use "NFC task launcher" and "erase tag" option.
Click to expand...
Click to collapse
The issue is that I'm pretty sure it's NFC Tag Launcher that's writing the URL to it when it writes the task to the tag. I don't know what I'd do to write the tasks out to the tag otherwise.
I use NFC Task Launcher's erase function as well. As soon as the tag is written to again, this issue occurs.
jh120 said:
I use NFC Task Launcher's erase function as well. As soon as the tag is written to again, this issue occurs.
Click to expand...
Click to collapse
And did you write a task to the tag after? The NFC tag will always be detect, even blanks. It will just try to launch a unknown command.
nunyabiziz said:
And did you write a task to the tag after? The NFC tag will always be detect, even blanks. It will just try to launch a unknown command.
Click to expand...
Click to collapse
The issue is that the act of writing the task with NFC Task Launcher writes the URI to the tag. So erasing then rewriting the task accomplishes nothing.
I dont know all tags are the same size so maybe my tags are different. Im using web evolved tags and by default until erased and written to the tags will launch my browser and redirect to their site.
nunyabiziz said:
I dont know all tags are the same size so maybe my tags are different. Im using web evolved tags and by default until erased and written to the tags will launch my browser and redirect to their site.
Click to expand...
Click to collapse
Yeah, this isn't caused by anything with the tags themselves, it's just that NFC Tag Launcher adds the URI to the tag when you write out a task no matter what.
I can confirm that this happens regardless of tag type. I erased an old NFC-capable train ticket and wrote a wi-fi toggle to it. It works, but the browser dialog box still pops up.
Yeah, it's NFCTL writing that URL to the tag.
That URL is used as the intent filter and serves a few purposes. 1.) it saves space over a longer custom mime type or application specific record (which stores the package name). 2.) it directs anyone who doesn't have to the app to the play store to get it so that the tag actually does something - an application specific record does the same thing but has to store the *entire* package name (28 bytes in this case).
The way this has worked on *every* other device (and the way it should work in Android) is that the entire NDEF message hits the intent filter for that URL and the message is then delivered to the app. The app then grabs all records from the message (there are two) and parses the second record and executes those actions.
Given what the OP has sent me for some reason the Verizon S3 isn't doing this. (The international and ATT version work as expected).
Given that it's showing the chooser it's missing the specific intent filter and showing a dialog for what to do with this URL:
Code:
D/NfcService( 909): TAG: Tech [android.nfc.tech.MifareUltralight,
android.nfc.tech.NfcA, android.nfc.tech.Ndef]
D/NfcService( 909): Attempting to dispatch tag with override
D/NfcService( 909): No activities for NDEF handling of Intent {
act=android.nfc.action.NDEF_DISCOVERED dat=http://tags.to/ntl (has
extras) }
However it's still delivering the payload to NFCTL as the actions get executed (which it shouldn't do if you're getting the browser chooser dialog). It shouldn't work this way, literally. If you get the chooser it should deliver the entire payload to the chosen app (it's not).
So, what can we do here? I can add an option to use an application specific record in place of the URL. This should ensure it doesn't happen but at the cost of space - you'll lose 15+ bytes of space on the tag as a result though as it will write a separate NDEF record to the tag containing the full package name.
Is there anyone with a Verizon device this *isn't* happening for?
I could in theory get this into a release tomorrow as I'd want to have this squashed pre release.
I've been playing around quite abit with this and I have "sort of" gotten around this by use the Tasker URL Launcher.
With TUL installed along with tasker, I can use another NFC writer utility to create the url of tasker://taskname
Now if I touch the new tag without NFCTL installed I will be prompted with the "New Collected Tag" screen....unfortunately its still not an autorun but I can tap the "new tag" and the sequence fires correctly.
Obviously as previously stated the problem is the interception by the phone of the URL string used by NFCTL. Personally I have rooted and ripped out most all the Verizon bloat so I'm unsure what is left to cause this interception.
Let me know and I'll test whatever.
konman2k4 said:
I've been playing around quite abit with this and I have "sort of" gotten around this by use the Tasker URL Launcher.
With TUL installed along with tasker, I can use another NFC writer utility to create the url of tasker://taskname
Now if I touch the new tag without NFCTL installed I will be prompted with the "New Collected Tag" screen....unfortunately its still not an autorun but I can tap the "new tag" and the sequence fires correctly.
Obviously as previously stated the problem is the interception by the phone of the URL string used by NFCTL. Personally I have rooted and ripped out most all the Verizon bloat so I'm unsure what is left to cause this interception.
Let me know and I'll test whatever.
Click to expand...
Click to collapse
I may add a quick option tomorrow morning and throw a test APK up here. If the Verizon release is anything like the International and US pre-orders I suspect we'll see a lot of downloads and this is a *really* annoying thing to happen. So far Samsung takes the crown from HTC's head as the OEM making the weirdest changes.
I've been screwing around with busybox's hwclock, but man-page != reality. I keep getting the "RTC_SET_???" invalid format/value error. <le sigh>
My RTC is currently in June 1970, wrong day, wrong time. The "big" pain has been that all nandroids are being dated by the RTC.
I can't find a setting, a hidden menu, an app, or any other helpful info.
+1 I've noticed that
Check out "Reboot Now" for Windows Phone http://www.windowsphone.com/s?appid=86cbd073-cbac-4297-be47-5032779eba80.
Add shutdown option too....pls..
So that we can directly shut down...without using side button.
Amirphp said:
Add shutdown option too....pls..
So that we can directly shut down...without using side button.
Click to expand...
Click to collapse
Sorry not my app. You'll have to contact the developer through the app. Just shared it here cause first restart app I've seen that wasn't home brew.
tonbonz said:
Sorry not my app. You'll have to contact the developer through the app. Just shared it here cause first restart app I've seen that wasn't home brew.
Click to expand...
Click to collapse
Screenof would be nice
Never mind, found it
http://www.windowsphone.com/nl-nl/store/app/lock-screen/f93c89f3-2136-4640-8f58-ecf86aba05b9
OK, the reboot one is kind of silly. I decompiled it. You want to know what the implementation of the reboot function is?
protected override void OnNavigatedTo(NavigationEventArgs e)
{
base.OnNavigatedTo(e);
string str = Common.UppercaseWords(AppResources.ApplicationTitle.ToLower());
if (MessageBox.Show(AppResources.RebootMessage, str, MessageBoxButton.OKCancel) == MessageBoxResult.OK)
{
this.RebootOSNow();
return;
}
Application.Current.Terminate();
}
private async void RebootOSNow()
{
await Launcher.LaunchUriAsync(new Uri("test:"));
}
Click to expand...
Click to collapse
... WTF? And no, it doesn't register a handler for the "test:" URI scheme. That's got to be something built in, that if called empty, reboots the phone. It's probably not *meant* to reboot the phone, though. Which raises all kinds of interesting questions about what it *is* meant to do...
I'll look at the screen-locking one in a sec.
OK, the Lock Screen one is actually weirder, in a way. It uses a native component, through a WINMD called WP8Helper.winmd. This WINMD file is larger than normal, 17KB even though it only exports a single class with five functions (for comparison, my FileSystem and Registry WINMDs combined are smaller than that, and have many times as many classes, structs, and APIs) and there's no corresponding native DLL. Nor does the WMAppManifest mention any in-process components. My best guess at an explanation for this is that the WINMD itself contains the native code and calls it directly (.P/Invoke, or possibly NET unsafe?) rather than through COM. Another possibility, I guess, is that the native DLL this WINMD talks to is in System32 and automatically loaded into the app...
Still, there isn't any shutdown app yet