Dan's Tech Blog
Welcome to my Firefox tweaks and other tech stories!
Tuesday, July 9, 2024
Android 14 boosts battery life even more - also removes some features though
According to reports from users and Google engineers, Android 14 brings significant battery life improvements over Android 13 thanks to more efficient system processes that reduce background activity by up to 50%. Additionally, cold app start time is reduced by an impressive 30%.
Power-Saving Optimizations in Android 14
Android 14 introduces several power-saving optimizations that help improve battery life and device performance:
Freezing cached applications: Android 14 freezes cached apps after a short period of time, giving them zero CPU cycles. This frees up the CPU for other tasks and prevents apps from using resources unnecessarily in the background. Google found that cached processes consumed up to 50% less CPU cycles in Android 14 compared to Android 13 during beta testing.
Optimizing broadcasts: Android 14 adjusts how cached apps receive context-registered broadcasts, ensuring they stay frozen. Broadcasts are now queued and any repetition gets merged into a single broadcast in the background. This helps reduce the duration of cold app starts (when an app boots up from scratch) by 20-30% depending on the device's RAM.
Reducing code size: Google included optimizations in Android 14 that reduce app code size by an average of 9.3% without impacting performance. This improves both memory and storage efficiency.
Patching background app loopholes: Android 14 patches a loophole that allowed apps to stay active indefinitely in the background by running multiple monitoring processes. The system now freezes the entire application and all its processes before killing individual ones, preventing this workaround.
Impact of Background App Management on Battery Life
Background apps can have a significant impact on battery life if not properly managed. Here are some key points about how background apps affect battery drain:
Apps that run in the background, even when not actively used, can consume CPU cycles, memory, and network resources which drains the battery.
Certain types of apps are more likely to run in the background and impact battery life, such as those that use location services, play audio, or interface with Bluetooth accessories.
Buggy or poorly optimized apps can get stuck running in the background indefinitely, causing excessive battery drain until force closed by the user.Android's Adaptive Battery feature uses machine learning to categorize apps and limit the system resources available to those that are rarely used, which can significantly reduce their impact on battery life.
Users can manually restrict specific apps from running in the background in Android's settings, which prevents those apps from using any system resources when not actively used.
On iOS, only certain types of apps are allowed to run in the background, and they will still consume some battery. Fully closing these apps can improve battery life.
Proper management of background apps, either automatically through the operating system or manually by the user, can have a major positive impact on device battery life.
Cooler Device Operation, especially for Pixel 6 & 7 users
Android 14 introduces significant improvements in heat management, particularly benefiting Pixel 6 and 7 users who previously experienced overheating issues. These enhancements contribute to better device performance and battery life. Key improvements include:
Reduced heat generation during normal use, with users reporting their devices running cooler after the update
Improved efficiency of the CPU scheduler, likely reducing usage of power-hungry big CPU cores
Better thermal mitigation through constant monitoring and feedback from the Thermal HAL 2.0
Enhanced thermal status reporting, allowing apps to adjust their behavior based on device temperature
Smoother overall performance, likely due to better heat management
Potential doubling of battery life for some users, partly attributed to reduced heat generation
Improvements noticeable even on older devices like the Qualcomm-based Pixel 5a
While these enhancements significantly improve heat management, it's important to note that Tensor SoCs may still generate heat under heavy use or in direct sunlight due to their power-hungry nature.
Optimized Screen Brightness Control
Android 14 introduces improvements to screen brightness control, enhancing both user experience and battery efficiency. Here are the key optimizations:
Automatic wallpaper dimming: When Battery Saver mode is activated, Android 14 automatically dims the wallpaper to reduce power consumption, especially beneficial for devices with AMOLED displays.
Enhanced adaptive brightness: The adaptive brightness feature in Android 14 uses machine learning to better understand user preferences and adjust screen brightness accordingly based on ambient light conditions.
Transparent navigation bar option: A new setting allows users to force apps to have a transparent navigation bar, potentially improving visibility and consistency across different apps.
Brightness bug fixes: Android 14 addresses some brightness-related issues, such as choppy display at peak brightness levels, which were reported by some users in previous versions.
Manual brightness control retention: While adaptive brightness is improved, Android 14 still allows users to manually adjust and control screen brightness according to their preferences.
These optimizations aim to provide a more seamless and power-efficient brightness control experience, balancing visibility and battery life across various usage scenarios.
Removed or Downgraded Features
Android 14 brings many improvements over Android 13, but there are a few potential drawbacks and removed features to be aware of:
Older app incompatibility: Android 14 no longer allows installation of apps targeting Android 5.1 (API level 22) or lower, which may prevent some older apps from working.
Removal of separate volume controls: Android 14 removes the ability to separately control ring and notification volumes that was present in Android 13.
Lock screen customization limitations: While Android 14 adds new lock screen customization options, some users report fewer clock styles available
compared to Android 13.
Potential adaptive brightness issues: Some users experienced flickering or brightness adjustment problems with the adaptive brightness feature in Android 14 beta versions.
Learning curve for new features: The redesigned settings menus and new customization options may require some adjustment for users familiar with Android 13.
Possible initial bugs: As with any major OS update, there may be some bugs or stability issues in the early release of Android 14 that get ironed out in subsequent updates.
Overall, while Android 14 offers numerous improvements, users should be aware of these potential drawbacks when considering the update.
source: Perplexity GPT-3.5 query using the new "Page"-feature @ https://www.perplexity.ai/page/how-big-are-the-android-14-bat-WxN8GGdgRQSKPPn7DftxtQ
Sunday, June 30, 2024
The Increasing Impact of Global Warming on Smartphone Charging-Performance
As global temperatures rise due to climate change, smartphone users are increasingly experiencing slower charging speeds and reduced device performance. This phenomenon occurs because most smartphones are designed to throttle charging and processing power when internal temperatures exceed certain thresholds, typically around 32°C (90°F), to prevent damage to the battery and other components. With global warming pushing ambient temperatures higher, especially in tropical and subtropical regions, smartphones are more frequently hitting their thermal limits, leading to extended periods of reduced charging efficiency. This growing challenge underscores the need for improved heat management and cooling systems in future smartphone designs, as users adapt their charging behaviors to cope with these changes.
The situation highlights an unexpected intersection between climate change and everyday technology use, potentially influencing future smartphone designs to emphasize improved heat management and cooling systems.
Rising global temperatures due to climate change exacerbate smartphone charging and performance issues
Ambient temperatures frequently approach or exceed 32°C (90°F), especially in tropical and subtropical regions
Phones are more likely to reach their thermal thresholds even when not in active use
Extended periods of slower charging and potential performance throttling occur, particularly during summer months or heatwaves
This situation highlights an unexpected intersection between climate change and everyday technology use
Future smartphone designs may emphasize improved heat management and cooling systems
Temperature-Based Charging Throttling
Charging speed regulation based on temperature is a crucial safety feature in modern smartphones. Internal sensors detect temperature rises and automatically reduce or halt charging when the device gets too warm, protecting against potential battery damage, swelling, or fire hazards. This mechanism balances fast charging capabilities with device longevity. Several factors can contribute to higher temperatures during charging, including:
Ambient temperature
Device usage while charging
Presence of a phone case
Heat generated by fast charging technologies
To maintain faster charging speeds, users may employ methods such as removing phone cases, avoiding device use during charging, or even actively cooling the phone. However, extreme measures like using air conditioning directly on the device are generally not necessary or recommended for everyday use.
Specific Temperature Thresholds
While exact temperature thresholds vary between devices, general ranges for charging speed reduction have been observed:
Above 74°F (23°C), charge current may already drop under 1570mA, depending on the phone
At approximately 86°F (30°C), charge current may drop to around 600mA
Charging speeds typically begin to decrease around 90°F (32°C) battery temperature
Significant throttling occurs above 113°F (45°C)
Some devices may have a cutoff point around 90°F (32°C) for dropping to minimal charging rates, such as 280mA
These thresholds are designed to optimize charging efficiency while protecting the battery from heat-related damage
Adaptive Charging Behaviors
To cope with temperature-related charging issues, users in affected areas are adopting new habits.
Charge devices in cooler locations or during cooler parts of the day to maintain faster charging speeds
Resort to active cooling methods, though this approach increases overall energy consumption
Adaptive behaviors may become more widespread as global temperatures continue to rise, potentially influencing future smartphone designs
Manufacturers might need to focus on developing more efficient heat management and cooling systems to address the growing challenge of temperature-induced charging slowdowns in various climates worldwide
source: summary of personal Perplexity GPT-3.5 query using the new "Page"-feature @ https://www.perplexity.ai/page/smartphones-and-temperature-ba-xEkc7Nd9RA2tXXMoC4VT3g
Thursday, June 20, 2024
New page "useful freeware"
You can now find my recommended freeware in the top right corner (top left in mobile view). I also added two programs.
Friday, April 26, 2024
[updated 28.04.24]
Huawei's Delicate Dance with the Chinese Government
The Chinese government and Communist Party could likely force the chinese tech company Huawei (and others like Oppo, Vivo, OnePlus, Realme, ZTE and Lenovo) to hand over customer data if they requested it, despite Huawei's denials (regarding Huawei). Experts argue that under China's national security laws, including the 2017 National Intelligence Law and 2014 Counter-Espionage Law, companies like Huawei would have little choice but to comply with any demand for data from the government.
The Chinese government has considerable influence over private companies like Huawei through heavy regulation, state-backed investment, and the requirement to have Communist Party branches within the company. Huawei's founder Ren Zhengfei is a former People's Liberation Army engineer and current Party member.
While Huawei has distanced itself from the Party and asserts it would never spy, the company's precise ownership structure is unknown. The Chinese government has also backed Huawei in its disputes with the U.S., suggesting the company is closely aligned with Beijing's interests.
Ultimately, Huawei's ability to resist government data requests remains untested in court. The company's close ties to the Party and China's vague national security laws make it unlikely Huawei could defy a serious demand for customer information from the Chinese state.
Unlikely Transparency: The Challenges of Verifying Data Access by China's Government on Huawei's Servers
It is highly unlikely that the public or even Huawei itself would find out if the Chinese government accessed data stored on Huawei's servers:
China's national security laws give the government broad powers to compel companies like Huawei to cooperate with intelligence gathering without disclosing it. Huawei would have little legal recourse to resist such demands.
The Chinese Communist Party (CCP) has significant influence over private companies through regulation, state investment, and requiring CCP branches within the firms.
Experts argue it would be nearly impossible for Huawei to openly defy a serious request for data from the Chinese government or CCP. The company's close ties to the state make it unlikely it would risk the consequences of defiance.
The U.S. has accused Huawei of having backdoor access to the networks it builds globally, allowing it to covertly access sensitive data. While Huawei denies this, the company's ownership structure is opaque and its ability to resist the CCP remains untested.
In summary, given China's vague security laws, the CCP's control over private firms, and Huawei's close alignment with the state, it is highly improbable the company or the public would ever find out if the Chinese government accessed data on Huawei's servers, even if it did so covertly.
further reading: https://en.wikipedia.org/wiki/Criticism_of_Huawei#Espionage_and_security_concerns
source: summarized Perplexity GPT-3.5 output @ https://www.perplexity.ai/search/huawei-and-privacy-1GvrPM.xRleDM4NicyKRJA
Tuesday, April 16, 2024
Facebook allegedly experiments with draining its' users phone batteries
A former Facebook data scientist named George Hayward has claimed that Facebook has the ability to secretly drain users' smartphone batteries as part of its internal app testing. Hayward alleges that Facebook engages in a practice called "negative testing", which involves deliberately depleting a user's battery to test how certain app features or issues perform when the battery is low.
He claims he was given an internal Facebook document titled "How to run thoughtful negative tests" that included examples of such battery-draining experiments.
Hayward says he raised concerns about this practice, telling his manager that it "could harm somebody", but was told that "by harming a few we can help the greater masses". He was later fired for refusing to participate in the negative testing.
While the full extent of this alleged practice is unclear, the search results indicate that Facebook has long been accused of causing abnormal battery drain on users' devices. Hayward's claims suggest this may have been an intentional effort by the company, though Facebook has not responded to the allegations.
Recommendation
Entirely disable automatic app updates in the Google Play Store for example to reduce risk of automatically becoming a participant of any new Facebook experiment for example, but of course don't forget to update apps if they don't function properly anymore at any point in time.
source: summarized Perplexity GPT-3.5 output @ https://www.perplexity.ai/search/Facebook-users-drain-J88ELze3TFGHm.PiyfvcNw
Monday, April 15, 2024
The Risks of Opera GX: Uncovering the Chinese Connection
A closer examination of Opera GX, the popular internet browser used by over 25 million gamers worldwide, reveals concerning ties to its parent company, Kunlun Tech, which is based in China. This raises significant privacy and security concerns for users. The company made false claims about its location and there are potential risks associated with its parent company.
Changing Policies and Data Sharing Privacy Concerns
The fact that Kunlun Tech is located in China is particularly troubling. The Chinese government has a history of exerting control over the flow of information and engaging in surveillance activities. This raises the possibility that the personal data of Opera's users, including sensitive information, could be accessed and potentially compromised by the Chinese government. One of the most significant changes observed is the update to Opera's privacy policy. The new terms state that by using any Opera service, including Opera GX, users consent to the company's "unrestricted use" of their data. This is particularly worrying given that Kunlun Tech is required to share user data with the Chinese Communist Party upon request.
Predatory Lending Apps
It is also revealed that Opera GX has been connected to several predatory lending apps on the Google Play Store. These apps were known for charging exorbitant interest rates, up to 876%, and even threatening users with legal action or credit blacklisting if payments were late. This shady practice further undermines the company's credibility and raises concerns about its ethical standards.
Opera GX's Concerning Data Practices
To further investigate the risks associated with Opera GX, an experiment was conducted to track the requests made by the browser. The results revealed that Opera GX was making unsolicited requests to a website that provided detailed geolocation data, including the user's exact city, zip code, and coordinates. This level of tracking is highly concerning and undermines the browser's claims of privacy and security.
Conclusion
In light of these revelations, it's clear that Opera GX and Kunlun Tech have a concerning history of questionable practices. From the potential risks associated with data sharing in China to the company's involvement in predatory lending, it's becoming increasingly difficult to trust the browser and its claims of user privacy and security. As users, we must be vigilant and carefully consider the implications of using Opera GX or any other products associated with Kunlun Tech.
Recommendation
Firefox offers a great level of customization and privacy settings while the Brave Browser offers similar features to Opera GX but with a stronger focus on protecting user data of course.
source: Qubick - "The Disturbing Truth Behind Opera GX": https://youtu.be/NV8akIgfDqQ
summarized Perplexity GPT-3.5 output @ https://www.perplexity.ai/search/please-summarize-this-LdYZjPQvSQG2RlB5l6NBFg
Friday, April 12, 2024
A whopping 7 Samsung devices, released between 2010 and 2012, had confirmed backdoors
A backdoor in Samsung Galaxy devices was discovered by the developers of the Replicant Android OS in 2014.
They discovered that the proprietary software running on the modem/baseband processor of certain Samsung devices contained a backdoor that allowed remote access and control of the device. This software allowed the modem to remotely read, write, and delete files on the device's storage, potentially giving an attacker access to the user's personal data and the ability to control the device.
They discovered the backdoor in Samsung Galaxy devices through the following process:
While reverse engineering Samsung's proprietary Radio Interface Layer (RIL) software, which handles communications with the modem/baseband processor, they found that it implemented a set of "RFS commands" that allowed the modem to perform remote file I/O operations on the device's storage.
They analyzed this proprietary Samsung software and discovered that it enabled the modem to read, write, and delete files on the phone's storage, potentially giving the modem access to the user's personal data.
They determined that this functionality constituted a backdoor, as the RFS commands did not appear to have any legitimate use case, and the modem could potentially be remotely controlled to exploit this backdoor.
Samsung has disputed these claims, stating that the "software feature" in question poses no security risk to users and is based on a misunderstanding. However, the researchers maintain that the backdoor functionality exists, even if it may have been added for legitimate purposes.
Affected devices:
Nexus S
Galaxy S
Galaxy S2
Galaxy Note
Galaxy Nexus
Galaxy Tab 2 (7-inch and 10.1-inch models)
Galaxy Note 2
source: summarized Perplexity GPT-3.5 output @ https://www.perplexity.ai/search/which-samsung-devices-kO5JtFT7TkWwJdV8clUhQA
Monday, April 8, 2024
A Linux backdoor (CVE-2024-3094), introduced by "Jia Tan", was discovered
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software for file-compression. Affected systems were Fedora® Rawhide (current development version), Fedora Linux 40, Kali Linux users who had updated their installation between March 26th to March 29th and some Arch Linux virtual machine images, container images and an installation medium.
Andres Freund, a software engineer at Microsoft, stumbled upon the backdoor while investig inating performance issues on a Debian development system, and was able to identify and report the serious vulnerability in the XZ Utils library, despite not being a security expert:
He was testing things on a Debian "sid" (development) installation and noticed that SSH logins were using a lot of CPU power and generating errors. Upon investigating, Freund found the problem was in the liblzma data compression library, which is part of the XZ package. He concluded that "the upstream xz repository and the xz tarballs have been backdoored". His discovery and reporting of the backdoor, which was then confirmed by Red Hat, was the beginning of the public revelation about the compromised XZ Utils versions.
The perpetrator "Jia Tan" (JiaT75) started contributing to xz in the last 2-2.5 years and gained commit access, and then release manager rights, about 1.5 years ago. He was removed on March 3, 2024, as Lasse Collin (Larhzu, the xz maintainer since ~2009) begins his long work ahead.
My personal favorites remain Ubuntu (v22.04.4 LTS) and Lubuntu (for old systems).
For more details regarding the backdoor, especially on how impressive the devious social engineering was, check this highly interesting LWN.net article or https://tukaani.org/xz-backdoor.
sources: Sam James https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27
Perplexity GPT-3.5 output https://www.perplexity.ai/search/were-any-devices-T1YI_0D4QjePSzTVgr1W9A
Sunday, March 24, 2024
Unveiling Google Chrome's Controversial Silent Scans: A Privacy Conundrum
Google Chrome has been known to scan computers for malware without explicit user consent. This scanning process, known as Chrome Cleanup, has raised concerns about user privacy and transparency. Despite the intentions to enhance security, the lack of clear disclosure has sparked debates about the extent of data collection and user awareness.
Chrome Cleanup operates as a local signature engine that scans for potential threats within files and processes on users' systems. While Google emphasizes that this scanning is narrower and less invasive than traditional antivirus software, questions remain about the scope of the scans and the data collected. Users have reported receiving notifications that suggest virus infections or prompt them to run scans, often leading to confusion and suspicion.
One of the key issues highlighted by security experts is the lack of explicit information provided to users regarding Chrome's scanning activities. Users may not be aware that Chrome is conducting these scans, leading to concerns about privacy and control over their devices. The inability to opt-out of this scanning process has also been a point of contention among users seeking more transparency and control over their browsing experience.
In conclusion, while Google's efforts to bolster security through Chrome Cleanup are commendable, there is a clear need for improved communication with users. Transparency, user consent, and clear information about data collection practices are essential in maintaining trust and ensuring user privacy in the digital age.
source: Perplexity GPT-3.5 output @ https://www.perplexity.ai/search/Did-google-chrome-0VedASmhQKuG1cAJ_a_CRA#0
Wednesday, December 13, 2023
Insane 4K streaming requirements...
Oh the struggles with 4K streaming... a post from a Discord user:
Thursday, December 7, 2023
Firefox Theme "Dark Blue Refresh 2023"
Check out my latest sleek and comfortable Firefox Theme "Dark Blue Refresh 2023"! (formerly "dark blue k")
🠞 https://addons.mozilla.org/en-US/firefox/addon/sleek-dark-blue/ 🠜
example screenshots:
Tabs & URL-bar
URL suggestions
Bookmark menu
Shoutout to mibbits user "freaktechnik" for his support making this theme
and to W3schools.com !
Sunday, September 3, 2023
How exploited click workers are spied on
Outsourcing-company CloudFactory Ltd. spies on their workers via their own webcams, part of their 2020 blogpost reveals:
With this new incredible level of surveillance, George Orwell's 1984 gets even closer to reality, with the lives of all affected workers (especially from low-wage countries like Kenya, Pakistan and Venezuela) reaching a striking similarity to his described "telescreens".
source: https://blog.cloudfactory.com/data-security-in-the-age-of-remote-workforces
Friday, July 21, 2023
Firefox Sync extended logging
Purpose
The successful Firefox Sync logs can be used to analyze parts of the inner working of the Sync process.
Configuration
The '''about:sync-log''' provides a list with log files and shows their location within the Firefox profile stored on your computer
The about:sync-log provides a list with log files and shows their location within the Firefox profile stored on your computer.
By default it is setup to only log unsuccessful sync events.
You can configure Firefox to write log files on successful sync as well. The parameter in question for extended logging is services.sync.log.appender.file.logOnSuccess.
Enable logging of successful sync events by following these steps:
Type about:config in the address bar and press Enter.
A warning page may appear. Click Accept the Risk and Continue to go to the about:config page. (For more information about this page see Configuration Editor for Firefox.)Search for the services.sync.log.appender.file.logOnSuccess preference and change its value from false to true by clicking the Toggle button.
Type about:sync-log in the address bar and press Enter.
You should see a page with your sync-log filepath, starting with Index of file:///. A few files named in the style of error-sync-x.txt might be listed, do not worry if you have only a few of those and only one file from the same day.Click the Firefox Account icon in the toolbar.
Click on sync now (assuming you already have set up Sync).
Depending on how long you have browsed without syncing it can take up to a couple of minutes to be completed.After the successful sync, a new file success-sync-x.txt should appear in the list. It's done! Now you will be able to always see when your last successful sync occured.
In the end, keep in mind to either occasionally delete some of the files in case this doesn't happen automatically or to set the services.sync.log.appender.file.logOnSuccess preference to false again. The growth of the sync logs depends on your individual browsing activity, but by default it is scheduled to sync every 10 minutes (~20 KB per logfile, equals to ~1MB per 8 hours of runtime).
Let’s get rid of the ideology of infinite economic growth! growthkills.org
Involved with Mozilla since June 2015
support my work @buymeacoffee.com/dantechblog
dantechblog@outlook.com
Fedora and the Infinity design logo are trademarks of Red Hat, Inc.
Laptop-icon by stephanie walter
© 2024