#androiddesktop — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #androiddesktop, aggregated by home.social.
-
Lilbits: Qualcomm launches Snapdragon X2 Elite and Extreme PC chips and Snapdragon 8 Elite for mobile
Qualcomm’s next-gen PC and mobile chips are coming soon, and you probably won’t be shocked to learn that the company is promising big performance gains. While the new Snapdragon 8 Elite Gen 5 is expected to bring some nice improvements to smartphones and tablets, I’m particularly interested in the new Snapdragon X2 Elite and X2 Extreme processors for Windows PCs.
That’s because while […]
#android #androidDesktop #androidOnPc #google #googlePlayGames #lilbits #obs #qualcomm #snapdragon8EliteGen5 #snapdragonX #snapdragonX2 #snapdragonX2Elite #snapdragonX2Extreme
-
Lilbits: Qualcomm launches Snapdragon X2 Elite and Extreme PC chips and Snapdragon 8 Elite for mobile
Qualcomm’s next-gen PC and mobile chips are coming soon, and you probably won’t be shocked to learn that the company is promising big performance gains. While the new Snapdragon 8 Elite Gen 5 is expected to bring some nice improvements to smartphones and tablets, I’m particularly interested in the new Snapdragon X2 Elite and X2 Extreme processors for Windows PCs.
That’s because while […]
#android #androidDesktop #androidOnPc #google #googlePlayGames #lilbits #obs #qualcomm #snapdragon8EliteGen5 #snapdragonX #snapdragonX2 #snapdragonX2Elite #snapdragonX2Extreme
-
Lilbits: Qualcomm launches Snapdragon X2 Elite and Extreme PC chips and Snapdragon 8 Elite for mobile
Qualcomm’s next-gen PC and mobile chips are coming soon, and you probably won’t be shocked to learn that the company is promising big performance gains. While the new Snapdragon 8 Elite Gen 5 is expected to bring some nice improvements to smartphones and tablets, I’m particularly interested in the new Snapdragon X2 Elite and X2 Extreme processors for Windows PCs.
That’s because while […]
#android #androidDesktop #androidOnPc #google #googlePlayGames #lilbits #obs #qualcomm #snapdragon8EliteGen5 #snapdragonX #snapdragonX2 #snapdragonX2Elite #snapdragonX2Extreme
-
Lilbits: Qualcomm launches Snapdragon X2 Elite and Extreme PC chips and Snapdragon 8 Elite for mobile
Qualcomm’s next-gen PC and mobile chips are coming soon, and you probably won’t be shocked to learn that the company is promising big performance gains. While the new Snapdragon 8 Elite Gen 5 is expected to bring some nice improvements to smartphones and tablets, I’m particularly interested in the new Snapdragon X2 Elite and X2 Extreme processors for Windows PCs.
That’s because while […]
#android #androidDesktop #androidOnPc #google #googlePlayGames #lilbits #obs #qualcomm #snapdragon8EliteGen5 #snapdragonX #snapdragonX2 #snapdragonX2Elite #snapdragonX2Extreme
-
KDE in Debian to check out the new hotness. Struggling with multiple NIC management though in a way I did not with Fedora.
XFCE on Debian on my Android Desktop #androiddesktop
-
Larger set of Phoronix benchmarks comparing Moto Edge Fusion 30 to Raspberry Pi 5
Benchmarks ran on #LinuxDeploy #Debian 11
BLUF: Phone is faster
-
Larger set of Phoronix benchmarks comparing Moto Edge Fusion 30 to Raspberry Pi 5
Benchmarks ran on #LinuxDeploy #Debian 11
BLUF: Phone is faster
-
Larger set of Phoronix benchmarks comparing Moto Edge Fusion 30 to Raspberry Pi 5
Benchmarks ran on #LinuxDeploy #Debian 11
BLUF: Phone is faster
-
Larger set of Phoronix benchmarks comparing Moto Edge Fusion 30 to Raspberry Pi 5
Benchmarks ran on #LinuxDeploy #Debian 11
BLUF: Phone is faster
-
Blinky works with ArduinoDroid app.
Had to download from a mirror, as GooglePlay is gatekeeping - Built for an older version bs.
-
I've been a #linux user since 1996 when I installed #slackware using a pack of 3.5" floppies
Just completed a phoronix test run comparing my #motorola phone to an RPi 5. The phone runs roughly 5 times faster for compilation tasks. It also seems to be about 4 times slower than my laptop for compiling.
There are serious issues with android around privacy. I support efforts to find parity with #Android through other efforts such as #LineageOS, but that is another thead.
Here is a snapshot of the #readyfor #androiddesktop I am currently using to type this reply running #Debian 11 via #LinuxDeploy and other apps.
-
I've been a #linux user since 1996 when I installed #slackware using a pack of 3.5" floppies
Just completed a phoronix test run comparing my #motorola phone to an RPi 5. The phone runs roughly 5 times faster for compilation tasks. It also seems to be about 4 times slower than my laptop for compiling.
There are serious issues with android around privacy. I support efforts to find parity with #Android through other efforts such as #LineageOS, but that is another thead.
Here is a snapshot of the #readyfor #androiddesktop I am currently using to type this reply running #Debian 11 via #LinuxDeploy and other apps.
-
I've been a #linux user since 1996 when I installed #slackware using a pack of 3.5" floppies
Just completed a phoronix test run comparing my #motorola phone to an RPi 5. The phone runs roughly 5 times faster for compilation tasks. It also seems to be about 4 times slower than my laptop for compiling.
There are serious issues with android around privacy. I support efforts to find parity with #Android through other efforts such as #LineageOS, but that is another thead.
Here is a snapshot of the #readyfor #androiddesktop I am currently using to type this reply running #Debian 11 via #LinuxDeploy and other apps.
-
I've been a #linux user since 1996 when I installed #slackware using a pack of 3.5" floppies
Just completed a phoronix test run comparing my #motorola phone to an RPi 5. The phone runs roughly 5 times faster for compilation tasks. It also seems to be about 4 times slower than my laptop for compiling.
There are serious issues with android around privacy. I support efforts to find parity with #Android through other efforts such as #LineageOS, but that is another thead.
Here is a snapshot of the #readyfor #androiddesktop I am currently using to type this reply running #Debian 11 via #LinuxDeploy and other apps.
-
Pushing #Debian to #Bookworm on #LinuxDeploy is breaking vnc somehow. I'm wondering if it is something to do with wayland, but idk.
So Bullseye Debian 11 it is on my #motorola #readyfor #androiddesktop
-
Pushing #Debian to #Bookworm on #LinuxDeploy is breaking vnc somehow. I'm wondering if it is something to do with wayland, but idk.
So Bullseye Debian 11 it is on my #motorola #readyfor #androiddesktop
-
Pushing #Debian to #Bookworm on #LinuxDeploy is breaking vnc somehow. I'm wondering if it is something to do with wayland, but idk.
So Bullseye Debian 11 it is on my #motorola #readyfor #androiddesktop
-
Pushing #Debian to #Bookworm on #LinuxDeploy is breaking vnc somehow. I'm wondering if it is something to do with wayland, but idk.
So Bullseye Debian 11 it is on my #motorola #readyfor #androiddesktop
-
Rooted a nice bright red #Motorola Edge 30 Fusion.
This is gonna replace my older LG ThinQ V50.Got #Fdroid, #Termux, and #LinuxDeploy installed
This phone has the kernel config.gz available, so I might be able to compile a fresh kernel for it.
Which means I might be running Docker on this phone!https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
-
Rooted a nice bright red #Motorola Edge 30 Fusion.
This is gonna replace my older LG ThinQ V50.Got #Fdroid, #Termux, and #LinuxDeploy installed
This phone has the kernel config.gz available, so I might be able to compile a fresh kernel for it.
Which means I might be running Docker on this phone!https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
-
Rooted a nice bright red #Motorola Edge 30 Fusion.
This is gonna replace my older LG ThinQ V50.Got #Fdroid, #Termux, and #LinuxDeploy installed
This phone has the kernel config.gz available, so I might be able to compile a fresh kernel for it.
Which means I might be running Docker on this phone!https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
-
Rooted a nice bright red #Motorola Edge 30 Fusion.
This is gonna replace my older LG ThinQ V50.Got #Fdroid, #Termux, and #LinuxDeploy installed
This phone has the kernel config.gz available, so I might be able to compile a fresh kernel for it.
Which means I might be running Docker on this phone!https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
-
Away for a bit while I hunt for a new phone on eBay. I did pick up a counterfeit Chinese 'clone' of Oppo Reno9. More on that later.
Meanwhile, a new toy for my #androiddesktop. I had trouble using getting HDMI using my own USB-C cables, but picked it up when I used the cable with the kit. Cuz USB-C
Just noticed that they are now out of stock. Guess I bought the only one? There are similar stands, but this one had integrated ethernet.
-
#androiddesktop - currently exploring Motorola ReadyFor
-
I had 6 specs I wanted to meet when I picked my #motorola edge+ 2022 512GB 12GB to replace my LG ThinQ V50 #android hacker phone
- #androiddesktop
- faster processor
- 512GB storage
- 12GB+ RAM
- SDcard port
- ~$300Motorola does not support an extra SDcard so that was out.
Now I find out that the 512GB phone I bought on eBay is actually 256GB.
Seller has generous 30 day return for any reason policy.
The only phone I see that matches the specs minus the SDcard is $60 more. And for no good reason, no Samsung. I'm exploring outside of the Samsung ecosystem.
Choices choices
-
This advice worked. Might have worked also if I new about the 'desktop settings' app. I was trying to fix the mouse in settings. Wrong. Desktop Settngs
-
Gonna have to fix the mouse size on my #motorola #androiddesktop
It's yuuuuuuge.
-
The #motorola #androiddesktop _wired_ connection is great.
My first attempt at the Ready-for _wireless_ connection was laggy, inserted random keystrokes, and overall not good.
-
Gonna have to fix the mouse size on my #motorola #androiddesktop
It's yuuuuuuge.
-
Took a moment to charge and find the right configs, but I now have an #Android #Motorola Edge+ 2022 with "Ready For" #androiddesktop displaying on external monitor.
The experience is BIG step up from the LG ThinQ V50. The Google apps such as Chrome are much better displayed, the resolution is much sharper, and the desktop fills my non-standard screen space (35" 3440x1440 monitor) I'm actually excited to have this phone.
Tomorrow I'll slap #LinuxDeploy #Debian on it.
-
Took a moment to charge and find the right configs, but I now have an #Android #Motorola Edge+ 2022 with "Ready For" #androiddesktop displaying on external monitor.
The experience is BIG step up from the LG ThinQ V50. The Google apps such as Chrome are much better displayed, the resolution is much sharper, and the desktop fills my non-standard screen space (35" 3440x1440 monitor) I'm actually excited to have this phone.
Tomorrow I'll slap #LinuxDeploy #Debian on it.
-
Took a moment to charge and find the right configs, but I now have an #Android #Motorola Edge+ 2022 with "Ready For" #androiddesktop displaying on external monitor.
The experience is BIG step up from the LG ThinQ V50. The Google apps such as Chrome are much better displayed, the resolution is much sharper, and the desktop fills my non-standard screen space (35" 3440x1440 monitor) I'm actually excited to have this phone.
Tomorrow I'll slap #LinuxDeploy #Debian on it.
-
Took a moment to charge and find the right configs, but I now have an #Android #Motorola Edge+ 2022 with "Ready For" #androiddesktop displaying on external monitor.
The experience is BIG step up from the LG ThinQ V50. The Google apps such as Chrome are much better displayed, the resolution is much sharper, and the desktop fills my non-standard screen space (35" 3440x1440 monitor) I'm actually excited to have this phone.
Tomorrow I'll slap #LinuxDeploy #Debian on it.
-
Took a moment to charge and find the right configs, but I now have an #Android #Motorola Edge+ 2022 with "Ready For" #androiddesktop displaying on external monitor.
The experience is BIG step up from the LG ThinQ V50. The Google apps such as Chrome are much better displayed, the resolution is much sharper, and the desktop fills my non-standard screen space (35" 3440x1440 monitor) I'm actually excited to have this phone.
Tomorrow I'll slap #LinuxDeploy #Debian on it.
-
My mental model (analogies) of my #android #androiddesktop setup is beginning to shape up like this
android -> windows
#termux -> wsl
#linuxdeploy -> docker running os with or without gui desktops
android shell -> the F2 CLI console on linux laptopsBut despite all these different shells, desktops, and containers - there is but one linux kernel to rule them all
Free Tip: Browsers are much better behaved running in a Linux Desktop (eg XFCE) than the native Browsers apps running on the 'second screen' android desktop. True for both Chrome and Firefox variants.
-
My mental model (analogies) of my #android #androiddesktop setup is beginning to shape up like this
android -> windows
#termux -> wsl
#linuxdeploy -> docker running os with or without gui desktops
android shell -> the F2 CLI console on linux laptopsBut despite all these different shells, desktops, and containers - there is but one linux kernel to rule them all
Free Tip: Browsers are much better behaved running in a Linux Desktop (eg XFCE) than the native Browsers apps running on the 'second screen' android desktop. True for both Chrome and Firefox variants.
-
My mental model (analogies) of my #android #androiddesktop setup is beginning to shape up like this
android -> windows
#termux -> wsl
#linuxdeploy -> docker running os with or without gui desktops
android shell -> the F2 CLI console on linux laptopsBut despite all these different shells, desktops, and containers - there is but one linux kernel to rule them all
Free Tip: Browsers are much better behaved running in a Linux Desktop (eg XFCE) than the native Browsers apps running on the 'second screen' android desktop. True for both Chrome and Firefox variants.
-
My mental model (analogies) of my #android #androiddesktop setup is beginning to shape up like this
android -> windows
#termux -> wsl
#linuxdeploy -> docker running os with or without gui desktops
android shell -> the F2 CLI console on linux laptopsBut despite all these different shells, desktops, and containers - there is but one linux kernel to rule them all
Free Tip: Browsers are much better behaved running in a Linux Desktop (eg XFCE) than the native Browsers apps running on the 'second screen' android desktop. True for both Chrome and Firefox variants.
-
My mental model (analogies) of my #android #androiddesktop setup is beginning to shape up like this
android -> windows
#termux -> wsl
#linuxdeploy -> docker running os with or without gui desktops
android shell -> the F2 CLI console on linux laptopsBut despite all these different shells, desktops, and containers - there is but one linux kernel to rule them all
Free Tip: Browsers are much better behaved running in a Linux Desktop (eg XFCE) than the native Browsers apps running on the 'second screen' android desktop. True for both Chrome and Firefox variants.
-
The Java application Zed Attack Proxy (ZAP) looks like 💩 in my XFCE / Debian / LinuxDeply / Android #androiddesktop
ETA: The inherent fuzzing in the image compression makes the pic look much better than on my monitor where the app is highly pixelated.
-
Messing around with Linux on #android #androiddesktop reminds me of Linux on the Desktop 20 years ago. Fussing with fonts, graphics scales, transient pointer and keyboard issues. Makes me appreciate how far Linux on Desktop has come.
Today's wtf. Wierd behaviour in Firefox in Debian container on Android. Solution: restart container
-
I tried installing #kali on #linuxdeploy for the #android #androiddesktop , but it failed on dependencies.
So going with straight #debian on #android for now.
The RealVNC (RVNC) app was not allowing resized desktops. This #MultiVNC app does and is displaying an #XFCE desktop geom of 1280x768. It does not do realtime desktop geo changes the same way most virtual machine displays do, and `xrandr` is not installed in the debian chroot container. It does, however, have a full screen mode.
-
I tried installing #kali on #linuxdeploy for the #android #androiddesktop , but it failed on dependencies.
So going with straight #debian on #android for now.
The RealVNC (RVNC) app was not allowing resized desktops. This #MultiVNC app does and is displaying an #XFCE desktop geom of 1280x768. It does not do realtime desktop geo changes the same way most virtual machine displays do, and `xrandr` is not installed in the debian chroot container. It does, however, have a full screen mode.
-
I tried installing #kali on #linuxdeploy for the #android #androiddesktop , but it failed on dependencies.
So going with straight #debian on #android for now.
The RealVNC (RVNC) app was not allowing resized desktops. This #MultiVNC app does and is displaying an #XFCE desktop geom of 1280x768. It does not do realtime desktop geo changes the same way most virtual machine displays do, and `xrandr` is not installed in the debian chroot container. It does, however, have a full screen mode.
-
I tried installing #kali on #linuxdeploy for the #android #androiddesktop , but it failed on dependencies.
So going with straight #debian on #android for now.
The RealVNC (RVNC) app was not allowing resized desktops. This #MultiVNC app does and is displaying an #XFCE desktop geom of 1280x768. It does not do realtime desktop geo changes the same way most virtual machine displays do, and `xrandr` is not installed in the debian chroot container. It does, however, have a full screen mode.
-
I tried installing #kali on #linuxdeploy for the #android #androiddesktop , but it failed on dependencies.
So going with straight #debian on #android for now.
The RealVNC (RVNC) app was not allowing resized desktops. This #MultiVNC app does and is displaying an #XFCE desktop geom of 1280x768. It does not do realtime desktop geo changes the same way most virtual machine displays do, and `xrandr` is not installed in the debian chroot container. It does, however, have a full screen mode.
-
Started doing #hackthebox from the #android #androiddesktop using #linuxdeploy running #debian buster
To connect, need OpenVPN tunnel.
I connected as expected using OpenVPN app on android.
I then killed the app and reran from OpenVPN client within the linuxdeploy debian buster container. From the logs, that appeared to work, with a successful VPN handshake with the HtB server and router tables in Debian container configured.
But my packets were refused or failed to return from my border router. I'll have to do some sniffing to find root cause, but I'm guessing the packets were inappropriately NAT'd by Android on the way out.
-
Started doing #hackthebox from the #android #androiddesktop using #linuxdeploy running #debian buster
To connect, need OpenVPN tunnel.
I connected as expected using OpenVPN app on android.
I then killed the app and reran from OpenVPN client within the linuxdeploy debian buster container. From the logs, that appeared to work, with a successful VPN handshake with the HtB server and router tables in Debian container configured.
But my packets were refused or failed to return from my border router. I'll have to do some sniffing to find root cause, but I'm guessing the packets were inappropriately NAT'd by Android on the way out.
-
Started doing #hackthebox from the #android #androiddesktop using #linuxdeploy running #debian buster
To connect, need OpenVPN tunnel.
I connected as expected using OpenVPN app on android.
I then killed the app and reran from OpenVPN client within the linuxdeploy debian buster container. From the logs, that appeared to work, with a successful VPN handshake with the HtB server and router tables in Debian container configured.
But my packets were refused or failed to return from my border router. I'll have to do some sniffing to find root cause, but I'm guessing the packets were inappropriately NAT'd by Android on the way out.
-
Started doing #hackthebox from the #android #androiddesktop using #linuxdeploy running #debian buster
To connect, need OpenVPN tunnel.
I connected as expected using OpenVPN app on android.
I then killed the app and reran from OpenVPN client within the linuxdeploy debian buster container. From the logs, that appeared to work, with a successful VPN handshake with the HtB server and router tables in Debian container configured.
But my packets were refused or failed to return from my border router. I'll have to do some sniffing to find root cause, but I'm guessing the packets were inappropriately NAT'd by Android on the way out.