Google Wallet can help you store your IDs, driving license, loyalty cards, concert tickets and more. You can also store your payment cards and use tap to pay to pay anywhere Google Pay is accepted. Google wallet is available in various countries but Google never launched it in India. Google let indian users stick with the Gpay which facilitates UPI payments. Tap to pay is not part of it. Also we can not store things such as IDs and Passes in indian version of Gpay. This might change and Google may launch Google Wallet in India. With the recent version of Google Wallet and Google Play Services, Google has added some flags and code which indicate that Google is working on something for Indian users regarding wallet. The first change I noticed recently when going through the Google Play Services apk was addition of two new flags Both flags are part of com.google.android.gms.pay package in the Google Play Services. This package contains all the flags for features of Gpay/Wallet. Google does server side flipping of flags to enable/disable features for users. So both these flags doesn't really provide any info about what features enabling these flags is going to bring. But the point here is that Google Wallet is not launched in India so why Google added these flags inside Play Services ? The answer could be that Google may be working on bringing Google Wallet to India. It can enable tap to pay, store payments and various other features for Indian users which we don't have in the current Gpay for India. I found similar flags in the analysis Google Wallet APK - These flags are also disabled by default. But this is again a clear indication of Google working towards something for Indian users. In both cases, enabling the flags doesn't bring anything noticeable UI or feature because there is nothing much added besides flags. Google has dogfood/testing versions internally, so the code will show up slowly in upcoming versions. The last piece of code I found is also from Google Play Services. In case you don't know, Google was working on Digilocker integration in the Google Files app which was supposed to bring your digital document inside the app such as driving license, COVID certificates, aadhar card. But Google has ditched the effort of bringing these features and they removed the "Important" tab (where digilocker was supposed to be integrated) from the Google Files app completely. So things are going to change and here is how. This is the code which I found in the Google Play Services - So the word "PASS" along with PAN, DRIVERS LICENCE, VACC CERTIFICATE & AADHAR CARD, is clear indication of the possibility of Google adding support for these directly through Google Wallet using Digilocker, just like Samsung Pass does it. This code is not old as I have checked older beta versions of Play Services where this code is not present. Here is a string which was added in a previous beta version a few weeks ago but I completely ignored it because it didn't make any sense without flags and the other code - This addition was surprising because there was nothing regarding digilocker before in the Play Services. In the words "pay_valuable", the "pay" to Wallet/Gpay and "valuable" refers to the things like Passes, loyalty cards and transit cards. Since we are talking about digilocker, these "valuable" are driving license, vaccination certificate, PAN card and Aadhar card which can be store in Google Wallet after digilocker integration. That's all about it. We will know more about it in upcoming app updates or maybe Google can itself annouce something about this.

Companies are going to have fewer people and fewer layers. Ten years from now, the software development circuit may have fewer jobs, higher salaries, and more product-centric work. The reason behind it is the rapid development of AI, AI has approached human beings at the intelligence level, a lot of work relying on thinking ability may be handed over to AI, while emotion is still the territory of human beings, how to communicate and collaborate is the most important ability in the near future. When Indeed's chart for software development and operations jobs was released, we found that, as the chart shows, there was a peak in early 2022, but after that there was a precipitous decline.

At the beginning of this year, Elon Musk had a fortune of $251 billion and could almost single-handedly solve world hunger. However, Tesla's stagnant sales, the endless struggle to buy Twitter, and the volatility of Tesla's stock price meant he lost a lot of money this year. According to Forbes, Musk is the billionaire with the most losses so far this year, with his wealth shrinking at a rate of about $5 billion a month. According to the website, his wealth shrank by more than 10% from the end of 2023 to June 28, 2024. As the website explains: Between December 31, 2023, and June 28, the last day of regular stock market trading for the first half of the year, Musk's net worth fell from $251.3 billion to $221.4 billion, a bigger drop than any other billionaire tracked by Forbes, but Musk remains the richest person on the planet. The main reason for the dip in Musk's pocketbook is that a Delaware judge in January canceled Musk's then-record Tesla compensation package worth $51 billion, which led Forbes to cut the value of the equity award by 50 percent because of uncertainty about whether Musk would receive those stock options. Excluding that bonus, Musk's wealth has remained volatile over the past six months, with the value of his 13 percent stake in Tesla shrinking by about $20 billion as falling profits and car deliveries sent the stock down 20 percent. But that was partly offset by the growth of Musk's stake in his generative artificial intelligence startup xAI to $14.4 billion (Musk also has a roughly $75 billion stake in private aerospace company SpaceX, a $7 billion stake in social media company X, And smaller stakes in other companies, such as brain experimentation startup Neuralink).

According to AndroidAuthority, the Linux kernel used by Android devices is mostly derived from Google's Android Universal Kernel (ACK) branch, which is created from the Android mainline kernel branch when new LTS versions are released upstream. For example, when kernel version 6.6 is announced as the latest LTS release, an ACK branch for Android15-6.6 appears shortly after, with the "android15" in the name referring to the Android version of the kernel (in this case, Android 15). Google maintains its own set of LTS kernel branches for three main reasons. First, Google can integrate upstream features that have not yet been released into the ACK branch by backporting or picking, so as to meet the specific needs of Android. Second, Google can include some features that are being developed upstream in the ACK branch ahead of time, making it available for Android devices as early as possible. Finally, Google can add some vendor or original equipment manufacturer (OEM) features for other Android partners to use. Once created, Google continues to update the ACK branch to include not only bug fixes for Android specific code, but also to integrate the LTS merge content of the upstream kernel branch. For example, the Linux kernel vulnerability disclosed in the July 2024 Android security bulletin will be fixed through these updates. However, it is not easy to distinguish a bug fix from other bug fixes, as a patch that fixes a bug may also accidentally plug a security vulnerability that the submitter did not know about or chose not to disclose. Google does its best to recognize this, but it inevitably misses the mark, resulting in bug fixes for the upstream Linux kernel being released months before Android devices. As a result, Google has been urging Android vendors to regularly update the LTS kernel to avoid being caught off guard by unexpectedly disclosed security vulnerabilities. Clearly, the LTS version of the Linux kernel is critical to the security of Android devices, helping Google and vendors deal with known and unknown security vulnerabilities. The longer the support period, the more timely security updates Google and vendors can provide to devices.

On the afternoon of July 8, local time, the Vietnamese Ministry of Health issued a notice stating that an 18-year-old girl in the country died of diphtheria. The Ministry of Health asked Nghe An Province and Bac Giang Province to take urgent action to control the epidemic. Diphtheria is an acute respiratory infectious disease caused by Corynebacterium diphtheriae, which is mainly transmitted through droplets and can also be indirectly transmitted by contact with objects containing Corynebacterium diphtheriae. Severe cases may show symptoms of poisoning throughout the body, complicated by myocarditis and peripheral nerve paralysis.