Thanks to the stinger for pointing me to https://github.com/KDE/kdeconnect-android/commit/63d1d15c4fb02dadf0a28ad3358150e14970f94d
Wwjl
- Oct 3, 2024
- Joined Jul 31, 2023
AlphaElwedritsch I'm mostly using it for keeping an eye on the battery while charging - and to get a notification on my desktop when it has 80%
I was told here that to add Google's adaptive charging would need too many proprietary pieces which probably only Google has anyway...Here's the log:
type: crash
osVersion: google/bluejay/bluejay:14/AP2A.240905.003.F1/2024092900:user/release-keys
package: org.kde.kdeconnect_tp:13203
process: org.kde.kdeconnect_tp
processUptime: 333 + 354 ms
installer: com.android.packageinstallerjava.lang.SecurityException: Settings key: <enabled_input_methods> is only readable to apps with targetSdkVersion lower than or equal to: 33
at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:3562)
at android.provider.Settings$Secure.getStringForUser(Settings.java:6974)
at android.provider.Settings$Secure.getString(Settings.java:6940)
at org.kde.kdeconnect.Plugins.RemoteKeyboardPlugin.RemoteKeyboardPlugin.checkRequiredPermissions(RemoteKeyboardPlugin.java:417)
at org.kde.kdeconnect.Device.addPlugin(Device.kt:558)
at org.kde.kdeconnect.Device.reloadPluginsFromSettings(Device.kt:629)
at org.kde.kdeconnect.Device.addLink(Device.kt:337)
at org.kde.kdeconnect.KdeConnect$connectionListener$1.onConnectionReceived(KdeConnect.kt:156)
at org.kde.kdeconnect.Backends.BaseLinkProvider.onConnectionReceived(BaseLinkProvider.java:42)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.addOrUpdateLink(LanLinkProvider.java:286)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.lambda$identityPacketReceived$0(LanLinkProvider.java:246)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.$r8$lambda$ffuZOFU1qk4o1cE14ZuWQYJam9A(LanLinkProvider.java:0)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$$ExternalSyntheticLambda6.handshakeCompleted(R8$$SyntheticClass:0)
at com.android.org.conscrypt.AbstractConscryptSocket.notifyHandshakeCompletedListeners(AbstractConscryptSocket.java:607)
at com.android.org.conscrypt.ConscryptEngineSocket.doHandshake(ConscryptEngineSocket.java:270)
at com.android.org.conscrypt.ConscryptEngineSocket.startHandshake(ConscryptEngineSocket.java:218)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.identityPacketReceived(LanLinkProvider.java:259)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.tcpPacketReceived(LanLinkProvider.java:119)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.lambda$setupTcpListener$3(LanLinkProvider.java:346)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.$r8$lambda$fPOfB-9YGQBHf7IKMxU23L4W5VA(LanLinkProvider.java:0)
at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$$ExternalSyntheticLambda5.run(R8$$SyntheticClass:0)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)- Edited
Got it this morning - and KDE Connect keeps crashing since. On DivestOS (older Pixel 3a) the same version still runs. Please tell me how to debug, or if anyone can reproduce - thanks.
Tried so far: rebooting, reinstalling the app (KDE Connect 1.32.3). Also tried with WebView JIT disabled (default is enabled).Can't say anything about Amazfit devices, first I thought I'd get one too, but in the end decided to use a sub 30$ Mi Band 8 instead.
Runs very nicely with Gadgetbridge after setting up an account with Xiaomi for the MiFit app to get a security key, a one-time process which is described on the Gadgetbridge webpages. Read more about my experiences with that combination on my blog if you wish, filter it with something like https://wolfgang.lonien.de/?s=gadgetbridge
Hope that helps...
- Edited
davey decided against self hosting
I understand.
Re: wallet - I don't use one, and for payments I've tried the app from my bank (Deutsche Bank) in the past which worked. But since I'm also against putting all things in one basket, that one had to go again.
Regarding security, I rate GrapheneOS higher than both my Arch and Debian installs on the desktop.- Edited
For CalDav, you could probably run an own server, this is what I do. I have https://radicale.org/v3.html on a RaspberryPi 5 (it's even in the repository, so no biggie to set it up), and on the phone side I use Etar together with DavX5 for syncing, which works well. I copied the calendar from Google to that radicale server; done.
Edit: forgot - just looked up my phone with GrapheneOS on the Pi-Hole, not one blocked address at all, while I see both stock Pixel 8 and 6 from daughter and wife there... it's the best system in the house.I used OrganicMaps especially on older hardware because its downloadable offline maps are pre-rendered, so the whole application takes less CPU than OsmAnd(+). However, after buying a fitness tracker and integrating it with Gadgetbridge, I swapped to OsmAnd(+) on my Pixel 6a so I could track myself when excercising outdoors if I wanted to.
MagicEarth isn't entirely open source, but I think you'll have that problem anyway in case you want nice and good sounding natural voices, so that would be my preferred choice in a car (love the British English voices).
I don't have Google services installed, but all three work very well. Hope that helps...mommy No, but you can achieve that with Obtainium if you like. Or manually like @mythodical wrote.
Debian and Arch. See https://wolfgang.lonien.de/2023/12/now-running/ for more info
[deleted] I've had zero issues
That may well be. I also had zero issues installing all kinds of third party operating systems on numerous Nexus and Pixel devices over the years, and GrapheneOS installed nicely (via cli) on the Pixel 3a. So I guess it must me my bluejay device which behaves somehow strange.
treequell There are no such issues with web installer.
Of course not - that was what I saw using the cli installer, the flash-all.sh script stopped after flashing the first slot, so from there on (after rebooting the device) I tried those lines one by one myself, just with copy & paste from the script to the command line.
treequell If you're still struggling with your PC
I don't think that I'm stuggling with my PC. I'm retired by now, but before that I helped the Debian project a bit, was a system administrator in healthcare IT, and also with IBM for several years in technical support. I think I know my way around computers, except that I don't like Windows or Mac much (have been on Linux for over 20 years, also tried some BSDs and supported Solaris before that).
But no bad feelings, again I thank you all, and it's all good. For the moment I'll stay on stock Google Android (as do my wife and daughter anyway), and on the 3a Graphene was awesome, but DivestOS is also nice.
Thanks all.
- Edited
treequell I just did, temporarily disconnected my audio interface to do so. No difference.
treequell This error is most likely caused by your USB connection dropping.
I thought so too in the beginning - but as it can be repeated with GrapheneOS (haven't tried others on this 6a) I think somehow it corrupts the first phone slot after flashing it, and then stops. I've tried that twice now, the rescue mode then booted stock Android from slot B which saved me.
treequell Make sure also that you have at least 32GB free storage space on your PC.
On my /home I have 32.5GiB/256GiB, on my /bigdisk (still rotating platters) it's 1.99TiB/3.58TiB. That's the occupied/total bits...
I could flash it back to stock with Google's web installer, and that option also locked my bootloader again - now it's on the August patch of Android 13, which I'll keep for now.
But thanks for the help everyone. I still think GrapheneOS is golden, although on the 3a I now changed to DivestOS (easily and without any problems installed from my front USB btw) as suggested. That's a good option for devices not covered here anymore indeed, so thanks for that tip as well.
- Edited
I have only a USB Type C port free on the back of my machine; however I can still try to temporarily unplug my monitor's USB cable from one of the USB A ports.
That doesn't however solve the problem with the unsuccessful downloads from the web installer. Still repeatedly getting:
no matter if I try from Debian or Arch, no matter if I try Chromium or the original Google Chrome browser without any extensions...
To my limited knowledge that should have nothing to do with any USB cabling and/or port, or does it?
Anyway, thanks all...2nd edit: just checked, started into fastboot again, and then it's like this:
wjl@handa-6:~$ fastboot devices
29011JEGR15311 fastboot
wjl@handa-6:~$ fastboot flashing get_unlock_ability
< waiting for any device >
^C
wjl@handa-6:~$And no matter which fastboot command from the .sh script I try manually, it's always that answer - guess that is the reason that the web installers (both Graphene's and also Google's) also get stuck at this point... tried factory reset yesterday, didn't help. No idea at which point the Android web installer then worked, and why (I was still on platform tools 33 on Debian yesterday, now it's 34.0.4)... anyway, it's after midnight here, so thanks for now and good night...
- Edited
treequell Use the USB ports on the back of your machine. The ones on the front usually aren't suitable for flashing GrapheneOS.
Hm, I don't know if I have any free in the back, can look for that tomorrow. The front ones are 2 x USB 3.2 Gen 1 Ports, the back ones 4 x USB 3.2 Gen 2 ports so yes these are a bit speedier. MB is https://rog.asus.com/motherboards/rog-strix/rog-strix-b550-i-gaming-model/ in a mini-ITX case (Cooler Master NR200)
Edit: one of the the front ports is currently charging the Pixel 3a, while the 6a is on the wall socket charger, updating stock Android while I type... bugs me that the boot loader is still open...- Edited
de0u That sounds like it might be a USB cable/port problem. What kind of cable are you using, and where is it plugged in?
The original cable (USB-C to USB-A) which came with the device, and I tried two different USB-A ports on the front of my machine (the back is hard to reach, that's where keyboard, mouse, and audio interface are used). Normal data transfer or charging works nicely with those front ports (I've built the machine myself, should be good).
OS: tried with both Arch and Debian Bookworm, could also try with Windows if that had to be, but I don't know much about Windows anymore...- Edited
I have the same with the web install method. After trying to download release with its blue button, I get in red: Error: undefined. Is repeatable, but stops at different downloaded bytes.
Also, when trying the cli method it stops after trying to flash the first slot, then the phone doesn't react on any further fastboot command except fastboot devices. Knobs are pretty much stuck at this point, the only key combination to save one's butt is holding Rescue and vol up at the same time for about 10 seconds or so, then it boots into stock Android but with an unlocked bootloader...
Could flash it back with stock Android yesterday, now there's a new one, still trying after failing with GrapheneOS again on this device... (bluejay)wyliecon Can you check fastboot --version on a Mac?
I'm asking because on Arch I had the platform tools version 34 which were seriously broken (fastboot devices for instance showed me the correct serial on anything connected, but the string there was from my Focusrite Scarlett audio interface), and I think I've seen the same message there.
On Debian where I still had fastboot version 33.0.3-8952118 everything worked nicely, but as of now it's changed to "at least 34.0.4" on https://grapheneos.org/install/cli#obtaining-fastbootde0u As a practical matter, once a device falls out of GrapheneOS support if you have low-security uses for it you might look at some other platforms such as DivestOS.
That is very good advice I think - especially because the dev of DivestOS also recommends GrapheneOS for those who can easily afford new Pixel devices... thanks!
