We are currently trying to solve this issue which is occurring only on some devices among our users.
Our application a reporting system which lets the user to collect information and take pictures which they can then export to our server. Once exported successfully they can download various reports from their on-line account.
The symptoms that we are getting on some of the android devices (running with froyo) are as following
Our app becomes sluggish and slow (all the lists and buttons respond with a lag)
If user takes a photograph it takes 10-15 seconds to for that photo to get saved
All the changes that user is making (adding new items to their report) does not get saved to disk and in the event of app (or even the whole device) crashing user looses all the data that he/she has so far collected.
On close inspection of these problematic tablets (all of these are Samsung Galaxy 7" tablets), we have found that there is a constant call to LicensingServer going in the background which is keeping everything busy. Our app does not use license and this background request for licence check has nothing to do with our app. Still the effect is very negative on our app. As you can notice from following section of logcat, the device is making 8-9 calls to the licensing server every seconds.
02-03 14:38:47.976 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.823 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.710 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.577 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.347 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.218 LicenseValidator(31668)Error contacting licensing server.
02-03 14:38:47.108 LicenseValidator(31668)Error contacting licensing server.
This constant hit has adverse effect on everything.
My question is, why does it try to contact licensing server so many times and if there is a way to stop it from doing so. As a part of our set-up we always turn off the "Background data" and "Auto sync" (which is under Settings - > Accounts and sync). The reason we do this because we don't want our users to access Android Market (its a part of management rulebook given to us as a part of this contract).
Even if we turn on the Background data the master Gmail account is the one that is set by us and the user does not have password for it. In this case sometimes the device goes into non-sync state (which is shown as an orange triangle icon at the notification bar at top). In this case also the device goes into this madness calling the licensing server 8-9 times every second.
Is there a way to make the device stop contacting the licensing server completely. We have spend last one week searching every possible corner of on-line forums and Android documentation. We have not yet come across anyone out there facing this problem. Any help or hint towards a solution will be hugely appreciated.
Usman Chamad
I was receiving a message that read "Market Licensing Error ... In order to validate your license, you need an Internet connection and to be logged into your Google Account." After clicking on the "validate license" button, it would come back with a message "License Validation Failed".
Many people, like me, turn off "Background Sync" & "Auto Sync" (Settings/Accounts & Sync/Background Data) on their Droids/Evo because it uses a great deal of battery power. I was going crazy trying to figure out how to get that annoying message to stop appearing every 30 seconds.
So, I logged into my Google G-mail, went into Settings/Accounts & Sync/Background Sync. Checked the box next to "Background Sync" and clicked the button to validate license. It worked, and even came back with a message "License Validation Successful" after about 5 minutes of me not knowing if it would even work. I then, of course, un-checked the box next to "Background Sync" and also un-checked the box next to “Auto Sync”.
I have to look at these settings about once a week because it seems to magically check itself once in a while, probably after an up-date, I don't know. But, when I notice my battery life is getting used too quickly, I check to make sure the box next to "Background Sync" and "Auto Sync" are un-checked.
Related
I've updated everything for their new API v4 and also the new Android application (the old one was removed from the Play Store).
Now I'm having a problem with the messages in application running android 5.0, I've to press "Check Server Now" everytime to check for new messages (which are sent to API correctly but gets the status Pending until I press in the app manually).
Someone tolds us to install the previous version of the .apk to solve this issue but I don't know how to get it.
Yes that is correct since May 12 I did need to update my php version it took a while but when I finally get it my phone did not need to download the app again now I see that play on my favor, I did use the app with no problems, I also saw that the sending process was not even aligned with the every minute I configure on my old samsung.
Today sadly 9/2/2018 my cell stop to work better said the app claimed for internet to be able to connect, of course I had WiFi and 4G but looks like something happened a 6 am pacific time.
I was expecting it was a problem with server so I wait patiently until 2 PM, and I asked my son to see the app on his phone Samsung J7 and the app was asking for user and password
I knew that the J7 was not able to configure the asking time to server looking for pending sms's but I thought will be enough for today sending messages every 5 minutes thinking was the default time. But did not work unless we click the manual form in the app or at least having the app on the screen swivel and will update sending sms's as mentioned leaving the status on pending and some times sent.
I did something stupid delete my old version of the app from my old samsung and guess what, I could not download the new version for incompatibility with my phone, I still not sure if my old version will start to work later on the day or tomorrow, but certainly I lost the opportunity to know.
I used https://apkpure.com/es/sms-gateway-api/networked.solutions.sms.gateway.api go get the older version an installed again on my SGH-M919V Samsung Android 4.4.2 not compatible anymore so the option of configure the refresh is not there any more, J7 was not able to do that,
Sep 3 2018 team upload new version since the notification process to send the sms did not work, the new version suppose to ask server every 2 min not working on my J7 Samsung. so at this point I have to send the messages clicking manually to search on the server for sms pending to send.
I have been using Google CloudPrint since December, and suddenly (sometimes, mostly when the networks is slow) when printing, it keeps printing.
I am using this configuration: Android Phone, my App creates a print job with ticket via Google CloudPrint, the android notification center displays the print job "Printing" (as in sending...), the Google CloudPrint receives the task, and prints it with the printer associated, then, normally, it removes the print job from the notification center. and thats all.
Now, it stays in the notification center... for ever, even if you cancel, it already sent a lot of print jobs (they are slow to appear on the GoogleCloud panel).
Is there a bug with Google CloudPrint or is a problem with my (probably outdated now) code?
I know is Beta, and that, but i neither find documentation, known bugs, or anything at all.
If you can guide me in solving this problem...
(This is the code i use to send the intent)
PrintHelper photoPrinter = new PrintHelper(Context);
photoPrinter.setScaleMode(PrintHelper.SCALE_MODE_FIT);
photoPrinter.printBitmap("print job", bitmap);
I had the same issue on a Samsung Galaxy Tab 4. I uninstalled Cloud Print and then reinstalled. Fixed the issue.
I implement Google Tag Manager on my project .When i work on emulator all events come faster in Google anlyatics account shown which page open,but problem is that when i use in real device its taking more time to show the events,its taking around 2-5 mins.
I am using like that can any tell me why its not working in real device.
& also can any one help me out how to implement E commerce tracking in android app.
DataLayer dataLayer = TagManager.getInstance(context).getDataLayer();
dataLayer.push(DataLayer.mapOf("event", "openScreen",
"screenName", "Home Screen"));
GoogleAnalytics.getInstance(context).setLocalDispatchPeriod(5);
I'm not entirely sure, since I don't develop your Android, but for iOS using Google Tag Manager (and Google Analytics for that matter) the mobile platform is not pushing events in realtime, but they batch the data and send them every other minute or so. For me the emulator in iOS does the same, i.e. it sends data every other minute and the same on device. Maybe the emulator in Android is different in this regard, but I believe that mobiles do not send data in realtime at all, but batches a chunk of data and send it at the same time.
I don't think there is any way to go around this. Correct me if I'm wrong though, but that's what I read somewhere in the documentation. Can't seem to find the reference though.
I am going to enter the Samsung 2013 app contest, and one of the requirements is that you use their Chord API http://developer.samsung.com/chord.
I plan on allowing users to send messages to all phones that have my app installed. From what I gathered from the information in the previous link, this means that I will need to have a constantly running background process for users to receive the messages when they are not looking at the app at the time.
I want to know if this is true, and if so, is this viable? I am considering using the method detailed here: Android: keeping a background service alive (preventing process death) if I go ahead with this.
I'm trying to use Samsung Chord too. I thing you don't need to do this. Samsung's API Chord already provides this control.
According Chord's API:
"If a Chord node doesn’t receive a UDP signal within a specified amount of time, it considers the “missing”
node to no longer be part of the network."
And, the only thing you have to do is:
"A node cannot receive a UDP broadcast if it is in LCD-off status. Therefore, if developers want the node to discover other nodes while the application is running, the node’s status should be set to LCD-on. To do this, use Android’s PowerManager.WakeLock."
Best regards,
Adriano
I used to use an app called Log Collector to see system logs. It would send them to my email or via bluetooth,
However, on Jelly Bean the "read log" permission for apps no longer exists and apps can't read the logs, and Log Collector is obviously no exception.
So does one now need to root the device to see system logs? There must be a way for the user to read them. I don't need to access them from an application, I need to read them as a human being. Is there a way?
I got the answer in this google groups thread:
https://groups.google.com/forum/?fromgroups#!searchin/android-developers/READ_LOGS/android-developers/6U4A5irWang/8xOi74KfRIYJ
the message by Mark Murphy replying to Matteo Sisti Sette (which is me).
(it doesn't seem to be possible to link to a particular message, is it?)
POWER + VOLUME_UP + VOLUME_DOWN will generate a report and a screenshot that you can send via email or upload to Drive (ridiculous you can't share it in an arbitrary way such as send via bluetooth or open as text file, but anyways).
(seems you have to hold them for a while and the action is launched when you release them)
At first I thought he was making fun of me and that would just reboot or something, but then I tried and it works.
Quote from Google+ and credits to +Ian Clifton :
"If you go into the developer options of a device running 4.2, you can check the box to add the Bug Report option to the power menu. This also adds it to the quick notifications menu (not sure of the proper name, but slide down the notification shade with two fingers on a phone or on the right side of a tablet)."
..and that would be right answer.. Cheers