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.

The latest trade monitor released recently by the World Trade Organization shows that between mid-October 2023 and mid-May 2024, WTO members continued to introduce more trade promotion measures than trade restrictive measures. The WTO said it was an important signal of members' commitment to keep trade flowing amid the current geopolitical uncertainty. According to WTO statistics, during the monitoring period, WTO members adopted 169 trade promotion measures on commodities, more than the 99 trade restrictive measures introduced. Most of the measures are aimed at imports. Commenting on the findings, WTO Director-General Ngozi Okonjo-Iweala said that despite the challenging geopolitical environment, this latest trade monitoring report highlights the resilience of world trade. Even against the backdrop of rising protectionist pressures and signs of economic fragmentation, governments around the world are taking meaningful steps to liberalize and boost trade. This demonstrates the benefits of trade on people's purchasing power, business competitiveness and price stability. The WTO monitoring also identified significant new developments in economic support measures. Subsidies as part of industrial policy are increasing rapidly, especially in areas related to climate change and national security.

A Portadown man has avoided jail after sexually assaulting a 16-year-old shop worker under his employment. -ADVERTISEMENT- Brian Thomas Chapman (58), of Moyallan Road, appeared before Newry Magistrates’ Court on Monday for sentencing on two counts of sexual assault. The prosecution outlined that on September 23, 2020, a 16-year-old student in the employment of Brian Chapman, disclosed to her mother about incidents that had occurred in her workplace. She said Chapman had put his hand on her thigh and the back of her leg. She also disclosed that she had been getting extra money from him and he had been sending her text messages. The allegations were reported to police the next day, September 24. The victim then took part in an interview on October 9, in which she said, when she was alone in Chapman’s office, he placed his hand on her upper thigh and his other hand on her lower back, underneath her trousers. The defendant was arrested and interviewed at Lurgan police station, where he denied the allegations. His phone was seized and an examination was carried out. The first interview of the defendant took place on October 9, during which he admitted to sending a message about wanting the victim to work 24/7, but stated this was a joke. The second interview took place on January 28, 2021, where he admitted to sending the 24/7 message, but denied sending other messages, such as “hope you’re spending the pounds on something special”. Throughout this process, Chapman denied sending the messages and denied any of the sexual assaults alleged by the victim. On the Chapman’s criminal record, the prosecution added that he was convicted of three common assaults on appeal. In terms of commission, these matters pre-dated this case but the conviction occurred during the running of this case and also involved a female working for the defendant. Prosecution continued that the age of the victim was an aggravating feature, arguing there was a “vulnerability” due to the “power-imbalance” between Chapman and the young student working for him. An additional aggravating feature, they said, was that during the course of the defence, part of the defence was that the victim had “manipulated or manufactured” some of the text messages that were sent. A defence lawyer, speaking on the pre-sentence report, noted the author deemed Chapman to be of low risk. He also noted that similar offences were contested in the County Court in respect of another complaint, with the judge substituting indecent assault charges for common assault. He also argued a Sexual Offences Prevention Order (SOPO) was not necessary as the offending was four years ago, there has been no repetition and risk had been addressed. District Judge Eamonn King noted the defendant was convicted on two of four original charges following a contest, which ran over a number of days, with the case adjourned for a pre-sentence report and victim impact statement to be produced. He added the defendant “continues to deny” the charges and seeks to appeal the outcome. District Judge King, on reading the pre-sentence report, noted the defendant “denies ever hugging or touching the individual and he denies any sexual attraction to the victim”, but pointed to a paragraph in the report which stated, “From the available evidence, it’s possible to surmise that he demonstrated risk taking and impulsive behaviour. It appears that he took advantage of his position and power in a bid to meet his sexual needs, given the victim’s young age and the fact that he was her employer”. The report added that this demonstrated “limited victim empathy and responsibility due to his denial of the offences”. On the victim impact statement, District Judge King described her as a young girl getting her first job, with the “world as her oyster”. He continued: “As a result of what she says occurred, that turned on its head. It left her feeling inwardly uncomfortable, anxious and lonely. She cut herself off from her friends. She stopped going out. She didn’t want to go to school.” He also described a “degree of manipulation” in the case, as this was the victim’s first job and there was a power imbalance between her as an employee, and Chapman as the employer. In his sentencing remarks, District Judge King, said: “I’ve taken time to emphasise to the victim in this case that the victim did nothing wrong. The victim did everything right and the victim shouldn’t feel lonely, anxious or isolated. “The victim should feel confident, strong and outgoing.” Owing to the defendant’s ongoing denial of the charges, he added: “My sentencing exercise isn’t the conclusion of the case today, but I will sentence, so that we can move towards the conclusion going forward. “I am satisfied, irrespective of what the pre-sentence report says, that the defendant took advantage of someone, attempted to groom someone and was guilty of the two offences.” On the two counts, Chapman was sentenced to three months in prison, suspended for two years. He was also made subject to a Sexual Offences Prevention Order (SOPO) for five years and placed on the sex offenders’ register for seven years. Following sentencing, District Judge King fixed bail for appeal at £1,000.

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.

Beijing self-driving cars on the road will usher in legislative protection. Recently, the Beijing Municipal Bureau of Economy and Information Technology solicited comments on the "Beijing Autonomous Vehicle Regulations (Draft for Comment)". The city intends to support the use of autonomous vehicles for urban public electric bus passenger transport, online car booking, car rental and other urban travel services. In addition to application scenarios, the draft for comments also standardizes autonomous driving innovation from many aspects, such as whether there is a driver, how to deal with traffic problems, and so on. The release of the opinion draft also means that the commercialization of automatic driving is accelerating, and perhaps soon we will be able to experience the convenience of automatic driving. In addition, the accelerated pace of autonomous driving, and whether it will have an impact on the taxi and traditional network car industry, it is also worth thinking about.