Dedetok: My Experience Notes

Thursday, October 23, 2025

Debian 13: increase nvme life time, and how to check its health with additional ssd sata

We move some mount point to cheaper device sata ssd (sata ssd is cheaper then nvme)

/home
/var
/tmp

for small ram consider to move swap disk into sata ssd. for big ram (equal or more then 16GB), you may keep it on nvme, in case the os require to use swap, it will use nvme for best performance. It is for Debian or other linux distribution, not for windows.

nvme

install nvme-cli to check nvme lifetime

# apt-get install nvme-cli

To list nvme device

# nvme list

To view nmve information

# nvme smart-log -v /dev/nvme0n1 Smart Log for NVME device:nvme0n1 namespace-id:ffffffff critical_warning : 0 temperature : 93 °F (307 K) available_spare : 100% available_spare_threshold : 5% percentage_used : 3% endurance group critical warning summary: 0 Data Units Read : 13440652 (6.88 TB) Data Units Written : 11259034 (5.76 TB) host_read_commands : 204366865 host_write_commands : 182401866 controller_busy_time : 3981 power_cycles : 1399 power_on_hours : 1106 unsafe_shutdowns : 32 media_errors : 0 num_err_log_entries : 0 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 93 °F (307 K) Thermal Management T1 Trans Count : 0 Thermal Management T2 Trans Count : 0 Thermal Management T1 Total Time : 0 Thermal Management T2 Total Time : 0

To view nmve error information

# nvme error-log -v /dev/nvme0n1

You can copy paste the result to AI for analyzing. Gemini said:

"Low Usage. This is the total amount of data written to the drive. For a modern consumer or enterprise SSD, 5.76 TB is a very low amount of lifetime writes."

ssd sata

install smartmontools to check ssd sata

# apt-get install smartmontools

To find ssd

# smartctl --scan /dev/sda -d scsi # /dev/sda, SCSI device

To check /dev/sda health

# smartctl -H /dev/sda smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.48+deb13-amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED

To view information from /dev/sda

# smartctl -a /dev/sda

To show all information in /dev/sda with filter Error

# smartctl -x /dev/sda | grep Error Error logging capability: (0x01) Error logging supported. 1 Raw_Read_Error_Rate -O--CK 100 100 050 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 050 - 0 0x10 GPL,SL R/O 1 NCQ Command Error log SMART Extended Comprehensive Error Log Version: 1 (1 sectors) Device Error Count: 6 (device log contains only the most recent 4 errors) ER = Error register Error 6 [1] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) Error 5 [0] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) Error 4 [3] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) Error 3 [2] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)

to test ssd on /dev/sda

# smartctl -t long /dev/sda smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.48+deb13-amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in off-line mode". Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 4 minutes for test to complete. Test will complete after Thu Oct 23 15:35:03 2025 WIB Use smartctl -X to abort test.

You can use option -t short. After 4 minutes run this command to see the result.

