platform_frameworks_base

>Their fix included a similarly large refactor Their change is hardly a big refactor. This includes all the new code, all the parameter changes everywhere the function is used, and two additional test cases. This is a tiny change. >12 changed files with 102 additions and 26 deletions. [1] https://github.com/aosp-mirror/platform_frameworks_base/comm...

Seems to me like this impacts not only Pixel devices but all Android devices? Patch was to AOSP: https://github.com/aosp-mirror/platform_frameworks_base/comm... I don't have a locked SIM handy, but can someone please test on their non-Pixel device and confirm?

>Therefore, with IPv6, telcos could disable the tethering function of the phones / charge extras, just by suitably configuring their network. Most carriers count tethering traffic from packets received with a TTL decremented by 1, whether or not you NAT it is irrelevent. This was the case for ipv4 and looks to be the case for ipv6 thanks to this very recent commit: https://github.com/aosp-mirror/platform_frameworks_base/comm...

Android connects to the phone network using a different type of connection (DUN) to send tethered data. The code to do that is in android here: https://github.com/aosp-mirror/platform_frameworks_base/blob... There is a setting you can set to disable it and make the provider treat all traffic as if it is non-tethered. adb shell settings put global tether_dun_required 0 Considering how knowledgeable the HN crowd is on all things networking, it surprises me to see so much uncertainty on something so easy to check in the code!

That method just instructs the OS to send keepalive packets on a system thread. It saves some CPU power by letting your process sleep, but still requires waking the cell radio up periodically. The implementation can be found here: https://github.com/aosp-mirror/platform_frameworks_base/blob...

In the Android world, translations are usually found in string resources. See [1], for example. AFAIK, if you want improved translations, 1) you'd need to either fork AOSP, build a custom ROM, and your users would need to deploy that custom ROM on their devices. or 2) convince Google to accept your changes [2]. Edit: There may be other hacky approaches I'm not aware of. You might find something useful if you trawl the XDA forums [3]. [1]: https://github.com/android/platform_frameworks_base/blob/nou... [2]: https://source.android.com/source/contributing [3]: https://forum.xda-developers.com/

Just call the isTheFinalCountDown() function of the Chronometer class. Source code: https://github.com/android/platform_frameworks_base/blob/6c7c55206dcca24880ac873fd…

The current list is https://www.google.com/generate_204 http://connectivitycheck.gstatic.com/generate_204 http://www.google.com/gen_204 according to https://github.com/android/platform_frameworks_base/blob/5b2...

Um, why is this worthy of the hackernews front page? Is this not the permissions extracted from the platform manifest with all the useful per-permission information removed? https://github.com/android/platform_frameworks_base/blob/mas... is much more useful. Linked to from my repo entry https://github.com/doridori/Android-Security-Reference/blob/...

Starting Q3 2015 the commit rate of this central Android component dropped significantly. See https://github.com/android/platform_frameworks_base/graphs/contributors What happened?

Apparently fixed: https://github.com/android/platform_frameworks_base/commit/4...

Things have changed a bit since the last time I had anything to with it, but you can read the Android source code: https://github.com/android/platform_frameworks_base/blob/mas... NITZ is terrible. You only get one-second accuracy, a GMT offset, and a DST flag, and they can all be wrong at the whim of someone at the phone company.

Actually quite a bit of the view code is native still - start reading the source for View etc and you hit a level where it's mostly calls out to native libraries. e.g https://github.com/android/platform_frameworks_base/blob/mas...

You're making the precise mistake we're talking about: don't project from your experience of desktop Linux to Android. This equally applies for any Java platform too as the VM performance characteristics don't resemble any from the Sun/Oracle family. The key thing is to understand what is involved to get an Android app to start up. This is terrifying when considering just the Dalvik case, but what most C++ types don't realise is that even if your app is using NativeActivity it means you are really subclassing this: https://github.com/android/platform_frameworks_base/blob/mas... This means in order to load the native lib you first have to load Dalvik, a whole load of classes relevant to the app, allocate the whole Dalvik heap for the app, and then you rely on the Dalvik code to initiate loading of the native lib. As a result this only beco

Not correct. AOSP source code has always included full source for android.view., android.widget., and so forth. Which are, by the way, Apache-licensed, not GPL. If you'd like to look for yourself, it's here: https://github.com/android/platform_frameworks_base in the "core/java" subdirectory. In recent releases (4.x, a/k/a ICS and later), some of the low-level GPU drivers are included as binary blobs, but the GUI libraries built on top of them remain, at the very least, source-available.