Google has renamed AOSP's "master" branch to "main" today, in accordance with the company's commitment to using inclusive language in their products and services.
The legacy "master" branch will be a read-only replica of "main" but will be deleted in the future.
"Hi,
We are renaming the master branch to main in AOSP today. This is in line with our commitment to using inclusive language in our products and services. We believe this name will be more welcoming to everyone who uses our products.
In addition to the change in the branch name, you’ll notice that the targets on http://ci.android.com have new build variants named next, trunk_food, and trunk_staging. These variants represent builds with different feature flags, and you can use any of these for your local development (more information about these variants will be made available on http://source.android.com at a later time).
The legacy master branch will continue to exist in AOSP as a read-only replica of main and will be deleted at some time in the future. We encourage everyone to switch to using main starting today.
For those of you who use codesearch, please note that the source tree for master branch will no longer be updated. Please switch to using main in all your workflows and queries that use codesearch.
Regards,
The AOSP team"
The legacy "master" branch will be a read-only replica of "main" but will be deleted in the future.
"Hi,
We are renaming the master branch to main in AOSP today. This is in line with our commitment to using inclusive language in our products and services. We believe this name will be more welcoming to everyone who uses our products.
In addition to the change in the branch name, you’ll notice that the targets on http://ci.android.com have new build variants named next, trunk_food, and trunk_staging. These variants represent builds with different feature flags, and you can use any of these for your local development (more information about these variants will be made available on http://source.android.com at a later time).
The legacy master branch will continue to exist in AOSP as a read-only replica of main and will be deleted at some time in the future. We encourage everyone to switch to using main starting today.
For those of you who use codesearch, please note that the source tree for master branch will no longer be updated. Please switch to using main in all your workflows and queries that use codesearch.
Regards,
The AOSP team"
👍28🤔22🤡16👎11❤8😁5🌚5🤮2👾1
This media is not supported in your browser
VIEW IN TELEGRAM
FINALLY! Gboard is preparing to add an "undo" function so you can recover deleted words/sentences. Here's a demo of the feature in the latest beta release.
Credits go to Akos Paha from the Rboard Themes Telegram group for discovering this!
Credits go to Akos Paha from the Rboard Themes Telegram group for discovering this!
❤🔥68❤14👍12🎉7🔥3🤩3👏2😁2
Samsung made a great feature called Maintenance Mode that hides your apps & personal data so you don't have to factory reset your phone before sending it in for repair.
Google should DEFINITELY bring this to Pixel phones and I have an idea of how.
Before you say, "can't they just use a guest profile or add another user?" Well, yes but also no, because Android requires the primary user's credentials when it boots up.
Instead, Google can leverage Dynamic System Updates (DSU) to simulate a factory reset but without actually deleting any data.
My latest article for Android Central goes into detail on how this could be done, along with a demo video of this new factory reset-less DSU in Android 14.
Google should DEFINITELY bring this to Pixel phones and I have an idea of how.
Before you say, "can't they just use a guest profile or add another user?" Well, yes but also no, because Android requires the primary user's credentials when it boots up.
Instead, Google can leverage Dynamic System Updates (DSU) to simulate a factory reset but without actually deleting any data.
My latest article for Android Central goes into detail on how this could be done, along with a demo video of this new factory reset-less DSU in Android 14.
Android Central
Google should bring Samsung’s Maintenance Mode to Pixel phones
And here’s how they could do it.
👍55🔥11❤3👏3
Android 14 Beta 4 just dropped, so here’s my thread covering what’s new 🧵
(First look at the new Easter egg!)
(First look at the new Easter egg!)
❤56🔥6👍4👎1🤔1
Google has announced Android 14 Beta 4! Beta 4 is available for the Pixel Tablet and Pixel Fold as well.
This is the fourth Android 14 beta release available for users in the Android Beta program! There should be one more beta before the stable release.
Since Android 14 reached Platform Stability with Beta 3, Beta 4 doesn’t introduce any new APIs or app-facing system behaviors. However, there are some user-facing changes in this release, including the new Easter egg!
Edit: The update is now actually rolling out, by the way. The factory images/OTA files for Pixels are up, as are the release notes.
This is the fourth Android 14 beta release available for users in the Android Beta program! There should be one more beta before the stable release.
Since Android 14 reached Platform Stability with Beta 3, Beta 4 doesn’t introduce any new APIs or app-facing system behaviors. However, there are some user-facing changes in this release, including the new Easter egg!
Edit: The update is now actually rolling out, by the way. The factory images/OTA files for Pixels are up, as are the release notes.
Android Developers Blog
Android 14 Beta 4
Beta 4 is our second Platform Stable Android 14 release. Developer APIs and all app-facing behaviors are now final so you can review and integrate.
❤23👍7🔥1
Summary of what's new in Android 14 Beta 4 (build number UPB4.230623.005):
* Expanded availability to Pixel Fold and Pixel Tablet
* New Easter egg. To activate the Easter egg, open Settings > About Phone > Android version and repeatedly tap on “Android version” until you see the Android 14 logo floating in space. Hold down on the logo and you’ll see the “stars” speed by.
* New SystemUI icon
* New status bar icon for "mute"/"silent" mode
* "Speech" settings moved from Settings > System > Keyboard to Settings > System > Languages
* "Auto-confirm unlock" toggle has been added to Settings > Device unlock > Screen lock. This feature unlocks your phone automatically when you enter your PIN correctly. Your PIN must be 6 digits or more to enable this.
* Under Settings > About phone > Model, you can now see your phone’s “manufactured year”. This is derived from your device's serial number.
* The “ring volume” and “notification volume” sliders are now completely separated in Android 14, with no way to merge them again. In older betas, the separation was controlled by a DeviceConfig flag, but that flag’s no longer in use.
* Lock screen clocks are now enabled on the Pixel 4a 5G, Pixel 5, Pixel 5a 5G, and Pixel Fold, but not the Pixel Tablet.
* New default profile picture options
* The Settings app references a new “speed boost” toggle in SIM settings. I’m not sure what it’ll do yet, as it launches an activity in Adaptive Connectivity Services that doesn’t exist yet in Beta 4. Interestingly, the feature is explicitly disabled for Spectrum mobile.
* Expanded availability to Pixel Fold and Pixel Tablet
* New Easter egg. To activate the Easter egg, open Settings > About Phone > Android version and repeatedly tap on “Android version” until you see the Android 14 logo floating in space. Hold down on the logo and you’ll see the “stars” speed by.
* New SystemUI icon
* New status bar icon for "mute"/"silent" mode
* "Speech" settings moved from Settings > System > Keyboard to Settings > System > Languages
* "Auto-confirm unlock" toggle has been added to Settings > Device unlock > Screen lock. This feature unlocks your phone automatically when you enter your PIN correctly. Your PIN must be 6 digits or more to enable this.
* Under Settings > About phone > Model, you can now see your phone’s “manufactured year”. This is derived from your device's serial number.
* The “ring volume” and “notification volume” sliders are now completely separated in Android 14, with no way to merge them again. In older betas, the separation was controlled by a DeviceConfig flag, but that flag’s no longer in use.
* Lock screen clocks are now enabled on the Pixel 4a 5G, Pixel 5, Pixel 5a 5G, and Pixel Fold, but not the Pixel Tablet.
* New default profile picture options
* The Settings app references a new “speed boost” toggle in SIM settings. I’m not sure what it’ll do yet, as it launches an activity in Adaptive Connectivity Services that doesn’t exist yet in Beta 4. Interestingly, the feature is explicitly disabled for Spectrum mobile.
❤37👍16🔥9⚡2
Mishaal's Android News Feed
This is a bit personal, but screw it: the All About Android podcast that I've been fortunate to be a co-host of is ending after a 12 year run. Tonight's episode (at 5:00 PM PT) will be the final one. RIP 😢
From the ashes of All About Android comes the new Android Faithful podcast, and its first episode is out featuring yours truly!
We talk about Android 14 Beta 4, the Pixel Fold, and much more, so check it out!
We talk about Android 14 Beta 4, the Pixel Fold, and much more, so check it out!
👍31❤10
Forwarded from linuxct's channel (linuxct)
EasterEgg14.apk
3.5 MB
I saw that new Android 14 UDC Easter Egg and I really wanted to try it on my Android 12 and 13 devices, so I patched the APK to work there.
It’s possible it works on older versions of Android, but that’s up to you to try.
It’s possible it works on older versions of Android, but that’s up to you to try.
🔥25👍7👀3
It's still Amazon Prime Day, and one product that's on sale is the new "OSOM Privacy Cable", a USB-C cable with a data blocker switch. It is worth it?
OSOM sent me a cable to check out, but no this post isn't sponsored. The cable is 1m/5ft in length and supports USB 2.0 data transfer rates. Sadly, no USB 3.0 means there's not enough bandwidth for DP Alt. Mode, so you can't use this for video. Just charging (at up to 60W) or data (at up to 480Mbps).
One end of the cable has the product's main selling point: a hardware data signaling switch. It's pretty self-explanatory: Flip the switch and no data transfer is allowed, only charging.
I know Android's USB preferences says that "no data transfer" is an option, but it's actually an inaccurate denoscriptor. If it truly meant that no data was allowed, then ADB/USB debugging wouldn't work in this mode (but it does).
Android DOES support disabling USB data signaling, but it's:
1) Only possible on Android 12+
2) Requires USB HAL 1.3+
You can check the HAL version with this command:
Even if your device does support this, there's no user-facing toggle. All the APIs are available through Device Policy Manager, which is used to manage enterprise devices. I had to use Google's TestDPC app to test this.
Even though Android doesn't provide an easily accessible way to disable USB data signaling, should you buy a cable that can disable it at a hardware level? It's really up to you, as it's more about peace of mind than actually protecting you from a serious threat.
"Juice jacking" is more of a theoretical than actual issue. (Some great articles by KrebsonSecurity & ArsTechnica.) But if you just want to plug your phone in anywhere without worry, then maybe it's worth it to you.
The OSOM Privacy Cable normally costs $29.99 but is on sale for $23.99 until EOD on Amazon (non-affiliate link). It's a nice, braided cable albeit relatively expensive if you don't care about the data blocker switch. But again, it's up to you.
OSOM sent me a cable to check out, but no this post isn't sponsored. The cable is 1m/5ft in length and supports USB 2.0 data transfer rates. Sadly, no USB 3.0 means there's not enough bandwidth for DP Alt. Mode, so you can't use this for video. Just charging (at up to 60W) or data (at up to 480Mbps).
One end of the cable has the product's main selling point: a hardware data signaling switch. It's pretty self-explanatory: Flip the switch and no data transfer is allowed, only charging.
I know Android's USB preferences says that "no data transfer" is an option, but it's actually an inaccurate denoscriptor. If it truly meant that no data was allowed, then ADB/USB debugging wouldn't work in this mode (but it does).
Android DOES support disabling USB data signaling, but it's:
1) Only possible on Android 12+
2) Requires USB HAL 1.3+
You can check the HAL version with this command:
adb shell svc usb getUsbHalVersionEven if your device does support this, there's no user-facing toggle. All the APIs are available through Device Policy Manager, which is used to manage enterprise devices. I had to use Google's TestDPC app to test this.
Even though Android doesn't provide an easily accessible way to disable USB data signaling, should you buy a cable that can disable it at a hardware level? It's really up to you, as it's more about peace of mind than actually protecting you from a serious threat.
"Juice jacking" is more of a theoretical than actual issue. (Some great articles by KrebsonSecurity & ArsTechnica.) But if you just want to plug your phone in anywhere without worry, then maybe it's worth it to you.
The OSOM Privacy Cable normally costs $29.99 but is on sale for $23.99 until EOD on Amazon (non-affiliate link). It's a nice, braided cable albeit relatively expensive if you don't care about the data blocker switch. But again, it's up to you.
👍21👎6🤔1
Google Play has just announced a couple of new policies. Here's a summary of what they announced:
1) A new blockchain-based content policy that states that devs must complete a declaration for apps that enable users to transact blockchain-based digital content. Additional requirements apply for NFT gamification. Google's blog post on this particular change.
2) Apps that run "On-device Android Containers" will be required to respect the new REQUIRE_SECURE_ENV flag, indicating that they don't want to be run in an On-device Android Container.
I believe this refers to apps like Virtual Android and VMOS on Google Play, which run Android in a container. Google believes apps should be able to opt out of running in containers, hence this new flag.
3) New guidelines to their Deceptive Behavior policy to provide guidance on "non-transparent behavior." Basically, Google's making it clearer what they mean when they say developers can't engage in non-transparent behavior. Devs must make their app's functionality clear to users.
4) Expanded verification: when you create a Play Console account for an organization, you'll need to provide a D-U-N-S number. Further, Google will share more developer details on your app's store listing page.
This will roll out starting August 31 for anyone creating a new Play Console developer account. More details will be shared in October for existing developers. Google's blog post.
5) All apps that offer financial features must complete the declaration form. These apps may need to submit supporting documentation as well. This takes effect August 31.
6) The Request Install Package Permission policy has been expanded to allow companion apps used to sync Android phones to wearables or IoT devices.
1) A new blockchain-based content policy that states that devs must complete a declaration for apps that enable users to transact blockchain-based digital content. Additional requirements apply for NFT gamification. Google's blog post on this particular change.
2) Apps that run "On-device Android Containers" will be required to respect the new REQUIRE_SECURE_ENV flag, indicating that they don't want to be run in an On-device Android Container.
I believe this refers to apps like Virtual Android and VMOS on Google Play, which run Android in a container. Google believes apps should be able to opt out of running in containers, hence this new flag.
3) New guidelines to their Deceptive Behavior policy to provide guidance on "non-transparent behavior." Basically, Google's making it clearer what they mean when they say developers can't engage in non-transparent behavior. Devs must make their app's functionality clear to users.
4) Expanded verification: when you create a Play Console account for an organization, you'll need to provide a D-U-N-S number. Further, Google will share more developer details on your app's store listing page.
This will roll out starting August 31 for anyone creating a new Play Console developer account. More details will be shared in October for existing developers. Google's blog post.
5) All apps that offer financial features must complete the declaration form. These apps may need to submit supporting documentation as well. This takes effect August 31.
6) The Request Install Package Permission policy has been expanded to allow companion apps used to sync Android phones to wearables or IoT devices.
👍16❤1😁1