WASHINGTON, June 24 (Reuters) - Problems with Boeing's Starliner capsule, still docked at the International Space Station (ISS), have upended the original plans for its return of its two astronauts to Earth, as last-minute fixes and tests draw out a mission crucial to the future of Boeing's (BA.N), opens new tab space division. NASA has rescheduled the planned return three times, and now has no date set for it. Since its June 5 liftoff, the capsule has had five helium leaks, five maneuvering thrusters go dead and a propellant valve fail to close completely, prompting the crew in space and mission managers in Houston to spend more time than expected pursuing fixes mid-mission. Here is an explanation of potential paths forward for Starliner and its veteran NASA astronauts, Barry "Butch" Wilmore and Sunita "Suni" Williams. THE CURRENT SITUATION Starliner can stay docked at the ISS for up to 45 days, according to comments by NASA's commercial crew manager Steve Stich to reporters. But if absolutely necessary, such as if more problems arise that mission officials cannot fix in time, it could stay docked for up to 72 days, relying on various backup systems, according to a person familiar with flight planning. Internally at NASA, Starliner's latest targeted return date is July 6, according to this source, who spoke on condition of anonymity. Such a return date would mean that the mission, originally planned for eight days, instead would last a month. Starliner's expendable propulsion system is part of the craft's "service module." The current problems center on this system, which is needed to back the capsule away from the ISS and position it to dive through Earth's atmosphere. Many of Starliner's thrusters have overheated when fired, and the leaks of helium - used to pressurize the thrusters - appear to be connected to how frequently they are used, according to Stich.

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.

July 9 (Reuters) - Lucid Group (LCID.O), opens new tab will recall about 5,251 of its 2022-2023 Air luxury sedans due to a software error that could cause a loss of power, according to a notice from the U.S. National Highway Traffic Safety Administration published on Tuesday. The regulator added the EV maker will also recall about 7,506 of its 2022-2024 Air luxury sedans due to an issue with a coolant heater that could fail to defrost the windshield. Lucid had released an over-the-air software update in June as a fix for the software error and a separate update to identify a high voltage coolant heater failure and provide a warning to the drivers of the affected vehicles. The company had reported second-quarter deliveries above market expectations on Monday, as price cuts helped boost demand for its luxury electric sedans.

A provocative new study reveals the complex effects of the space environment on human health, providing insight into potential damage to blood, cell structure and the immune system. The study focused on SpaceX's Inspiration4 mission, which successfully sent two men and two women into space in 2021 to orbit the Earth for three days and shed some light on the effects of space travel on the human body. The research data, derived directly from the Inspiration4 mission, shows that even a brief trip to space can significantly damage the human immune system, trigger an inflammatory response, and profoundly affect cell structure. In particular, space travel triggered unprecedented changes in cytokines that play a key role in immune response and muscle regulation but are not usually directly associated with inflammation. In particular, the study found a significant increase in muscle factors, which are physiological responses specific to skeletal muscle cells in microgravity, rather than a simple immune response. Although non-muscular tissues did not show changes in proteins associated with inflammation, specific leg muscles such as soleus and tibialis anterior muscles showed significant signs of metabolic activity, especially increased interleukin in the latter, further enhancing the activation of immune cells.

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.