# smartctl -x /dev/sda smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.48+deb13-amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: RX7 2.5 240GB Serial Number: AA000000000000002178 LU WWN Device Id: 0 000000 000000000 Firmware Version: FW201105 User Capacity: 240,057,409,536 bytes [240 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available Device is: Not in smartctl database 7.3/5528 ATA Version is: ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Oct 30 22:15:22 2025 WIB SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Unavailable === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 120) seconds. Offline data collection capabilities: (0x5d) SMART execute Offline immediate. No Auto Offline data collection support. Abort Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 4) minutes. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate -O--CK 100 100 050 - 0 5 Reallocated_Sector_Ct -O--CK 100 100 050 - 0 9 Power_On_Hours -O--CK 100 100 050 - 643 12 Power_Cycle_Count -O--CK 100 100 050 - 476 160 Unknown_Attribute -O--CK 100 100 050 - 0 161 Unknown_Attribute -O--CK 100 100 050 - 0 163 Unknown_Attribute -O--CK 100 100 050 - 880 164 Unknown_Attribute -O--CK 100 100 050 - 85 165 Unknown_Attribute -O--CK 100 100 050 - 118 166 Unknown_Attribute -O--CK 100 100 050 - 50 167 Unknown_Attribute -O--CK 100 100 050 - 81 168 Unknown_Attribute -O--CK 100 100 050 - 0 169 Unknown_Attribute -O--CK 100 100 050 - 100 175 Program_Fail_Count_Chip -O--CK 100 100 050 - 184549376 176 Erase_Fail_Count_Chip -O--CK 100 100 050 - 355223 177 Wear_Leveling_Count -O--CK 100 100 050 - 2488567 178 Used_Rsvd_Blk_Cnt_Chip -O--CK 100 100 050 - 0 181 Program_Fail_Cnt_Total -O--CK 100 100 050 - 0 182 Erase_Fail_Count_Total -O--CK 100 100 050 - 0 192 Power-Off_Retract_Count -O--CK 100 100 050 - 15 194 Temperature_Celsius -O--CK 100 100 050 - 30 195 Hardware_ECC_Recovered -O--CK 100 100 050 - 21 196 Reallocated_Event_Count -O--CK 100 100 050 - 0 197 Current_Pending_Sector -O--CK 100 100 050 - 0 198 Offline_Uncorrectable -O--CK 100 100 050 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 050 - 0 232 Available_Reservd_Space -O--CK 100 100 050 - 0 241 Total_LBAs_Written -O--CK 100 100 050 - 82732 242 Total_LBAs_Read -O--CK 100 100 050 - 76686 249 Unknown_Attribute -O--CK 100 100 050 - 105586 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 GPL,SL R/O 1 Summary SMART error log 0x02 GPL,SL R/O 1 Comprehensive SMART error log 0x03 GPL,SL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 GPL,SL R/O 1 SMART self-test log 0x07 GPL,SL R/O 1 Extended self-test log 0x09 GPL,SL R/W 1 Selective self-test log 0x10 GPL,SL R/O 1 NCQ Command Error log 0x11 GPL,SL R/O 1 SATA Phy Event Counters log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0 GPL,SL VS 16 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) Device Error Count: 6 (device log contains only the most recent 4 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6 [1] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- a0 00 01 00 00 4f 00 c2 c0 51 00 Device Fault Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d5 00 01 00 00 4f 00 c2 c0 a0 00 00:00:00.430 SMART READ LOG ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:00.430 IDENTIFY DEVICE 67 b6 c2 97 32 21 61 7b 60 cf ba 1f ff 00:00:00.360 [RESERVED FOR SERIAL ATA] Error 5 [0] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- a0 00 01 00 00 4f 00 c2 c0 51 00 Device Fault Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d5 00 01 00 00 4f 00 c2 c0 a0 00 00:00:00.430 SMART READ LOG ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:00.430 IDENTIFY DEVICE 67 b6 82 97 32 21 69 79 60 cf ba 3f ff 00:00:00.360 [RESERVED FOR SERIAL ATA] Error 4 [3] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- a0 00 01 00 00 4f 00 c2 c0 51 00 Device Fault Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d5 00 01 00 00 4f 00 c2 c0 a0 00 00:00:00.410 SMART READ LOG ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:00.410 IDENTIFY DEVICE 67 b6 8a 97 b2 21 6b 7b 60 cf ba 3e ff 00:00:00.360 [RESERVED FOR SERIAL ATA] Error 3 [2] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- a0 00 01 00 00 4f 00 c2 c0 51 00 Device Fault Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d5 00 01 00 00 4f 00 c2 c0 a0 00 00:00:00.410 SMART READ LOG ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:00.410 IDENTIFY DEVICE 67 b6 c2 97 32 21 69 79 60 cf ba 1e ff 00:00:00.360 [RESERVED FOR SERIAL ATA] SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Offline Completed without error 00% 641 - # 2 Offline Self-test routine in progress 10% 641 - # 3 Offline Self-test routine in progress 10% 641 - # 4 Offline Self-test routine in progress 10% 641 - # 5 Offline Self-test routine in progress 10% 641 - # 6 Offline Self-test routine in progress 10% 641 - # 7 Offline Self-test routine in progress 10% 641 - # 8 Offline Self-test routine in progress 10% 641 - # 9 Offline Self-test routine in progress 10% 641 - #10 Offline Self-test routine in progress 10% 641 - #11 Offline Self-test routine in progress 10% 641 - #12 Offline Self-test routine in progress 10% 641 - #13 Offline Self-test routine in progress 10% 641 - #14 Offline Self-test routine in progress 10% 641 - #15 Offline Self-test routine in progress 10% 641 - #16 Offline Self-test routine in progress 10% 641 - #17 Offline Self-test routine in progress 10% 641 - #18 Offline Self-test routine in progress 10% 641 - #19 Offline Self-test routine in progress 10% 641 - SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Commands not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 476 --- Lifetime Power-On Resets 0x01 0x010 4 643 --- Power-on Hours 0x01 0x018 6 5421924352 --- Logical Sectors Written 0x01 0x020 6 85241306 --- Number of Write Commands 0x01 0x028 6 5025693696 --- Logical Sectors Read 0x01 0x030 6 74355305 --- Number of Read Commands |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x0009 4 764 Transition from drive PhyRdy to drive PhyNRdy 0x000a 4 221 Device-to-host register FISes sent due to a COMRESET 0x000b 4 0 CRC errors within host-to-device FIS 0x000d 4 0 Non-CRC errors within host-to-device FIS

