home.social

#rooting — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rooting, aggregated by home.social.

  1. 2GB RAM tablet in 2026. Android perpetually in status low before a single app opened.

    The fix was already in the kernel — zRAM, a compressed swap block living entirely in RAM. Lenovo compiled it in and never switched it on.

    Three ADB commands (animations, bloat, GPS daemons) freed 60MB without touching the bootloader. Then Magisk + a one-line boot script to call swapon.
    Same hardware. status normal.

    Notes + full command annexure: mrdee.in/notes/rooting-lenovo-

    #Android #Magisk #Rooting #Debian #Homelab

  2. 2GB RAM tablet in 2026. Android perpetually in status low before a single app opened.

    The fix was already in the kernel — zRAM, a compressed swap block living entirely in RAM. Lenovo compiled it in and never switched it on.

    Three ADB commands (animations, bloat, GPS daemons) freed 60MB without touching the bootloader. Then Magisk + a one-line boot script to call swapon.
    Same hardware. status normal.

    Notes + full command annexure: mrdee.in/notes/rooting-lenovo-

    #Android #Magisk #Rooting #Debian #Homelab

  3. Pixel Watch 2 - Privacy Preserving Setup

    I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

    • Unpairing the Watch means factory resetting it.
    • Every feature (literally everything) is google dependent (who would have thought.. i know)
    • Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

    This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

    First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

    I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

    After the watch was set up, i continued and:

    • Deleted the user profile from which i connected the Watch
    • Enabled wireless debugging
    • Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
    • Removed the Google account in the settings
    • Cleared all Bluetooth preferences
    • Enabled Bluetooth discovery
    • Installed KDE Connect on it (not meant for WearOS but it does work barely)

    The watch is now in a state where i can use it daily.

    But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

    Now comes the fun part.

    I've created a basic Kotlin project with both a mobile and WearOS app.

    I will implement features like:

    • Notification sync
    • Call notifications
    • Media Player Control
    • Weather (openweathermap)
    • Heartrate monitoring
    • Sleep tracking
    • Do not Distrurb Sync
    • Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
    • And much more ..

    The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

    Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

    Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

    I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

    So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

    I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

    Cheers.

    #privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

  4. Pixel Watch 2 - Privacy Preserving Setup

    I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

    • Unpairing the Watch means factory resetting it.
    • Every feature (literally everything) is google dependent (who would have thought.. i know)
    • Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

    This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

    First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

    I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

    After the watch was set up, i continued and:

    • Deleted the user profile from which i connected the Watch
    • Enabled wireless debugging
    • Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
    • Removed the Google account in the settings
    • Cleared all Bluetooth preferences
    • Enabled Bluetooth discovery
    • Installed KDE Connect on it (not meant for WearOS but it does work barely)

    The watch is now in a state where i can use it daily.

    But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

    Now comes the fun part.

    I've created a basic Kotlin project with both a mobile and WearOS app.

    I will implement features like:

    • Notification sync
    • Call notifications
    • Media Player Control
    • Weather (openweathermap)
    • Heartrate monitoring
    • Sleep tracking
    • Do not Distrurb Sync
    • Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
    • And much more ..

    The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

    Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

    Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

    I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

    So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

    I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

    Cheers.

    #privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

  5. Pixel Watch 2 - Privacy Preserving Setup

    I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

    • Unpairing the Watch means factory resetting it.
    • Every feature (literally everything) is google dependent (who would have thought.. i know)
    • Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

    This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

    First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

    I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

    After the watch was set up, i continued and:

    • Deleted the user profile from which i connected the Watch
    • Enabled wireless debugging
    • Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
    • Removed the Google account in the settings
    • Cleared all Bluetooth preferences
    • Enabled Bluetooth discovery
    • Installed KDE Connect on it (not meant for WearOS but it does work barely)

    The watch is now in a state where i can use it daily.

    But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

    Now comes the fun part.

    I've created a basic Kotlin project with both a mobile and WearOS app.

    I will implement features like:

    • Notification sync
    • Call notifications
    • Media Player Control
    • Weather (openweathermap)
    • Heartrate monitoring
    • Sleep tracking
    • Do not Distrurb Sync
    • Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
    • And much more ..

    The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

    Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

    Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

    I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

    So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

    I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

    Cheers.

    #privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

  6. Pixel Watch 2 - Privacy Preserving Setup

    I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

    • Unpairing the Watch means factory resetting it.
    • Every feature (literally everything) is google dependent (who would have thought.. i know)
    • Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

    This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

    First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

    I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

    After the watch was set up, i continued and:

    • Deleted the user profile from which i connected the Watch
    • Enabled wireless debugging
    • Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
    • Removed the Google account in the settings
    • Cleared all Bluetooth preferences
    • Enabled Bluetooth discovery
    • Installed KDE Connect on it (not meant for WearOS but it does work barely)

    The watch is now in a state where i can use it daily.

    But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

    Now comes the fun part.

    I've created a basic Kotlin project with both a mobile and WearOS app.

    I will implement features like:

    • Notification sync
    • Call notifications
    • Media Player Control
    • Weather (openweathermap)
    • Heartrate monitoring
    • Sleep tracking
    • Do not Distrurb Sync
    • Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
    • And much more ..

    The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

    Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

    Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

    I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

    So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

    I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

    Cheers.

    #privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

  7. Pixel Watch 2 - Privacy Preserving Setup

    I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

    • Unpairing the Watch means factory resetting it.
    • Every feature (literally everything) is google dependent (who would have thought.. i know)
    • Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

    This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

    First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

    I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

    After the watch was set up, i continued and:

    • Deleted the user profile from which i connected the Watch
    • Enabled wireless debugging
    • Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
    • Removed the Google account in the settings
    • Cleared all Bluetooth preferences
    • Enabled Bluetooth discovery
    • Installed KDE Connect on it (not meant for WearOS but it does work barely)

    The watch is now in a state where i can use it daily.

    But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

    Now comes the fun part.

    I've created a basic Kotlin project with both a mobile and WearOS app.

    I will implement features like:

    • Notification sync
    • Call notifications
    • Media Player Control
    • Weather (openweathermap)
    • Heartrate monitoring
    • Sleep tracking
    • Do not Distrurb Sync
    • Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
    • And much more ..

    The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

    Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

    Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

    I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

    So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

    I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

    Cheers.

    #privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

  8. Why We’re Rooting For Punch The Monkey

    A Story That Feels Personal Punch’s journey resonates because it mirrors human experiences. Observers noticed that Punch often…
    #NewsBeep #News #Wildlife #AU #Australia #for #monkey #punch #rooting #Science #the #were #why
    newsbeep.com/au/512985/

  9. I bought a tablet in 2018 to bring it with me to Ghana instead of my office computer when I was holding training sessions about Organic farming and Aquaponics/Hydroponics farming.

    That was my worst investment ever.

    ChuWi 10 pro with dual boot window 8 and android, I thought would be great to be able to use for presentation and connect to my phone and mobile projector.

    Windows 8 broke immediately and it became unusable. Android can't be updated and its sluggish.

    Trying to turn it into android TV or something similar to be able to watch streaming movies on my home TV (48" 4K that is kind of smart). The main reason I want to use it is because I want to use my VPN, add blockers and remote keyboard to make it easier to enjoy movies and TV shows.

    Damn, it is difficult to do. The platform is no longer supported, the Android can't be updated and using Firefox to access streaming sites is too slow for such an old device.

    I hate getting rid of it, because it works, but I am afraid I can only use it for social media and web surfing.

    #Tablet #Technlogy #ChuWi!0Pro #Android #Windows8 #AndroidTV #Streaming #Support #Rooting

  10. I bought a tablet in 2018 to bring it with me to Ghana instead of my office computer when I was holding training sessions about Organic farming and Aquaponics/Hydroponics farming.

    That was my worst investment ever.

    ChuWi 10 pro with dual boot window 8 and android, I thought would be great to be able to use for presentation and connect to my phone and mobile projector.

    Windows 8 broke immediately and it became unusable. Android can't be updated and its sluggish.

    Trying to turn it into android TV or something similar to be able to watch streaming movies on my home TV (48" 4K that is kind of smart). The main reason I want to use it is because I want to use my VPN, add blockers and remote keyboard to make it easier to enjoy movies and TV shows.

    Damn, it is difficult to do. The platform is no longer supported, the Android can't be updated and using Firefox to access streaming sites is too slow for such an old device.

    I hate getting rid of it, because it works, but I am afraid I can only use it for social media and web surfing.

    #Tablet #Technlogy #ChuWi!0Pro #Android #Windows8 #AndroidTV #Streaming #Support #Rooting

  11. Sempre più ridicoli, "... Sottoposto a rooting o modificato senza autorizzazione." a chi dovrei chiedere l'autorizzazione per modificare un #hardware comprato con i miei soldi quindi mio!? #Samsung #smartthings #android #lineageos #root #rooting #playintegrty #aosp

  12. Well S7 means I gotta rethink a few things Palapa Webserver is being replaced by #KSWeb

    TerminalEmulator is being superseded by #Termux (cause built in #ffmpeg means no need for #rooting )

    Recurring ones:
    * 66DNS
    * #Lazyboard
    * #USBCamera
    * #iBisPaint (not sure how to disable wifi connection on stock...)

    Gone:
    * Magisk
    * #XPosedEdge (This one hurts the most. I really wanna keep Dex. #Tasker can substitute a few schedulers but.. XEdge really is its own thing)

    Oh well.
    We'll see
    #StuffAlcea

    #Cronjobs also supported in KSWeb (pro)

    (Ultimatively #Macrodroid serves as goodenough #cronjob makeshift)

    #repost •acws #acws

  13. Well S7 means I gotta rethink a few things Palapa Webserver is being replaced by #KSWeb

    TerminalEmulator is being superseded by #Termux (cause built in #ffmpeg means no need for #rooting )

    Recurring ones:
    * 66DNS
    * #Lazyboard
    * #USBCamera
    * #iBisPaint (not sure how to disable wifi connection on stock...)

    Gone:
    * Magisk
    * #XPosedEdge (This one hurts the most. I really wanna keep Dex. #Tasker can substitute a few schedulers but.. XEdge really is its own thing)

    Oh well.
    We'll see
    #StuffAlcea

    #Cronjobs also supported in KSWeb (pro)

    (Ultimatively #Macrodroid serves as goodenough #cronjob makeshift)

    #repost •acws #acws

  14. i'm #rooting for #anybody trying to be a better version of #themselves. shit not always easy!!

  15. i'm #rooting for #anybody trying to be a better version of #themselves. shit not always easy!!

  16. i'm #rooting for #anybody trying to be a better version of #themselves. shit not always easy!!

  17. i'm #rooting for #anybody trying to be a better version of #themselves. shit not always easy!!

  18. i'm #rooting for #anybody trying to be a better version of #themselves. shit not always easy!!

  19. Zimperium found a critical flaw in an older version of the Android rooting tool, #KernelSU, that could allow a full device takeover. Update now if you use it!

    Read: hackread.com/kernelsu-android-

    #CyberSecurity #Vulnerability #Android #Security #Rooting

  20. I was today years old when I started #rooting androids.

    Lessons so far.
    1. Root your phone before it goes stale. Tried to root a 11 yo HTC. The Tools and boot images are memory holed.

    2. #OPPO cockblocks rooting (at least on CPH1941 😥)

  21. Are there any "advanced" rooting/modding support channels? Places where I can ask things like:

    * Is it possible for me to decrypt and mount the /data partition manually from the lineageos recovery?
    * What exactly was it that google changed about play integrity that broke bypasses? It doesn't seem to affect microg, will it in the future?
    * How are secrets stored in the keystore and can I disable the hardware keystore to make backups work?

  22. The secret behind “unkillable” Android backdoor called xHelper has been revealed - Enlarge (credit: portal gda / flickr)
    In February, a researcher detailed a widely circulating And... more: arstechnica.com/?p=1668757 #factoryreset #persistence #android #malware #rooting #biz&it

  23. Another Robot Vacuum released from the cloud. Now can live a happy offline life 🙂

    I have a Dreame Breakout PCB in Vienna and can help you rooting your robot, if supported.

    Check out valetudo.cloud/pages/general/s

    #robotvacuum #rooting #cloudfree #cloudless #tech #valetudo

  24. Trying to propagate mountain laurel (Kalmia latifolia). I'm not optimistic and would be happy with even one. Will update in six months or so. #plants #kalmia #ericacea #propagation #hormones #rooting #gardening

  25. Gravenstein scion wood from 2024 that's been in the refrigerator. I saw a forum post mentioning they had some old scion wood that was callused up so I went and looked at mine and some of it was callused up so I stuck it in some water and put a bag over it the other day. It was already leafed out and I didn't expect those to turn green but they did. Wait and see if the callus grows roots.

    #gardening #orchard #AppleTree #rooting #propagation #apples #GrowYourOwn

  26. New Study: Rooted Android phones are 3,000x more likely to face breaches, while jailbroken iPhones are actively targeted with malware; thanks to advanced toolkits.

    Read: hackread.com/rooted-androids-b

    #CyberSecurity #Android #iOS #Rooting #Jailbreak

  27. It turns out to be surprisingly easy to get fresh herbs from the grocery store to root in an old soda bottle. Here is some mint ready to be repotted! #rooting #mint #herbs #propagation #hope

  28. CW: long post, Final research about rooting samsungs phones

    ​:kanaDead:​ Since I was struggling myself to find a safe, non-misleading guide, There are the simple steps:

    # Getting TWRP & Unlocked vbmeta.img
    For TWRP: https://twrp.me/Devices/
    For patched vbmeta.img: Ask the developer who developed TWRP for your device
    For Qualcomm & Snapdragon, there should be KVM support, but couldn't guarantee.
    If you don't find your phone in the list, check if OrangeFox recovery supports your phone or download the firmware of your phone from https://samfw.com , get TWRP base repository tree and thinker around with the vendor & product images, which are providing functionality to use the phone drivers.
    
    # Unlocking
       * WARNING: Knox Warranty may flip from 0x0 to 0x1, meaning no warranty, Samsung locked it down well
       * You can use Odin instead of heimdall if you want, but is up to you
       * Example usage for heimdall: `heimdall flash --vbmeta vbmeta.img` | `heimdall flash --<partition name> <image>`
    1. Developer Options
    2. OEM Unlock
    4. poweroff
    5. Hold VolUp + VolDown && plug USB into the phone
    6. Will boot into Odin screen
    7. Unlock bootloader
    8. After restart, Developer Options & USB Debugging
    9. From PC: adb reboot bootloader
    10. Use heimdall on PC to upload twrp*.img and vbmeta.img, remember to add no-reboot option to heimdall
    11. To upload both twrp*.img and vbmeta.img you may need to enter bootloader twice
    12. Reboot manually in possibly both cases and quickly press VolUp + Power Button
    13. Enter TWRP
    14. Do Backup -> Boot + Super + Cache (SDCard needed, will use /sdcard/TWRP/BACKUPS)
    15. Go to Terminal / Advanced -> Terminal and type: "multidisabler" or "multi_disabler" (TAB it if possible)
    16. This will flash patch onto boot.img, after executing command go back to Backup -> Boot
        * System is now ready with TWRP
    17. Go to Install -> Select Image and select your GSI OS of choice or some compatible one
        * Treble GSI should give you full phone firmware support
        * For rooting, Follow Magisk guide as it was the only one working at the time (2024/2025~)
        * Done
    
    # Locking
    1. Developer options
    2. OEM Unlock check + USB Debugging
    3. From PC: adb reboot recovery
    4. Wipe data && factory reset && all cache, Internal Storage etc., WITHOUT "Storage" + Restore first backup
       * You may want here to unplug the SDCard after restore
    5. in TWRP: Reboot -> bootloader
    6. Flash stock vbmeta.img found from samfw.com
    7. Reboot manually
    8. System should automatically restore recovery and boot up
    9. Power off
    10. Hold VolUp + VolDown && plug USB into the phone
    11. Lock bootloader
    12. System will reboot and erase pending data
    13. In Stock Android: Developer option -> OEM Unlock: OFF
        * Possibly restart if said so
    14. Wipe again in the Stock Android recovery
        * WARNING: Know Warranty is still voided even if you've got back the Strong Integrity
        * Done

    Backup of the message can be found
    here.

    #samsung #rooting #android

    Linking patched vbmeta in-case you couldn't get one or develop out of stock one:

  29. A rare encounter: I spent two days unlocking and a donated phone with the help of Russian forums, just to find out that it doesn't support USB host mode in the end. No free microscope display for me today.

    On a side note, Android is crazy snappy compared to any computer I used after 2000. There's no delay between touching the screen and the sound feedback. This should never get forgotten in

  30. A good example of the start of scion (Viognier in this case) rooting because the under-vine weeder has mounded up soil around the vine trunk.

    If this continues, you end up with the situation in the second photo: large roots growing from the scion but the rootstock fails to thrive. Eventually the rootstock dies off and the vine is own-rooted (and therefore susceptible to phylloxera and other soil conditions they may not be well adapted to...).

    #Viticulture #Rootstocks #Rooting #OwnRoots

  31. for different reasons, wild #boar are also beneficial to the #forest #ecosystem, contrary to popular misconceptions. Here's an excerpt from an article by Chantal Lyons, "Rooting for the truth: on wild boar" - Lyons writes, "I suppose there are two layers to this. In terms of their #ecological role, they’re unique. The niche they occupy, and the ecological functions they perform, there are no other animals among British #fauna that do the things they do. For example, their #rooting; #badgers engage in some rooting behaviour, resembling mini boars at times. However, they don’t penetrate the soil as deeply, and their rooting is not as extensive.

    There’s a term for it called ​#bioturbation: the act of going into the soil, breaking it open, and mixing the different layers, which impacts the nutrients and the microbial activity in the #soil. This also involves exposing the #seed bank and creating space for #wildflowers to germinate. There’s evidence that bioturbation enhances the soil in a way that makes it easier for #trees, such as #oaks, to germinate and grow.

    Related to the rooting behaviour, wild boar are particularly effective at dispersing seeds and spores. They go all over the place, carrying these organisms in their fur and hooves, and even in their digestive systems, subsequently depositing them through excretion. Additionally, their wallowing activities create mini wetlands, providing valuable ephemeral pools that benefit other wildlife."

    rewildingbritain.org.uk/blog/w

    #Rewilding #UK #GreatBritain #Britain #Biodiversity

  32. I've been #rooting #Android devices for well over a decade (something like eight or nine phones in total). Typically, that much time and experience in any subject will result in mastery.

    But every time I get a new phone and start trying to #root it, I find that most of what I "know" about rooting is no longer valid, so I have to re-learn most of it from scratch. Which is kind of frustrating, but also kind of fun.

    To illustrate what this feels like, imagine that every few years, you decide to re-read one of your favorite #novels, so you retrieve it from your bookshelf, only to discover that a bunch of chapters, settings, characters, and plot points have been added, removed, or changed since the last time you read it. It's basically a brand new #book, even though you've read it many times before. And though you find it mildly irritating that your beloved #novel keeps changing, you also enjoy the #novelty of it (no #pun intended).

    Never a dull moment in the life of a #tech #nerd. 🤓📱

  33. Yesterday I woke up angry at the world. So I channeled my anger into getting rid of the useless I would otherwise need to log in to my company's account. OneLogin Protect is just an elaborate way to hide a token while simultaneously punishing people for exercising their device ownership by their device. Now I have the token I can just use any other app.

  34. I have officially given life to TWO #iPods, an #iPodNano 5th gen. and an #iPodShuffle 2nd gen. by "#rooting" them (using #GTKpod and some other hacks) and allowing #FOSS applications which include libgpod to import and export songs.

    Such applications are #Clementine #Strawberry and #Rythmbox if I'm not mistaken

    I'm really proud of myself!!

  35. my device is worth it after all... and you can't change my mind

    on is absolutely fantastic and I am in love :blobfoxmeltsoblove:

  36. ഓക്കേ.. #android #rooting നിർത്തിയേക്കാം.... #LavaMobiles Lava X2 രണ്ടുദിവസം റൂട്ട് ചെയ്യുവാൻ ശ്രമിച്ചു വെറുതെ കളഞ്ഞു 😂😭 ഒരു രക്ഷയും ഇല്ല!