This basically answers my question about dark weather in the future for all of this. If Google is standing on an issue of trusting their clients to be in the right bucket of profitable customer to get through agreements and NDAs on what they’re proving unless you’re a multi national juicy enterprise target they’re really not the people I want to deal with. I don’t know what kind of deal Google has but I suspect they finance a substantial amount of “evolutions” for their purposes through the blob device vendors.
I think that Samsung sells rooted devices to companies or organizations engaged in their partner program. There’s at least one company using those commercially in Europe to offer a modified device. I wonder if there is a gray market for Chinese boot loader unlocked devices, or if that’s dealt with on a service per device transaction level with some cellphone shop. If you can buy a device from Samsung with an unlocked boot loader and customized security updates in a sort-of private contract, where they acquire them with who knows what arrangement today that started with their partner program, it seems like a price issue more than a practical issue or policy limitation. I see the software for unlocking devices frequently but I suspect it is a short lived game for those people, either using factory provisioning while they have access to the software or otherwise monetizing the effort to offer these tools and services. Probably malware, definitely device info collection, but it just ends up at the same conclusion. if there is friction, why? Is Goog adversarial to developer devices now? Athe devices without friction in some other way made compliant or unsuitable for general use? Is unlocking the boot loader so much a risk to the firmware delivery and control scheme for the baseband propriety stuff and chipsets or is it just that it’s vertically integrated in western markets through device financing by telecoms? — I do mean to seriously ask what is their holdup. They can’t afford to develop the software and hardware simultaneous tracked and offer that product if it leaves the control of their promised end user as a client?
I wonder if one side I very low power emitter designed to connect to the other head-side unit, presumably designed to connect to your device. Some bt headphones are designed with a weak unit and strong unit.
There is no left or right side to the helmet unit; the entire unit is on the left side of the helmet (right hand operates the bike's throttle, so the left hand is the free hand to operate the unit).
Correlation of even anonymized hardware emissions and location history for commercial use such as advertising would eventually identify police or company specific hardware. A product for this purpose already exists in Signaltrace, and probably exists as an in house solution for large campus operators like Walmart, universities, or a place like HP.
Apparently if I’m reading the work of others correctly a notification component and subsequent other interaction logs, in this case that the notification was not generated, is also logged in knowledgeC pointing to at least some metadata of non-notified messages logged.
I’ve been looking into reproducing the extraction of unredacted data. Found this, and it’s speculative, but Magnet Forensics has an internal “infomercial” on reconstructing content from notifications, too.
“find the inclusion of this information interesting because there is a chance that this still contains communications even when the record has been deleted from the sms.db file. I've yet to find definitive proof that this is the case however and it's possible that it is purged at the same time as sms.db is cleared.”
Looking at the detritus in the filesystem on Jailbroken iOS devices you will observe that iOS decides to vacuum, purge, and let linger all sorts of databases and logs until something triggers a cleanup which is usually time or an iCloud sign-out induced erase and subsequent sync. People have been complaining for years about excessive phantom “system storage” and “other data.” Interestingly the photos thumbs database can grow seemingly indefinitely in size for some weeks or more if you’re regularly deleting all of your photos and saving to photos from apps or taking photos. I suspect that there a lot of behavioral data records that is left on most devices until a convenient period of inactivity passes and the possible user behavior analysis and reporting functions of iOS allow whatever cleanup happens after processing on device. It would be useful to capture iCloud backup restores from physical devices to corellium virtual devices with some creative matching of your existing idevices identifiers. Could see what triggers a cleanup during backups, local or otherwise, get a good look at what is being restored from iCloud. I also think it’s possible that iCloud can sync a database, say safari bookmarks, pushing it to the device inducing a state where the device bookmarks are moved to inaccessible tables and left there, unavailable to the end user, but not out of sync with the current active session state. Of course this is just my musing based on observations of weekly ffs extractions of a few devices over the last 5 years.
My observations from when I daily drove iOS (no more) mirror yours: the incredible amount of cruft that would accumulate was astonishing. At one point I had a device that was majority full of system storage and other data. The same was true across family devices, too.
Some years ago I stopped depending on Apple's purchased downloaded movies for long flights, after an instance of having the files downloaded to the device beforehand, but Apple deciding I didn't have the DRM keys to play said files during a long transoceanic flight. I then moved to storing DRM-free movies in VLC, but iOS prioritized keeping system storage and other data cruft around, and wiped VLC's stored files. Talk about paying for an expensive device and media you don't really own.
I'd imagine the metadata picture that could be synthesized from that data could be extensive in some cases. This stuff is hard and I'm sure there are good reasons for caching things, especially on a device positioned to primarily act as a readily available front end for online stores, but I have a hard time believing that Apple's executing it well.
This all seems like a reasonable critique but the idea that the reason for not cleaning up data is so the system can run background behavioral analysis on it seems paranoid. Surely the main reason for not running cleanup until storage is needed is just optimizing for in the moment performance.