Sample Device Model: RX7 2.5 240GB

The result required knowledge to interpret it. Copy paste this to AI and what are they suggesting.

Gemini recommendation for "smartctl -x /dev/sda | grep Error" (copy paste only error messages), may misleading recommendation:

"Recommendation: Since the error occurred so early, it's highly likely to be a dead-on-arrival (DOA) or early life failure. The drive should be considered unreliable and immediately replaced under warranty. Do not store critical data on this device."

Gemini recommendation for "smartctl -x /dev/sda" (copy paste all output):

"The drive's SMART overall-health self-assessment test result: PASSED and the zero count on critical wear-related attributes (like Reallocated Sector Count) suggest the media is physically healthy and not currently failing due to wear.

However, the high number of "Device Fault" errors that occurred early in the drive's life, combined with the anomalous self-test log, indicates a potential instability issue."

Chatgpt.com commenting for the output:

"Verdict: Your RX7 240 GB SSD is fully healthy and nowhere near worn out.

Your RX7 240 GB SSD is healthy, low-wear (~2.8 TBW), and has ~95 % lifespan remaining."

Chatgpt.com explanation about the errors:

"What those “Errors” really are

These are entries in the SMART Extended Error Log, not current hardware problems.
Your log shows 6 errors, all at power-on lifetime: 0–1 hours.
That means: they happened right when the drive was brand new or initializing — years ago.
Since then (643+ hours of runtime), no new errors have been logged."

Tuesday, October 21, 2025

Debian 13: upgrading hp ink tank 315 configuration

chatgpt "when you upgraded from Debian 12 → 13, your printing stack also got a major bump (Debian 13 uses CUPS 2.5+ and newer ipp-usb / cups-filters packages). These prefer driverless (IPP Everywhere) printing — and your HP 415 does support that mode."

These steps are generated by chatgpt, but I follow it step by step.

Identify both printer URIs

# lpstat -v device for HP-Ink-Tank-Wireless-415: socket://x.x.x.x:9100 device for HP_Ink_Tank_Wireless_410_series_1BAF5D: implicitclass://HP_Ink_Tank_Wireless_410_series_1BAF5D/ device for PDF: cups-pdf:/

"The implicitclass:// scheme comes from cups-browsed, which discovers and manages driverless IPP printers automatically.
In your case, that printer (HP_Ink_Tank_Wireless_410_series_1BAF5D) is a modern, IPP Everywhere version of your HP Ink Tank 415.
It’s the correct, future-proof configuration — and it’s why your test print worked even without the old socket:// driver."

Remove the legacy driver and clean up your setup

# lpadmin -x HP-Ink-Tank-Wireless-415

Optional to make your new driver as default printer

# lpadmin -d HP_Ink_Tank_Wireless_410_series_1BAF5D

Note: option -d to choose default printer

Check your scanner

# scanimage -L device `v4l:/dev/video0' is a Noname Integrated Camera: Integrated C virtual device device `escl:https://x.x.x.x:443' is a HP Ink Tank Wireless 410 series [1BAF5D] platen scanner device `hpaio:/net/ink_tank_wireless_410_series?ip=x.x.x.x&queue=false' is a Hewlett-Packard ink_tank_wireless_410_series all-in-one device `airscan:e0:HP Ink Tank Wireless 410 series [1BAF5D]' is a eSCL HP Ink Tank Wireless 410 series [1BAF5D] ip=x.x.x.x, xx:xx:xx:xx::1

This is upgrade from previous post Debian Buster: install all in one hp ink tank 315

Thursday, October 16, 2025

How to create apache2 alias myapp to directing to user myuser under directory /home/myuser/public

Note: FOR DEVELOPMENT NOT PRODUCTION!

Use root or sudo for sign with #

Use user myuser for sign $

Enable alias module

# a2enmod

Edit /etc/apache2/sites-available/000-default.conf

.... /etc/apache2/sites-available/000-default.conf Alias "/myapp" "/home/myuser/public" <Directory "/home/myuser/public"> Options Indexes FollowSymLinks MultiVIews AllowOverride None Require all granted </Directory> </VirtualHost>

Create directory public

$ mkdir public

Change the group ownership

# chown -R myuser:www-data /home/myuser/public

Give the www-data group read and execute permissions.

# chmod -R g+rx /home/myuser/public

Adjust the permissions for the home directory itself (not recommended for production, use ACL)

# chmod a+x /home/myuser

Test configuration

# apache2ctl configtest AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message Syntax OK

Restart service

# systemctl reload apache2

Open in your browser http://localhost/myapp

Tuesday, October 14, 2025

Android Studio 2024.1.4: backup and how you migrate your old project

Android Studio move so fast, the developer and ide tools are racing each other.

These are must you backup:

