We make it easy for companies to comply with the notice requirements (via build scripts that populate inside the about phone section of the OS) and we often advocate for what we consider to be our high level of compliance wrt code mirroring.
If you review the manufacturers of devices that actually make it into people's pockets, you'll find that they are fairly decent about compliance (notification and providing source on request) and a few are very good and doing more than the licenses actually require (posting mirrored code online at time of shipment, like we do).
Some are not as fast about code provision. In those cases, I suggest joining gpl-violations and starting there. Email me too and I'll pass word along if they are one of the manufacturers that we have a decent relationship with.
For most of the small run manufacturers, we have little or no relationship and gpl-violations might be a better place to start.
We aren't the world's linux cop and I know from experience it's the last thing people want Google to be.
There are some companies that don't care about doing compliance right, and they'll take what is in my opinion a long time to comply with the license, or work certain corners of the license (like sveasoft did many years ago) to wiggle out from under the code provision requirements of the gpl. It's actually quite difficult to see what could productively done about these bad actors.
I take umbrage from people who say crap like 'Google makes money off other peoples violation of the gpl' . It isn't true and It shows a lack of thoughtfulness on the part of MJG on this issue.
Finally; As one of the people who contacts developers and manufacturers using our software outside of the provisions of the apache, bsd, lgpl and gpl licenses, compliance is almost always about education and not about malice.