#rooting — Public Fediverse posts

One of three Quince Bushes I propagated for our new ranch house. #quince #quincebush #quincebushes #pennsylvaniagarden #pennsylvaniagardens #garden #gardens #gardening #gardener #gardeners #bush #bushes #propagate #propagation #propagating #root #roots #rooting #watering #fertilizing #beauty #naturalbeauty #beautyofnature #woody #woodystems #woodystem #leaf #leaves #green #greenery

One of three Quince Bushes I propagated for our new ranch house. #quince #quincebush #quincebushes #pennsylvaniagarden #pennsylvaniagardens #garden #gardens #gardening #gardener #gardeners #bush #bushes #propagate #propagation #propagating #root #roots #rooting #watering #fertilizing #beauty #naturalbeauty #beautyofnature #woody #woodystems #woodystem #leaf #leaves #green #greenery

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Are there any "advanced" #android 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?

#rooting #androidroot #lineageos #crdroid #mod

Rooted Devices: 250 Times More Vulnerable to Cyber Compromise Risks - https://www.redpacketsecurity.com/rooted-devices-250-times-more-vulnerable-to-compromise/

#threatintel #rooting #mobile_security #malware

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 https://valetudo.cloud/pages/general/supported-robots.html

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

#Rooting hard & soft cuttings to #propagate for our garden. #FrugalGardening requires #education on how to propagate. Two of my fave side #hobbies w/ #gardening are learning how to propagate & graft plants. I really enjoy experimenting with plants!
#zone8 #Propagation #Wsanec #Saanich #VictoriaBC #yyj #vanisle #VancouverIsland #PNW #PacificNorthwest #BritishColumbia #Canada #GardenersOfMastodon #SDFgardeners #FreePlants #MastodonGardeners #GrowPlantsNotHate #PlantAGarden #WhatsGoingIntoMyGarden

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: https://arstechnica.com/?p=1668757 #factoryreset #persistence #android #malware #rooting #biz&it