Last month raygun.io released its official Android provider, which captures all unhandled exceptions (before the app crashes) and sends it to the service, where the stack trace, hardware/OS data, etc are displayed. It also includes custom data and ad hoc sending support (like in a catch {} block), as well as app version tracking and unique user tracking (for a count of how many affected users for a particular bug). This helps tackle fragmentation as you can see what bugs affect certain models, and for what versions.
If there's no network available when a crash happens, the provider caches it and sends it the next time it can. And the capture & sending all happens asynchronously, so no blocking of the UI thread. Hope someone can benefit from this
Related
Google is releasing a security fix for all phones, is this going to affect the ROMs? Will this be something Devs will have to build a ROM patch for?
Here is the article with the details:
Google Fixes Android Glitch That Affected '99 Percent' of Devices
Google said Wednesday that it has fixed a security glitch that reportedly opened up 99 percent of Android-based devices to a security breach.
"Today we're starting to roll out a fix which addresses a potential security flaw that could, under certain circumstances, allow a third party access to data available in calendar and contacts," a Google spokesperson told PCMag. "This fix requires no action from users and will roll out globally over the next few days."
Google would not say what percentage of devices were actually affected.
At issue is a Tuesday report that said 99 percent of Android devices are vulnerable to attack when they're used to log into a site on an unsecured network. The report, which came from researchers at Germany's University of Ulm, claimed that phones or tablets running on Android 2.3.3 or earlier were vulnerable because of an improperly implemented ClientLogin authentication protocol. ClientLogin is used to verify users' identity on Android apps, and it saves the authentication data (authToken) for up to two weeks. The authToken is obtained from ClientLogin by providing a username and password on an https connection.
But the researchers said that when a user would login to a site like Facebook or Twitter that stored data could be open to attackers who could use the info to falsely gain access to their private information like Google Contacts and Calendars.
The researchers—Bastian Könings, Jens Nickels, and Florian Schaub—decided to simulate an attack to see if there findings were correct.
"We wanted to know if it is really possible to launch an impersonation attack against Google services and started our own analysis," they said. "The answer is: Yes, it is possible and it is quite easy to do so. Further, the attack is not limited to Google Calendar and Contacts, but is theoretically feasible with all Google services using the ClientLogin authentication protocol for access to its data APIs."
There was also an issue with the way data was handled when devices were synced with Picasa, but Google said this has also been fixed. Called a "silent fix," a Google spokesperson said all users will get the update automatically.
Click to expand...
Click to collapse
My understanding is this is a Google server side fix, and isn't something that needs to be "pushed" out to mobile devices.
Sounds more like it'll be an update to 1-2 apps to patch the security hole.
Hi,
Is there an application similar to the android one that can meter calls and messages throughout a month?
it would be very usefull but never found something similar for my wp7 device...
if you know any just tell me the name thx
I haven't run across a general-purpose one (haven't really looked either), but some of the carriers include that functionality in their own apps. The myAT&T app, for example, on AT&T, will allow you to view usage of minutes, data, texts, etc. if you're on AT&T.
im not with at&t, im from europe
too bad there is no application for this purpose, it would be really usefull
I think it's a good idea. Will see
is there a library for windows phone that enables a software dev to access the call history and messages sent?
because if there is i might be able to do it myself as i have some experience with blend and c#
if you know of something like that please post here!
This isn't possible on WP7 because Microsoft doesn't provide a way to access SMS/Calls.
See here http://social.msdn.microsoft.com/Forums/en-US/windowsphone7series/thread/6b2469b9-0bb6-4503-bc73-364812a1c277/
Short description
Link to the google store: https://play.google.com/store/apps/details?id=com.tim4dev.imokhere
Watching the location of the device.
The application allows you to track the location of Android devices (and their owners).
It can be: your's children, elderly relatives, friends, yourself.
The application must be installed on the device "observed" and "observers".
This is a MVP (minimum viable product).
Important: this is not a GPS tracker. Data is transmitted much less often and the data source is not just GPS.
Differences from competitors
Anonymous,
save battery,
free of charge,
no advertising,
no in-app purchases.
Requirements
Android 4.1 "Jelly Bean: (API level 16) and higher.
The "observable" device should be able to determine its location and have access to the Internet.
The "observer" device must have access to the Internet.
How it works
The user who installed the application can be either "observed" or "observer", possibly simultaneously.
In order to become "observable" you need to start the location service in the "I'm watched" menu, and allow the application to access the location and access to the Internet.
In this case, the "observed" will be assigned a certain identifier and data about its location will be periodically sent to the remote server (see privacy policy).
Important: You should not disclose your identifier to third parties.
When you exit the application or reboot the device, the service continues to run in the background. Stop the data transfer service through the same menu or by uninstall the application.
In order to become an "observer" you must obtain the identifier of the "observed". On the "watched" device in the "I'm watched" menu, send your ID to the "observer". After receiving the identifier, the "observer" through the "I'm watching" menu can receive data about the location of the "observed" and see it on the Google map. "Observed" can pass its identifier to several "observers".
"Observer" can receive data from few devices.
Screenshots
See attachments.
Privacy policy
The application does not start up on its own. You must start and configure the application yourself. You can uninstall the app at any time.
The application provides complete anonymity. Registration is not required.
A remote database stores an temporary anonymous identifier that is not associated with you personally, with your particular device, or with your phone number. Data that is transmitted and stored in a remote database is location data and some other data: longitude, latitude, time; If available: accuracy, altitude, speed, bearing, battery charge.
Only the last xx records are stored in the remote database (this restriction may be changed). No data is provided to third parties.
If you reinstall the application, you will be assigned a new anonymous identifier and link with all the old data will be lost.
The application does not hide the fact of its work. The application does not have any other hidden features, except those described here.
Usage limits
The last xx locations are remembered (this restriction may be changed).
https://firebase.google.com/pricing/
https://developers.google.com/maps/pricing-and-plans
https://developers.google.com/maps/documentation/geocoding/usage-limits
Firebase, simultaneous connections : 100.
Geocoding API : 2,500 free requests per day.
For beta testers
To become a member of the open beta-testers team, join the Google group (mailing list)
[email protected]
https://groups.google.com/d/forum/en-imokhere
This is recurring in all phones I've had for at least a year now. Once again...And it is just now that I am once again getting upset at Google Play Services making itself a device admin daily on startup so it can update its app daily. So it can weasel into the browser and log my account and store cookies and track and etc etc etc.
If I do not lose my phone, then it should stop activating the find my device. If I lock my screen, then it should stop activating itself as an administrator. If it was just to find the device, then it should stop putting itself as an account in my browser.
The Google Play Services can no longer be reverted. It has turned the phone into just another chunk of Google Garbage.
It's a critical part of android. What is it you are trying to achieve by locking it down?
James.Miller said:
It's a critical part of android. What is it you are trying to achieve by locking it down?
Click to expand...
Click to collapse
site storage in browser. I believe it is s carrier config or carrier settings. I have ridden myself of it by disabling carrier configs on other phones but here I can't disable carrier system apps.
I play with it off on some phones, and of course on rooted phones. It is irremovable here now. I had it removed during the first few days on my new A70 but now can't get it off noway no how.
The carrier configs and other things from carrier are a real problem. Carriers (used to) push settings they deem appropriate at regular intervals on an old phone I had. Their settings push included things like turning on location, and worse. all kinds of settings would get changed. Google calls these in its "partner" app. It's all tied together. There are credit agencies certs, and security companies in the system app.
James.Miller said:
It's a critical part of android. What is it you are trying to achieve by locking it down?
Click to expand...
Click to collapse
I may sell the phone if I can't use it on internet without continued police insults on my humanity. I'm sick of it all. Been taking abuse for years. Only useful as a gaming and music player.
In my experience, once you have confirmed to your own recognition that they are behind the curtain of the device, talking to you invisibly thru the back door in the comments sections of the internet, then the phone is no good.
I believe that screenshots of their android back-doored comments, -- along with proof in pictures or recordings that they have been speaking in narrative to you that way -- should be grounds for money back from the phone company for the device. The device is faulty then beyond the shadow of a doubt and worthless and irreparable. Money back should be the rule for hacked devices.
comments, recommendations...or other festures being hacked. I have had apps hacked, I have had voice recognition dictation hacked. etc. I don't remember a list of features of android I've stopped using because of insult hacks. The predictive words on the keypads, and auto correct, used to be a favorite exploit they'd use to deliver cracked commentaries against my humanity...
All features and apps I no longer use. And how many people would never pick up on how these devices are being used against them.
I think the phones should be peogrammed to avoid cached dns results, and to randomize the dns it uses. The apps such as YouTube should never return to an open session or use a cache. These devices are fast enough and simple LTE/4G is fast enough to load fresh sessions from sites from new lookup services.
if Google needs to have Find My Device in Android to serve customers who are afraid their devices will be stolen by non professional phone thieves or lost, then they should sell different versions for those who don't want a system admin like Google which gets its money from data theft and spamming.
The persistent settings in the browser for its default site bothers me. I got rid of it on my Oreo running phone. Took awhile, but I finally got rid of it on one phone by deleting all browser data. It comes back when the browser restarts on internet tho, and persists again like a foul barnacle. Used to be able to get rid of it.
Here it's seen it camoflages itself if I change the default search page, but it still persists
I have written a very simple app which uncovers a problem with Android. It seems that the Android developers have implemented SMS sending limits as an anti SPAM mechanism. Here is a link to a stackoverflow question which includes my code which uncovers the problem. I want to develop an app that sends SMS messages to a number (thousands) of registered users of Friday morning to inform them of what time Shabbos will start. Because of the limits imposed by the Android operating system this seems to not be possible at the moment. I have even tried writing two apps. App 1 launches and relaunches app 2. App 2 sends a hundred SMS messages. This seems to make some progress but also runs into limitations.
So my question is this. Are LineageOS developers aware of this problem? Has it been solved already? If not, does anybody have any idea what a patch would look like that would solve this problem? I imagine there is some variable somewhere in the code which defines what too many SMS messages looks like to the system. Presumably this can be tweaked or even bypassed to alleviate the problem.