Project name
Your key file i.e jks for your project
your project source

<root_app> remove folders .gradle .idea and build, remove file .gitignore
<root_app>/app remove folders build, libs and release, remove file .gitignore
<root_app>/gradle remove file ./gradle/wrapper/gradle-wrapper.jar

For upgrading from old project, and your project does not have libs.versions.toml file:

Create it (see below) or copy from other project <root_app>/gradle/libs.versions.toml.
change build.gradle.kts (:app)
plugins {
id("com.android.application")
}
into
plugins {
alias(libs.plugins.android.application)
}
Change dependency
dependencies {

implementation("androidx.appcompat:appcompat:1.7.1")
implementation("com.google.android.material:material:1.12.0")
implementation("androidx.constraintlayout:constraintlayout:2.2.1")
testImplementation("junit:junit:4.13.2")
androidTestImplementation("androidx.test.ext:junit:1.2.1")
androidTestImplementation("androidx.test.espresso:espresso-core:3.6.1")
implementation("com.google.android.gms:play-services-ads-lite:24.0.0")

}
into
dependencies {

implementation(libs.appcompat)
implementation(libs.material)
testImplementation(libs.junit)
androidTestImplementation(libs.ext.junit)
androidTestImplementation(libs.espresso.core)

// admob
implementation(libs.play.services.ads)
}
Update your libs.versions.toml, revise the version if necessary:
[versions]
agp = "8.13.0"
junit = "4.13.2"
junitVersion = "1.3.0"
espressoCore = "3.7.0"
appcompat = "1.7.1"
material = "1.13.0"
playServicesAds = "24.7.0"

[libraries]
junit = { group = "junit", name = "junit", version.ref = "junit" }
ext-junit = { group = "androidx.test.ext", name = "junit", version.ref = "junitVersion" }
espresso-core = { group = "androidx.test.espresso", name = "espresso-core", version.ref = "espressoCore" }
appcompat = { group = "androidx.appcompat", name = "appcompat", version.ref = "appcompat" }
material = { group = "com.google.android.material", name = "material", version.ref = "material" }
play-services-ads = { module = "com.google.android.gms:play-services-ads", version.ref = "playServicesAds" }

[plugins]
android-application = { id = "com.android.application", version.ref = "agp" }

Note: if you have other external dependency, keep the library first, and migrate after common library successfully upgraded.

To create libs.versions.toml, at left side Project Files -> gradle -> New -> File, name it with: libs.versions.toml. Continue step 2 above.

This is example of external library, how to move jsoup into libs.versions.toml

Change build.gradle.kts (:app) from

dependencies { ... implementation("org.jsoup:jsoup:1.21.2") // jsoup }

change into

dependencies { .... implementation(libs.jsoup) }

And add into libs.versions.toml

[versions] ... # Define the version number jsoup = "1.21.2" ... [libraries] ... # Define the library coordinates, referencing the version above jsoup = { group = "org.jsoup", name = "jsoup", version.ref = "jsoup" } ...

Friday, October 10, 2025

Debian 13: Configure NVidia in dual gpu - hybrid mode and how to utilize it in Android Studio

List your VGA:

# lspci | grep -E "VGA|3D" 01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 2050] (rev a1) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 0b)

Installation

# apt-get install firmware-nvidia-graphics nvidia-detect nvidia-driver linux-headers-$(uname -r) vulkan-tools

Warning "Conflicting nouveau kernel module loaded" may appear.

Check your nvidia

# nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA107 [GeForce RTX 2050] [10de:25ad] (rev a1) Checking card: NVIDIA Corporation GA107 [GeForce RTX 2050] (rev a1) Your card is supported by all driver versions. Your card is also supported by the Tesla 535 drivers series. It is recommended to install the nvidia-driver

Chek your nvidia software

Note: run glxinfo in "xfce terminal", not "terminal emulator"

GLX information

$ glxinfo | grep "OpenGL renderer" OpenGL renderer string: AMD Radeon 660M (radeonsi, rembrandt, LLVM 19.1.7, DRM 3.61, 6.12.31-amd64)

The desktop will utilize AMD GPU, we want to run Android Studio and utilize GeForce RTX 2050. Create a bash script to run Android Studio using NVidia Geforce RTX2050 instead build in AMD gpu, e.q

#!/bin/bash # Launch Android Studio using the NVIDIA GPU (Prime Render Offload) APP_PATH="$HOME/AndroidStudio/android-studio/bin/studio.sh" if [ ! -f "$APP_PATH" ]; then echo "Error: Android Studio not found at $APP_PATH" exit 1 fi # Run Android Studio with NVIDIA GPU offload __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia "$APP_PATH" &

Usefull command if any systemd error during boot

# journalctl -b -u systemd-modules-load.service