I am testing out a new app and noticed whilst looking at my reports that for a period of approximately 1 hour all charts showed zero activity. I.e. Requests/Second, CPU Seconds Used, Instances all display zero, when they shouldn't be as the app receives a constant supply of traffic. Note: Error/Second shows no errors for that time period.
This screenshot conveys this:
I have looked in my logs and during that period it shows I still received traffic and requests were handled successfully - which is puzzling.
Has anyone else noticed such an anomaly or is this likely to be an issue with my app!
Thanks
This is almost certainly a reporting issue - your site was getting traffic, and serving it fine, but the infrastructure that collects stats failed to do so for a short while. Check your logs to confirm.
It happen to me today ~(6/11/2011) also, I think its a one time flock.
Its probably a result of the switching to the new billing model.
Related
Before some one close this due to the reason that it may have been asked earlier kindly read the following note
Note: Another question here with almost same scope of information and usage has been asked earlier but it does not contain any answer! Tried googling a lot but did not find any satisfactory answer!
My Question is about the EditText in android, how much text it can hold in it?
I write a code of server which receives a request from clients and display the history of all requests received so after 2650+ requests my app begin to not respond and finally crashes. I noticed that due to some reason very large text makes the EditText unresponsive one request contains almost 85 chars data!
Platform Nokia 6.1 with Android One 9.0 Pie
There should not be any real limit, but as you see you may run out of memory or require too much computation power.
My advice: Load the visible partof the log you want to inspect / edit.
Eclipse starts "scalability mode" when you have more than ~ 5k lines of code.
WhatsApp and Telegram only show the latest ~50 messages, but quickly load more when you scroll up a lot.
9Gag, Facebook etc. will load more posts on demand.
So you should think about something like that, or google scalable textEdit solutions. My advice would be to store the logs in separate files and load dynamically.
Ideal cpu percent for android app
I used to see the break down of battery usage about 5 weeks ago similar to the above topic's answer with CPU total, CPU foreground, GPS (because my app use GPS), and Computed power usage. However, after an auto update, the Battery Usage now shows only While in active use and While in background which is pretty much useless information and it does not even track the time my app use in the background properly (always 0 minutes even after running in the background for 16 hours - I checked the log to verify this).
Ideally, I would like either see the detailed breakdown again so I know exactly how much total time was requested for each category. Should I flash an earlier version of android or just install the right Settings apk file? If so, could you please tell me your Settings's version?
Not ideally, I can get the cpu usage break down through adb shell /system/bin/dumpsys cpuinfo, however I cannot control the time I want to sample like using the previous setting app (full charging & unplug would start the timer). Anyone have experience using adb to specify which time range I would like to query CPU time from?
Several users of my app have reported their battery draining at around 1% a minute with my app running in the background. I have been unable to replicate this issue even when using the same account credentials on the same device model that the user had the error on. Reinstalling the app apparently does not solve the problem, and there does not seem to be any specific Android version or device associated with the issue. All the reports I've had are Samsung devices running 4.x, but this is also fairly representative of my user base overall. My background service listens for GCM messages and contact list changes as well as firing off an http request roughly every hour using a ScheduledExecutorService.
I should also note that I do not use any wake locks in the app.
I am wondering if anyone has any ideas as to what sorts of bugs might cause an issue like this, or even what tools or methods might be effective in narrowing down my problem scope.
About what percentage of users are reporting this problem? If you tried it on a Samsung device running 4.x and you didn't get an issue something besides your code must be the problem.
If I were you I'd
Start testing with your wifi turned off.
Test your application while simulating high latency (Charles
has a free 30-days trial)
And add some code for monitoring battery level and charging
state.
I'm sorry I don't a better answer.
I have an application which records information using a tablet which is sync'ed to a server where reports are then run on the results. The users spend all day using the tablets and travel a lot throughout the day.
The time when the users complete these tasks is crucial to the reports and we have had several occurrences where we can't rely on the device time.
The user sometimes manually sets the time to something different on the device in order to look like they have done more work - this happens more than we expected
When relying on the time set to 'automatic', the time sometimes jumps around as the users travel between networks
When the tablet is initially switched on, sometimes the device time is set to 1970
I have a webservice to get the server time which is not currently used because we can't rely on the users having internet connection because they generally don't have any connection at all due to the nature of the work. However, they sync the data everyday usually, or at least once every few days.
I'd like to create something that gets the server time and counts the time from then on and the app would use this time. Any time they connect, this time will be updated, just to make certain the time is synced. Does anyone have any suggestions as to the best way to do this? Bear in mind that the time that we send up is crucial - it could be the case that if misreported on several occasions, someone could lose their job.
Thanks in advance!
Android do have 3 different kind of timer...
SystemClock
One of them will be useful to you,uptimeMillis()
Once the app starts, save the current uptimeMillis... when the app ends.. you could get the difference from "uptimeMillis() - oldUpTimeMillisThatWasStored"...
Android do sent a broadcast when the time or timezone is changed...
And if you have a broadcast receiver which catches for these changes from manifest file...
you will know when the time is changed (even if you app is not running)..
ACTION_TIME_CHANGED
You need persistent internet connection. Otherwise you have to rely on client time which can be modified as you already mentioned. You may be able to track the changes, but only as long as the app is running which can easily be faked by disabling the app (Settings -> Apps) before changing the time.
Scenario:
User completes task, client time gets stored
User modifies time
Device gets internet and syncs with server, telling him its current time and the task so server can calculate tasks "real" completion time. <-- ERROR
I left this unfinished, but have now implemented a solution.
I've created a Service which runs in the background, and downloads the date at intervals from a webservice, and uses a Timer to increment the time in between calls to the webservice.
Further to this, I use GPS to get the current time and date, and it uses this if possible, and if not then it uses this internal clock.
The time should be right most of the time, in theory!
I wrote an android application to request a scan for available wifi signals around, using the WifiManager, then dump the results to a file. The program works fine, but this weird bug occurs.
Initially I was requesting a scan every 30 seconds, and everything worked fine. I then tried to request a scan every two seconds, I get this strange bug. Everything will work fine for a few minutes, then the time between two scan requests jumps from 2 seconds to 50 seconds for no reason. Then, for four more scans, it will scan at 2-second intervals, then skip to a 50-second interval, and it continues to do this consistently.
With larger time intervals this bug does not appear. Has anyone experienced this bug before? Is there a way to prevent it? Or does Android automatically cancel scan requests if they are too frequent?
Thank you for your help!
NS
Any chance of posting some code?
Could this be an intentional limitation placed upon developers to avoid killing the battery.